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
You may also try reproduce the issue using clean environment using the following command: M-x lsp-start-plain
Bug description
#3455 inherited a bug from #3404 where it’s possible for inlay hints to be added to the wrong buffer. For example, watch the Magit buffer in this recording:
This is happening because the handler for the async request is operating on whatever the active buffer is.
Steps to reproduce
These two steps must be performed in quick succession:
Open a JavaScript or Rust file while having lsp-javascript-display-hints or lsp-rust-analyzer-server-display-hints (respectively) set to t.
Immediately switch to another buffer.
Expected behavior
Inlay hints are added to the buffer they belong to.
Which Language Server did you use?
lsp-javascript
lsp-rust
OS
Windows
Error callstack
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
shivjm
changed the title
Inlay hints added to wrong buffer when original buffer is not active
Inlay hints added to wrong buffer when original buffer is not active (lsp-javascript, lsp-rust)
Apr 12, 2022
Thank you for the bug report
lsp-mode
related packages.M-x lsp-start-plain
Bug description
#3455 inherited a bug from #3404 where it’s possible for inlay hints to be added to the wrong buffer. For example, watch the Magit buffer in this recording:
This is happening because the handler for the async request is operating on whatever the active buffer is.
Steps to reproduce
These two steps must be performed in quick succession:
lsp-javascript-display-hints
orlsp-rust-analyzer-server-display-hints
(respectively) set tot
.Expected behavior
Inlay hints are added to the buffer they belong to.
Which Language Server did you use?
lsp-javascript
lsp-rust
OS
Windows
Error callstack
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: