-
-
Notifications
You must be signed in to change notification settings - Fork 70
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
Option to enable inlay-hints #655
Comments
Right now we don't have granular controls for LSP/diagnostic components of Neovim itself. This is a part of the debt we inherited on fork, but I'm currently looking to close those gaps. As a temporary workaround, you can use There is #643 which I can sneak lsp configuration options into, but with Neovim 0.11 lspconfig will be obsolete, and I'd much rather rework everything then. Again, configuring it via Lua should do the trick for now. |
I will look into Appreciate the quick response! I'll leave the issue open in case you want it as a reminder of the request - That's up to you :) |
I'll keep it open as a mental note for myself, I tend to forget things otherwise 😔 |
To anyone else stumbling upon this, i got this working in the home-manager module using: programs.nvf.settings.vim.luaConfigPre = ''
vim.lsp.inlay_hint.enable(not vim.lsp.inlay_hint.is_enabled(), { bufnr })
''; |
🏷️ Feature Type
API Additions
🔖 Feature description
For rust (especially) and some other languages, it is essential for many users to have the inlay-hints introduced in nvim 0.10 enabled. However, they aren't by default. I can't seem to find a way to enable them in the Appendix.
✔️ Solution
Adding the option
vim.lsp.inlay-hint.enable
to the flake❓ Alternatives
Any other way to add to the
on_attach
function for the lsp would also suffice📝 Additional Context
I haven't been able to find an option that enables this - And i can't seem to figure out how to add it manually to the
on_attach
hook for the lsp. If there is a way to do either of these, please tell! 😄The text was updated successfully, but these errors were encountered: