Open ocharles opened 4 years ago
Have you changed the value of lsp-prefer-flymake
(Doom sets it to nil
by default). Flycheck shouldn't miss errors like this unless you're actually using flymake.
Could you also report the value of next-error-function
?
lsp-prefer-flymake is nil
, next-error-function
is 'flycheck-next-error-function
Strangely I just had this and it's suddenly snapped back to working, so for some reason it gets "lost" and something restores it...
Just wanted to check in and say I'm still frequently running into this. lsp-diagnostic-package
is "Pick flycheck if present and fallback to flymake". ]e
is bound to next-error
. Interestingly C-c ! n
does work, and that's flycheck-next-error
.
Having this issue too. Interestingly if I go to compilation buffer and do SPC : compilation-mode
it starts working, but only until the next compilation.
EDIT: Turned out my issue was a bad regexp that didn't match against ANSI color escape sequences which my build tool produced.
Is there any solution, I am experiencing the same issue.
I experience the same error in Python buffers, sometimes it works and sometimes it doesn't. flycheck-next-error
always works.
I had the same problem as everyone else here where C-c ! n
or flycheck-next-error
does work as expected, but ]e
or next-error
sometimes works sometimes doesn't and I think I somewhat understand the cause. next-error
will run next-error-find-buffer
to get what buffer it should look at, which isn't necessarily the currently visible buffer as you might expect. I think the reasoning for that is if you're going through errors in a file, you navigate away to view definition or something, and then do next-error and you go again to the next error in the file you were working through, not in the file you navigated away to. When I think the behaviour is just downright confusing though, is in the case where I have errors in a buffer, I fix them, no more errors in it, then I'm working in another buffer and it has flycheck errors, but next-error
says "no more flycheck errors found" because next-error-find-buffer
is actually returning the now error-free buffer I was previously working in, not the buffer I'm currently working in with underlined flycheck errors. There's a big discussion on this on the emacs mailing list here. I still don't understand exactly the next-buffer behaviour or the reasoning behind it, but I set:
(setq next-error-find-buffer-function 'next-error-buffer-unnavigated-current)
and now it mostly works as I expect it to, and in the rare case where it doesn't I can do M-x next-error-select-buffer
to manually select what buffer next-error
should use
What did you expect to happen?
My point to move between the errors in the buffer.
What actually happened?
The point did not move, and I observed the error messages in the title in the minibuffer.
Additional details:
Steps to reproduce:
System information:
My Config