Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Coqtop stderr output appears on the screen randomly #61

Open
felixbauckholt opened this issue Jul 3, 2017 · 0 comments
Open

Coqtop stderr output appears on the screen randomly #61

felixbauckholt opened this issue Jul 3, 2017 · 0 comments

Comments

@felixbauckholt
Copy link

When stepping through the following file (using Linux and Coq version 8.6), the string "<W> Grammar extension: in [constr:operconstr] some rule has been masked" appears on the screen at an unpredictable location:

Inductive natprod : Type :=
| pair : nat -> nat -> natprod.
Notation "( x , y )" := (pair x y).

This string doesn't move when scrolling through this file, so it doesn't seem like Vim is aware of its existence.

The appearing string doesn't seem to be in the coquille files, it looks like it's the output of Coqtop (see for example some of the output here: http://www.lix.polytechnique.fr/coq/pylons/logs/view/QuicksortComplexity/5528711275707690290).

Furthermore, this doesn't happen when I add stderr = subprocess.PIPE to the coqtop = subprocess.Popen(...) call in coqtop.py. So I think this message is from the stderr output of Coqtop.

I'll make a pull request to suppress this message shortly; any suggestions on how to use this message in a helpful way are welcome!
felixbauckholt pushed a commit to felixbauckholt/coquille that referenced this issue Jul 4, 2017
Send the Coqtop stderr output to a pipe, as opposed to to Vim
14b9349 
This should fix issue the-lambda-church#61.

I tried doing what the code for Windows NT did and redirect the stderr
output to stdout, but that freezes my Vim process for some reason. So I
just send it to a pipe that is never read from.
@felixbauckholt felixbauckholt mentioned this issue Jul 4, 2017
Open
christofsteel pushed a commit to christofsteel/coquille that referenced this issue Aug 4, 2017
@christofsteel
Send the Coqtop stderr output to a pipe, as opposed to to Vim
22ec4fd 
This should fix issue the-lambda-church#61.

I tried doing what the code for Windows NT did and redirect the stderr
output to stdout, but that freezes my Vim process for some reason. So I
just send it to a pipe that is never read from.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@felixbauckholt