-
Notifications
You must be signed in to change notification settings - Fork 661
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.
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
CoqIDE on Windows does not report error if "Compile Buffer fails" #3991
Comments
Comment author: @MSoegtropIMC Dear Coq team, CoqIde 8.5-beta1 does not report an error if a compile buffer fails. As far as I can tell, this happens for any error, so I did not supply a sample. Best regards, Michael |
Comment author: @gares I have to admit that I did not even know this feature existed ;-) But here I see a (temporary) message in the bottom bar. Is this also broken on windows? Or you were expecting a red If so I will turn the bug into a feature request. |
Comment author: @MSoegtropIMC Dear Enrico, on Windows I don't see any difference between a succesfull and a failed compile, not even a temporary message in the status bar. With 8.4, in the case of an error the errors are shown in the bottom right message area and a message is shown in the status bar. On a successfull compile I get a message in the status bar. On 8.5 neither seems to work. Best regards, Michael |
Comment author: @Zimmi48 I cannot reproduce the bug in Coq 8.5pl2 on Linux. Compilation output: File "/home/theo/test.v", line 2, characters 2-8: Can we mark this bug as fixed or is there still a problem on Windows (in Coq 8.5pl2)? |
Comment author: @MSoegtropIMC Dear Théo, as fa as I know this problem always existed only on Windows. And it doesn't seem to be fixed there in 8.5pl2. When I create a file with an error, save it and compile it, I just get: Running: coqc -I "C:\TEMP" "C:\TEMP\Test.v" 2>&1 in the message buffer, but nothing else. Best regards, Michael |
Comment author: @Zimmi48 Yes, Enrico just explained that to me. Sorry for the noise :S |
Note: the issue was created automatically with bugzilla2github tool
Original bug ID: BZ#3991
From: @MSoegtropIMC
Reported version: 8.5
CC: @gares, @MSoegtropIMC
The text was updated successfully, but these errors were encountered: