Open wztdream opened 3 years ago
Note that org-mode-line-string is added to buffer local setting, so seems lsp-mode need update the value of buffer local value for global-mode-string after clock-in or some other command
I don't see how that can happen considering that global-mode-string can be changed after lsp-mode. The issue will be fixed once we go away from global-mode-string as part of https://github.com/emacs-lsp/lsp-mode/issues/2571
I double checked spacemacs-mode-line it can show org-clock correctly when there is no org-mode-line-string in buffer local global-mode-string
, so seems doom-mode-line should consider show both buffer local and global value. I mentioned this in doom-mode-line too.
Thank you for the bug report
lsp-mode
related packages.where
lsp-start-plain.el
can be downloaded here.Bug description
The issue is that some times there is no org-clock in mode-line for python mode. This issue is originally reported in doom-mode-line, and finally it turns out should due to lsp-mode.
Steps to reproduce
Here is how you can reproduce it:
global-mode-string
is:It is set as a buffer local value, the global value is shadowed then, so there is no org-clock. By watching the value of
global-mode-string
it shows this buffer local value is set by lsp-mode, so I report this issue here, hope can solve it.If I clock in first then open any .py file, the org-clock shows in mode-line, and the value of
global-mode-string
is:Note that
org-mode-line-string
is added to buffer local setting, so seems lsp-mode need update the value of buffer local value forglobal-mode-string
after clock-in or some other commandExpected behavior
update
global-mode-string
after org-clock-in` or other related commands that need show information in modelineWhich Language Server did you use?
lsp-pyright
OS
Linux
Error callstack
No response
Anything else?
No response