-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
doom-modeline checker segment fails to report flymake errors #14133
Comments
I have this issue also. The checker doesn't reflect flychecker errors/warnings like you described. I tested this in the init.el config file and also in some Clojure code. |
@zane |
I can also confirm this with Javascript, lsp-mode and flycheck (lsp-mode linting disabled). The segment in the mode line showing errors always show 0 if there are any errors and a green tick if there are none. Switching the mode-line to spacemacs default and errors are shown correctly. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Please let us know if this issue is still valid! |
Still an issue! |
I cannot reproduce this with the newest doom-modeline, perhaps it works since seagle0128/doom-modeline@2001454? It works correctly for both values of |
@zane please double check with the latest package versions. |
Description
doom-modeline
checker
segment does not include errors.Reproduction guide 🪲
The instructions below are for triggering an elisp error, but I believe this bug can be reproduced with any flycheck error.
I could not reproduce this bug on a vanilla Emacs configuration, so I believe this is not an issue upstream.
.spacemacs
setdotspacemacs-mode-line-theme
to'doom
.spacemacs
addsyntax-checking
todotspacemacs-configuration-layers
.el
file, insertx)
, and save.flycheck-mode
for the.el
file buffer.SPC e l
and note that flycheck is indeed reporting 5 info messages, 1 warning, and 1 error.Observed behaviour: 👀 💔
The
checker
segment in the modeline shows ":no_entry_sign: 0".Expected behaviour: ❤️ 😄
The
checker
segment in the modeline shows ":no_entry_sign: 7".System Info 💻
Backtrace 🐾
Not applicable.
The text was updated successfully, but these errors were encountered: