nvim-cmp
friendly-snippets
nvim-cmp | friendly-snippets | |
---|---|---|
250 | 48 | |
7,109 | 1,678 | |
- | - | |
8.1 | 8.5 | |
8 days ago | 9 days ago | |
Lua | Lua | |
MIT License | 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.
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 :)
friendly-snippets
-
LazyVim: How to turn default plugins off?
Those definitely seem to be coming from friendly-snippets, so it seems like it's not being disabled. You can verify this with the :Lazy command to bring up the lazy.nvim menu then checking log or debug to see what is loaded, when, and why.
-
Benchmarking some of my favourite neovim plugins over time
Here you go :), tested with friendly-snippets lazy loaded (Non lazy-loaded is 500ms)
-
NormalNvim 2.0: Officially released
Snippets for code comments.
-
Enabling python's snippets.
I am trying to add snippets for python, i have LuaSnip and friendly-snippets installed, but for some reason it does not load the snippets. This is how i load the plugins:
-
PR with TSdoc support sent to friendly-snippets
I just sent [this PR](https://github.com/rafamadriz/friendly-snippets/pull/301) that implements the [full TSdoc specification](https://typedoc.org/guides/overview/) in [friently-snippets](https://github.com/rafamadriz/friendly-snippets). In practice what you get is autocompletion in your typescript comments, which should be a nice of life improvement for most typescript developers.
-
friendly-snippets VS luasnip-latex-snippets.nvim - a user suggested alternative
2 projects | 18 May 2023
-
Does anyone know how to quickly create class, interface, record, ...etc in java with nvim
You mean snippets? If yes, you can try Luasnip and friendly-snippets with nvim-cmp and here's the setup guide. Hope it helps
-
Multi-Line completion with nvim-cmp
For example Luasnip with (I guess) friendly-snippets has multi line snippets defined by default. And you can use luasnip with nvim-cmp (read the docs or I guess there’s a YouTube tutorial)
-
How to I find default snippets
If you copied the config in the readme, then the snippet come from friendly-snippets.
-
How can I get Better react intergration.
I would recommend lsp-zero, the tsserver lsp provides code actions for auto import. There is auto import when confirming completion as well, I've seen it working with cmp, however I can't remember If that is out of the box behaviour. For snippets, I would go with LuaSnip - It's very versatile snippet engine and it integrates well with many snippet formats. There are specifically react es7 snippet definitions in the friendly-snippets repo which can be used by LuaSnip - https://github.com/rafamadriz/friendly-snippets/blob/main/snippets/javascript/react-es7.json
What are some alternatives?
coc.nvim - Nodejs extension host for vim & neovim, load extensions like VSCode and host language servers.
LuaSnip - Snippet Engine for Neovim written in Lua.
cmp-nvim-lsp - nvim-cmp source for neovim builtin LSP client
vim-vsnip - Snippet plugin for vim/nvim that supports LSP/VSCode's snippet format.
coq.artifacts
snippets.nvim
completion-nvim - A async completion framework aims to provide completion to neovim's built in LSP written in Lua
ultisnips - UltiSnips - The ultimate snippet solution for Vim. Send pull requests to SirVer/ultisnips!
lspkind.nvim - vscode-like pictograms for neovim lsp completion items
rust-tools.nvim - Tools for better development in rust using neovim's builtin lsp
cmp_luasnip - luasnip completion source for nvim-cmp