Ivan Yonchovski
Ivan Yonchovski
> I've come up with a solution that works for Emacs 26 on macOS. However, this solution prevents using the mouse to focus the frame in Linux, and doesn't fix...
> @Sorixelle - can you post your findings? cc @ericdallo who will take a look.
> So I guess that's another workaround: open a new frame, close the current one. This is not an option because creating a new frame is a slow operation. But...
Most likely delated to the discussion at https://github.com/emacs-lsp/dap-mode/pull/529
> but using the `lsp-ui-doc-enable` variable I can only seem to control the state on emacs startup I don't think that this is true. After reopening the buffer lsp-ui-doc should...
`M-x toggle-debug-on-quit` and then `C-g` will show you where emacs has stopped.
You should do `M-x toggle-debug-on-quit` before calling `lsp` and press C-g when emacs stuck.
@juanluis-lightneer probably is the same issue as https://github.com/emacs-lsp/lsp-mode/issues/514 . Unfortunately, I am not a windows user and I am out of options for that issue.
I think that it might be a potential regression from https://github.com/emacs-lsp/lsp-mode/pull/1419 . Do you have steps to reproduce? (preferably over hello world application).
Can you test https://github.com/yyoncho/lsp-mode/commit/7ce3ad597b4cbc8523d7c019b6e975a45354e4e3 ? I believe that the issue was that we do not flush delayed changes before sending notifications.