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

Closed
fommil opened this Issue Jan 1, 2016 · 11 comments

Comments

Projects
None yet
3 participants
@fommil

fommil commented Jan 1, 2016

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.

@lunaryorn

This comment has been minimized.

Contributor

lunaryorn commented Jan 1, 2016

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?

@fommil

This comment has been minimized.

fommil commented Jan 1, 2016

I think I only get that error when I use the mouse (uugh). I have eldoc installed too and I think it tends to win the race to the minibuffer.

@cpitclaudel

This comment has been minimized.

Member

cpitclaudel commented Jan 1, 2016

@fommil Could you try C-h . on an error?

@fommil

This comment has been minimized.

fommil commented Jan 1, 2016

@cpitclaudel oh, that does give me something in the minibuffer. Is that coming from flycheck? It seems built-in.

@cpitclaudel

This comment has been minimized.

Member

cpitclaudel commented Jan 1, 2016

Flycheck sets the help-echo property on errors, so pressing C-h . (which is by default bound to display-local-help) does show the Flycheck error which the point is on.

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) C-h . should do :)

@fommil

This comment has been minimized.

fommil commented Jan 1, 2016

That's great! More reason for us to use flycheck when it's ready.

@fommil fommil closed this Jan 1, 2016

@cpitclaudel

This comment has been minimized.

Member

cpitclaudel commented Jan 1, 2016

Glad your problem is resolved :) But what do you mean by "when it's ready?"

@fommil

This comment has been minimized.

fommil commented Jan 1, 2016

@cpitclaudel

This comment has been minimized.

Member

cpitclaudel commented Jan 1, 2016

Got it, thanks!

lunaryorn added a commit that referenced this issue Jan 2, 2016

lunaryorn added a commit that referenced this issue Jan 2, 2016

Improve error display section
Document the new C-c ! h binding, fix some factual mistakes, add
additional index entries and also mention C-h .

See GH-834

@lunaryorn lunaryorn added question and removed status: blocked labels Jan 2, 2016

@lunaryorn

This comment has been minimized.

Contributor

lunaryorn commented Jan 2, 2016

@cpitclaudel Nice, I didn't even know about C-h . ☺️

@fommil I've also added C-c ! h as a new binding which explicitly invokes Flycheck's error display for the error at point. Unlike C-h . it uses whatever is configured for Flycheck's error display, so if you're using flycheck-pos-tip you'll get a GUI popup instead of an echo area message. C-h . will always use the minibuffer.

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.

@fommil

This comment has been minimized.

fommil commented Jan 2, 2016

cool

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment