We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lsp-mode
M-x lsp-start-plain
I have this custom options set:
'(lsp-ui-doc-position 'at-point) '(lsp-ui-doc-show-with-cursor t)
When I run Graphical Emacs, everything works as expected:
But when I run Emacs on the terminal with the same options, it never shows "at-point", it dances around up and down.
Just setting:
It is not dependent of any language, it happens to all languages.
I used ts-ls and eslint, but the problem does not depend on any specific language server.
ts-ls
eslint
Linux
No error callstack.
I originally posted on Discord: https://discord.com/channels/789885435026604033/789890622424219658/1157881730246656071
Since no one could help, I am opening it as a bug.
The text was updated successfully, but these errors were encountered:
Thanks for moving it @yyoncho, It really is a lsp-ui issue.
Sorry, something went wrong.
No branches or pull requests
Thank you for the bug report
lsp-mode
related packages.M-x lsp-start-plain
Bug description
I have this custom options set:
When I run Graphical Emacs, everything works as expected:
But when I run Emacs on the terminal with the same options, it never shows "at-point", it dances around up and down.
Steps to reproduce
Just setting:
It is not dependent of any language, it happens to all languages.
Expected behavior
It is not dependent of any language, it happens to all languages.
Which Language Server did you use?
I used
ts-ls
andeslint
, but the problem does not depend on any specific language server.OS
Linux
Error callstack
No error callstack.
Anything else?
I originally posted on Discord: https://discord.com/channels/789885435026604033/789890622424219658/1157881730246656071
Since no one could help, I am opening it as a bug.
The text was updated successfully, but these errors were encountered: