Skip to content

UI broken after code action #1229

@stfl

Description

@stfl

I recently started using lsb-bridge via doom emacs.

After requesting a code action, from rust-analyzer, the code-action is applied to the buffer.
Keyboard inputs to the emacs frame do not work and the cursor (point) is not visible.
Mouse input does work and I can move point, indicated by hl-line but the actual point is not shown.
M-x or moving point with the keyboard does not work.

I have another frame open (for org-mode) which works as usual.
Closing the affected frame and opening the project in a new frame resolves the issue.
The buffer is edited but not saved.

In the lsp-bridge buffer I can see that I received an response for the code action and successive requests for textDocument/didChange and so on.

Is there a way to debug this situation?
How can I reset the UI in the affected frame?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions