-
Notifications
You must be signed in to change notification settings - Fork 17
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
fstar-mode opens new buffer upon errors #46
Comments
Can you try reproducign this in a clean Emacs ( |
Sorry, I'm not that familiar with emacs, which makes my config a likely candidate, however, the only thing that changed before those splits started appearing was an update of fstar-mode.
I would also try it with emacs -Q, but I did not manage using/installing fstar-mode with that method. |
Thanks for your help. I think a screenshot would help :) It might also be my config that makes things work nicely for me :) |
Thanks, that clarifies it a lot :) This sounds like an F* issue, at least in part. F* mode warns you loudly (as you can see) when F* warns about an error in a file that isn't the current file. Here, F* claims that the error came from FStar.Seq.Properties.fst, which isn't the current file. @aseemr, ideas? |
I do get the same buffer split with warnings such as:
|
up; that one is on the fstar-mode side. When I originally wrote it, F* didn't issue warnings like this one. An update would be good. I wonder what the UI should be like, though: should the warnings persist (like errros?), or should they be displayed in the echo area and fade after a small amount of time? I'd guess persisting would be better, right? |
For my taste, I would like the warning to persist in the echo area. It would be nice to hear some more opinions on this, though. I guess it's a matter of preference/workflow. |
@cpitclaudel: See #45 for F* reporting errors in other files (in that case, F* is to blame). |
@s-zanella Woops, not sure how I missed that other thread. Thanks! |
Persisting warnings is good. Maybe the mini-buffer should display the first error rather than the first warning, to ease navigation. |
Ok, I've pushed a draft to https://github.com/FStarLang/fstar-mode.el/tree/46-warning-popups :) @kkohbrok, can you have a look? It should show warnings as orange underlines. |
@kkohbrok It seems that you're still using the unpatched version. Are you sure your Emacs is not loading a stale .elc file? @cpitclaudel The behaviour improved somewhat for me: I no longer get a new Emacs windows for warnings, but warnings don't persist in the echo area as error messages do. Some warnings don't have proper location info (e.g. FStarLang/FStar#836), so they can go easily unnoticed since they will show only in the Messages buffer and there will be no highlighting in the source buffer. |
@s-zanella Thanks for testing! I tried FStarLang/FStar#836, and indeed I get Regarding persistence: can you post an example file? Thanks! |
I completely missed the line under the first character! All cases of Best to explain the persistence issue with pictures. |
Thanks for the screenshot! Does |
It doesn't. |
Snap. I'll look into this :) |
@s-zanella you were right. I forgot to check out the correct branch. |
@s-zanella Ah, that keybinding was introduced in Emacs 25. I pushed the corresponding change. |
Thanks! Works great. |
Thanks. I'll close this then :) |
Yes, I did have a |
I merged the warnings branch. Let me know if new errors pop up :) |
This might be a design decision, but I find that opening a (new) split buffer to display error messages is a bit intrusive.
Type checking the following code in interactive-mode, it opens a new buffer to display the error instead of displaying it at the bottom of the existing buffer.
The text was updated successfully, but these errors were encountered: