-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
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
Handle markdown from LSP data #3274
Comments
I've implemented basic handling for markdown formatting. Just code fences with syntax highlights for the preview window and |
I still have the off-white color in the popup |
Could you provide a screenshot? Maybe I can figure out what that is. |
I have pyright and flake8 as my linters Current Filetype: python let g:ale_python_auto_pipenv = 0 let g:ale_cache_executable_check_failures = v:null (executable check - success) flake8 <<>> (executable check - success) pyright-langserver <<>> |
That's not a bug, that's the difference between Vim popups and balloons. There's an open PR for popups here: #2925 It's held up because the author tried to implement two different uses of popups at once. One is somewhat ready to merge, the other I think will break things. You can get syntax highlighting in the preview window with |
Related to #2922, it would be nice to handle markdown data from LSP responses for features like hover information, so the relevant languages can be loaded for syntax highlighting, and certain markdown format markers or whatever LSP sends can be turned into Vim highlights.
Here's an example from a project I work on, with output taken from
pyright
:Ideally that can be rendered in a popup or preview window like this:
I'd like to write a function that accepts markup data and returns
[clean_string, highlights]
, wherehighlights
is aList
of highlights to render using Vim/NeoVim highlight functions.The text was updated successfully, but these errors were encountered: