Open ocharles opened 4 years ago
hlissner
commented
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?
ocharles
commented
4 years ago lsp-prefer-flymake is nil, next-error-function is 'flycheck-next-error-function
ocharles
commented
4 years ago Strangely I just had this and it's suddenly snapped back to working, so for some reason it gets "lost" and something restores it...
ocharles
commented
4 years ago 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.
yglukhov
commented
4 years ago 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.
lucafanselau
commented
2 years ago Is there any solution, I am experiencing the same issue.
d-miketa
commented
2 years ago I experience the same error in Python buffers, sometimes it works and sometimes it doesn't. flycheck-next-error always works.
bo-tato
commented
1 year ago 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
;;; init.el -*- lexical-binding: t; -*- (doom! :input :completion (company +childframe) (ivy +icons +prescient) :ui doom ; what makes DOOM look the way it does doom-dashboard ; a nifty splash screen for Emacs doom-quit ; DOOM quit-message prompts when you quit Emacs hl-todo ; highlight TODO/FIXME/NOTE/DEPRECATED/HACK/REVIEW modeline ; snazzy, Atom-inspired modeline, plus API nav-flash ; blink the current line after jumping ophints ; highlight the region an operation acts on (popup ; tame sudden yet inevitable temporary windows +all ; catch all popups that start with an asterix +defaults) ; default popup rules vc-gutter ; vcs diff in the fringe (window-select +switch-window) ; visually switch windows workspaces ; tab emulation, persistence & separate workspaces :editor (evil +everywhere); come to the dark side, we have cookies file-templates ; auto-snippets for empty files fold ; (nigh) universal code folding rotate-text ; cycle region at point between text candidates :emacs dired ; making dired pretty [functional] electric ; smarter, keyword-based electric-indent ibuffer ; interactive buffer management vc ; version-control and Emacs, sitting in a tree :term vterm :checkers (syntax +childframe) :tools direnv (lookup ; helps you navigate your code and documentation +docsets) ; ...or in Dash docsets locally lsp magit :lang data ; config/data formats (elm +lsp) ; care for a cup of TEA? emacs-lisp ; drown in parentheses (haskell +lsp) ; a language that's lazier than I am javascript ; all(hope(abandon(ye(who(enter(here)))))) markdown ; writing docs for people to ignore nix ; I hereby declare "nix geht mehr!" (org ; organize your plain life in plain text +attach ; custom attachment system +babel ; running code in org +capture ; org-capture in and outside of Emacs +export ; Exporting org to whatever you want +present) ; Emacs for presentations rst sh ; she sells (ba|z)sh shells on the C xor :email :app :config (default +bindings +smartparens)) (custom-set-variables ;; custom-set-variables was added by Custom. ;; If you edit it by hand, you could mess it up, so be careful. ;; Your init file should contain only one such instance. ;; If there is more than one, they won't work right. '(ansi-color-names-vector ["#21242b" "#e45649" "#50a14f" "#986801" "#4078f2" "#a626a4" "#0184bc" "#383a42"]) '(custom-safe-themes (quote ("728eda145ad16686d4bbb8e50d540563573592013b10c3e2defc493f390f7d83" "2d1fe7c9007a5b76cea4395b0fc664d0c1cfd34bb4f1860300347cdad67fb2f9" "2d392972cbe692ee4ac61dc79907af65051450caf690a8c4d36eb40c1857ba7d" "34c99997eaa73d64b1aaa95caca9f0d64229871c200c5254526d0062f8074693" "ab9456aaeab81ba46a815c00930345ada223e1e7c7ab839659b382b52437b9ea" default))) '(fci-rule-color "#383a42") '(jdee-db-active-breakpoint-face-colors (cons "#f0f0f0" "#4078f2")) '(jdee-db-requested-breakpoint-face-colors (cons "#f0f0f0" "#50a14f")) '(jdee-db-spec-breakpoint-face-colors (cons "#f0f0f0" "#9ca0a4")) '(objed-cursor-color "#e45649") '(vc-annotate-background "#fafafa") '(vc-annotate-color-map (list (cons 20 "#50a14f") (cons 40 "#688e35") (cons 60 "#807b1b") (cons 80 "#986801") (cons 100 "#ae7118") (cons 120 "#c37b30") (cons 140 "#da8548") (cons 160 "#c86566") (cons 180 "#b74585") (cons 200 "#a626a4") (cons 220 "#ba3685") (cons 240 "#cf4667") (cons 260 "#e45649") (cons 280 "#d2685f") (cons 300 "#c07b76") (cons 320 "#ae8d8d") (cons 340 "#383a42") (cons 360 "#383a42"))) '(vc-annotate-very-old-color nil)) (custom-set-faces ;; custom-set-faces was added by Custom. ;; If you edit it by hand, you could mess it up, so be careful. ;; Your init file should contain only one such instance. ;; If there is more than one, they won't work right. )