You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've updated my emacs packages, and I noticed this issue. It seems to be related (or identical) to #149, but I've been able to reproduce this in other language servers I use (clojure and rust), which leads me to believe it is a general issue with lsp-treemacs itself, and not something that depends on the language.
The problem is the following: When I open a project, LSP diagnostics work okay in the buffer, and the first time I launch lsp-treemacs-error-list, I see the correct output. If I then make any changes to my LSP setup, lsp-treemacs-error-list keeps showing the old errors indefinitely. I haven't found a way to make it refresh the contents other than restarting emacs.
This is a quick screen recording of my interaction:
I was able to successfully bisect the issue to the following commit: e668656
Unfortunately, the commit is large enough that I cannot continue debugging without a better understanding of the codebase. This seems to be a caching issue, and the fact there's multiple references to caches in the commit source makes me believe that is the case.
The text was updated successfully, but these errors were encountered:
I've updated my emacs packages, and I noticed this issue. It seems to be related (or identical) to #149, but I've been able to reproduce this in other language servers I use (clojure and rust), which leads me to believe it is a general issue with
lsp-treemacs
itself, and not something that depends on the language.The problem is the following: When I open a project, LSP diagnostics work okay in the buffer, and the first time I launch
lsp-treemacs-error-list
, I see the correct output. If I then make any changes to my LSP setup,lsp-treemacs-error-list
keeps showing the old errors indefinitely. I haven't found a way to make it refresh the contents other than restarting emacs.This is a quick screen recording of my interaction:

I was able to successfully bisect the issue to the following commit: e668656
Unfortunately, the commit is large enough that I cannot continue debugging without a better understanding of the codebase. This seems to be a caching issue, and the fact there's multiple references to caches in the commit source makes me believe that is the case.
The text was updated successfully, but these errors were encountered: