-
-
Notifications
You must be signed in to change notification settings - Fork 449
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
echo error at point (in minibuffer) #834
Comments
Thank you for this feedback! I'm not sure, though, whether I understand you. Are you aware that Flycheck shows the error at point when you move the point to an error location? Or would rather like to have an explicit key binding to show the error at point? Do you know about the error list which automatically scrolls to and highlights the error at point? |
I think I only get that error when I use the mouse (uugh). I have |
@fommil Could you try |
@cpitclaudel oh, that does give me something in the minibuffer. Is that coming from flycheck? It seems built-in. |
Flycheck sets the That being said, flycheck also has its own mechanism for displaying errors, so placing the point on an error and waiting for a bit should show that error as well (in the minibuffer, on in a pop up if the message is long). But for the specific feature that you were asking about (a keybinding to show the current error) |
That's great! More reason for us to use flycheck when it's ready. |
Glad your problem is resolved :) But what do you mean by "when it's ready?" |
Got it, thanks! |
Document the new C-c ! h binding, fix some factual mistakes, add additional index entries and also mention C-h . See GH-834
@cpitclaudel Nice, I didn't even know about @fommil I've also added I also took the opportunity to improve the corresponding section in our manual. Please take a look and tell me if you're missing anything. Thank you very much for reporting this issue. |
cool |
ENSIME has this (with
C-c C-v e
) and it is incredibly useful. Sometimes one sees red squigglies and it's nice just to be able to get a hint about what is going wrong.The text was updated successfully, but these errors were encountered: