lsp-inlayhints.nvim
nvim-cmp
lsp-inlayhints.nvim | nvim-cmp | |
---|---|---|
19 | 250 | |
423 | 7,154 | |
- | - | |
3.9 | 8.1 | |
11 months ago | 6 days ago | |
Lua | Lua | |
Apache License 2.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
lsp-inlayhints.nvim
-
Help needed with setting up inlay hints
Thanks for the reply! I also wanted to make it work with clangd, but it won't. I stumbled upon this issue. Maybe you have enough knowledge to figure this out, I don't know how to set up this compilation database. I installed clangd using Mason, and configured it via lspconfig basically the same way as the guy in the issue I linked did. Also, I'm using the newest nightly.
-
Forking of rust-tools.nvim
I don't understand why inlay hints must be implemented in a rust-specific plugin. https://github.com/lvimuser/lsp-inlayhints.nvim exists, has support for inline inlay hints (on a separate branch for now) and works with rust (and should work any language server since inlay hints are part of the spec). Am I missing something?
-
feat(ui): inline virtual text #20130 just merged
To use inlay hints in typescript an rust you would need this plugin: https://github.com/lvimuser/lsp-inlayhints.nvim It provides example in the readme on how to setup inlay hints for typescript and rust. For now the master brach has "old" inlay hints implementation but there is a branch that implement new one. And of course you will need nightly version for that for now.
-
rust-analyzer changelog #181
https://github.com/lvimuser/lsp-inlayhints.nvim (Multiple langs)
-
How to enable inlay hints for ocamllsp?
But it doesn't seem to work. I also tried lvimuser/lsp-inlayhints.nvim with no luck. Any advice of how to properly enable this feature when ocamllsp server is attached? Thank you in advance.
-
Help with finding a plugin & workflow
I have inlay hints working in nvim with lvimuser/lsp-inlayhints.nvim, no special configuration other than the LspAttach block from their README. The caveat is that your LSP server has to support inlay hints.
-
Please inform me of the plugin(s) enabling these two features
The second one might be https://github.com/lvimuser/lsp-inlayhints.nvim
-
tsserver configuration options
you can use nvim-lspcofig for LSP support, mason.nvim for installing LSP servers, linters, formatters and debug adapters. nvim-cmp for completions, luasnip for snippets, null-ls for configuring your formatter and linters , lsp-inlayhints for inlay hints.
-
getting inline rust analyzer error hints with neovim
Inlay hints are available through rust-tools.nvim, or lsp-inlayhints.nvim.
-
Is it possible to get inlay hints with Omnisharp?
iirc, inlay hints aren't supported by nvim's built-in LSP, but you can get them with the inlay-hints plugin: https://github.com/lvimuser/lsp-inlayhints.nvim (if the LSP for omnisharp also supports them)
nvim-cmp
-
What is this red color in cmp?
vim.api.nvim_set_hl(0, "PmenuSel", { bg = c.background_light, fg = "NONE" }) vim.api.nvim_set_hl(0, "Pmenu", { fg = c.foreground, bg = c.background_light }) vim.api.nvim_set_hl(0, "CmpItemAbbrDeprecated", { fg = c.foreground_light, bg = "NONE", strikethrough = true }) vim.api.nvim_set_hl(0, "CmpItemAbbrMatch", { fg = c.blue , bg = "NONE", bold = true }) vim.api.nvim_set_hl(0, "CmpItemAbbrMatchFuzzy", { fg = c.blue, bg = "NONE", bold = true }) vim.api.nvim_set_hl(0, "CmpItemMenu", { fg = c.purple, bg = "NONE", italic = true }) vim.api.nvim_set_hl(0, "CmpItemKindField", { fg = c.red }) vim.api.nvim_set_hl(0, "CmpItemKindProperty", { fg = c.red }) vim.api.nvim_set_hl(0, "CmpItemKindEvent", { fg = c.red }) vim.api.nvim_set_hl(0, "CmpItemKindText", { fg = c.green }) vim.api.nvim_set_hl(0, "CmpItemKindEnum", { fg = c.green }) vim.api.nvim_set_hl(0, "CmpItemKindKeyword", { fg = c.green }) vim.api.nvim_set_hl(0, "CmpItemKindConstant", { fg = c.yellow }) vim.api.nvim_set_hl(0, "CmpItemKindConstructor", { fg = c.yellow }) vim.api.nvim_set_hl(0, "CmpItemKindReference", { fg = c.yellow }) vim.api.nvim_set_hl(0, "CmpItemKindFunction", { fg = c.purple }) vim.api.nvim_set_hl(0, "CmpItemKindStruct", { fg = c.purple }) vim.api.nvim_set_hl(0, "CmpItemKindClass", { fg = c.purple }) vim.api.nvim_set_hl(0, "CmpItemKindModule", { fg = c.purple }) vim.api.nvim_set_hl(0, "CmpItemKindOperator", { fg = c.purple }) vim.api.nvim_set_hl(0, "CmpItemKindVariable", { fg = c.foreground }) vim.api.nvim_set_hl(0, "CmpItemKindFile", { fg = c.foreground }) vim.api.nvim_set_hl(0, "CmpItemKindUnit", { fg = c.orange }) vim.api.nvim_set_hl(0, "CmpItemKindSnippet", { fg = c.orange }) vim.api.nvim_set_hl(0, "CmpItemKindFolder", { fg = c.orange }) vim.api.nvim_set_hl(0, "CmpItemKindMethod", { fg = c.blue }) vim.api.nvim_set_hl(0, "CmpItemKindValue", { fg = c.blue }) vim.api.nvim_set_hl(0, "CmpItemKindEnumMember", { fg = c.blue }) vim.api.nvim_set_hl(0, "CmpItemKindInterface", { fg = c.aqua }) vim.api.nvim_set_hl(0, "CmpItemKindColor", { fg = c.aqua }) vim.api.nvim_set_hl(0, "CmpItemKindTypeParameter", { fg = c.aqua }) -- https://github.com/hrsh7th/nvim-cmp/pull/1689 vim.api.nvim_set_hl(0, 'FloatBorder', { fg = c.background_light, bg = c.background_light })
-
cmp border background is changed all of a sudden.
Doing a fast scan on the commit history this is probably related to https://github.com/hrsh7th/nvim-cmp/pull/1689 . Hope it helps.
-
Do I need NeoVIM?
https://github.com/hrsh7th/nvim-cmp This is an autocompletion engine https://github.com/nvim-treesitter/nvim-treesitter This allows NeoVim to install parsing scripts so NeoVim can do things like code highlighting. https://github.com/williamboman/mason.nvim Not strictly necessary, but allows you to access a repo of LSP, install them, and configure them for without you actively messing about in config files. https://github.com/neovim/nvim-lspconfig Also not strictly necessary, but vastly simplifies LSP setup. https://github.com/williamboman/mason-lspconfig.nvim This lets the above two plugins talk to each other more easily.
-
Can't go down when writing a command nvim
Edit: Solved I only had to do this
-
What is your most anticipated PR?
toggling sources by Treesitter context
-
About some deprecations in Neovim core
But today I'm a different person, and I'm sure that this is the right decision. I already gave a spiel on the cmp PR, but lemme copy-paste my response for those that weren't following the issue or don't check their GitHub notifications:
-
nvim starts multiple node processes leading to very high memory usage
EDIT: I was able to reproduce the issue with a simplified nvim-cmp init.vim - posted here: https://github.com/hrsh7th/nvim-cmp/issues/1728
-
[Need Help]: I am having trouble getting autocomplete with clangd.
You need to add nvim-cmp and cmp-nvim-lsp
-
is it possible to limit the size of nvim-cmps autocompletion window?
one thing that always annoyed me is how the autocomplete window behaves. when the space below your current line isn't sufficient it just teleports above the line. i know you can set a custom menu direction but i'd much rather have it pop up in a consistent place that is below the current line. the other behavior i dislike is the sizing. it's as big as the longest function in the list which can make the window enormous, to the point where there's almost no place left for the docs window. there aren't really any docs in the example below but i imagine with the little space that is left it'll get troublesome for more verbose docs such as with rust. i'd like to somehow tell nvim-cmp to always pop up below the current line, no matter how long the list is and possibly limit the horizontal size. is that at all possible? i've looked through the nvim-cmp wiki but haven't found an adequate solution. does this go beyond nvim-cmp?
-
Toggling the nvim-cmp documentation window
Update: This isn't currently supported by nvim-cmp (and in fact it has been a feature request for a bit) and so I did my best and opened a PR that implements it :)
What are some alternatives?
aerial.nvim - Neovim plugin for a code outline window
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
guess-indent.nvim - Automatic indentation style detection for Neovim
cmp-nvim-lsp - nvim-cmp source for neovim builtin LSP client
inlay-hints.nvim - almost not wip
coq.artifacts
incline.nvim - 🎈 Floating statuslines for Neovim, winbar alternative
completion-nvim - A async completion framework aims to provide completion to neovim's built in LSP written in Lua
barbecue.nvim - A VS Code like winbar for Neovim
LuaSnip - Snippet Engine for Neovim written in Lua.
gopher.nvim - Neovim plugin for make golang development easiest
rust-tools.nvim - Tools for better development in rust using neovim's builtin lsp