-
Notifications
You must be signed in to change notification settings - Fork 109
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
Blank line at the top(or bottom) of lsp window and no way remove it #158
Comments
You are right, that makes sense. |
In the default Neovim lsp markdown renderer, we strip the begininig and end of code blocks and use The new Noice markdown renderer uses Treesitter under the hood, since it is by far superior in terms of highlighting and concealing, but the Treesitter highlighter currently doesn't support highlighting regions. I'm planning to make a PR upstream to make this possible. Once that's done, I can use that to strip those lines. |
There's no way to caculate the concealed str width as far as I know. So that's why the window width is wider |
Indeed, it's a small problem, does't affecting the rest of the awesome features |
couldn't this be done with injections @folke or have I missunderstood something? |
@max397574 what do you mean? The markdown code blocks are using injections. Either we need anti-conceal to remove lines from the buffer, or we need a way to highlight a region with treesitter. The last option is what I'm going to see to implement upstream. |
I thought with the "highlight a region" you meant sth like injections |
Sorry to comment on an old issue, but what is the current state of this? Judging by the "Closed" status I guess it's solved somehow, but I can't seem to configure it properly. I've been trying to figure it out for several hours now, but I still get the empty (concealed) lines in the hover pop-ups (in Rust, with rustaceanvim) no matter what configuration I try. Right now I use the default config that is used in LazyVim. |
Hover
Signature
Completion
The text was updated successfully, but these errors were encountered: