vim-vsnip VS lspkind.nvim

My go to these days has been https://github.com/hrsh7th/vim-vsnip. It is compatible with LSP and VSCode snippet format. Since it is in pure VimScript you don’t need to battle configuring python just to get the plug-in to work.

I first started by reading some tutorials but most of those used parser combinators. For me, parser combinators always caused some issues sooner or later (at least in Lua when trying to parse recursive / nested nodes). An example project that uses this technique is vim-vsnip: https://github.com/hrsh7th/vim-vsnip/blob/master/autoload/vsnip/snippet/parser.vim. Later, I found out that Luacheck uses a different approach which I liked better: https://github.com/lunarmodules/luacheck/blob/master/src/luacheck/parser.lua. That's the project that helped me the most while writing my own parsers for different snippet engines.

This plugin could use it? hrsh7th/vim-vsnip

I am not a snippets expert, I don't even currently use snippets. However, I know that both LuaSnip and vim-vsnip can load these vscode style snippets. So my recommendation would be to get the snippets and use one of those two snippet plugins.

For autocompletion I use the nvim-cmp plugin. If you're not coding, it might be overkill. But during writing it helps me a lot, because it autosuggests words that I used in the current buffer, too. The most popular autocomplete plugins should be compatible with the most popular snippets engines like vim-vsnip.

Have you ever wondered how to have a snippet completion in VSCode so you can write Julia code fast but in Neovim? Fear not! vim-vsnip is the plugin you need. This plugin supports LSP/VSCode's snippet format. But first, you need to install cmp-vsnip for this plugin to be sourced to nvim-cmp. Oh btw, these three plugins: nvim-cmp, vim-vsnip, and cmp-vsnip → are made by the same person which is actually cool! If you want to support them, become a sponsor! (I am poor so I cannot sponsor yet 😔)

I believe you want the second variant. Then you should install some snippet plugin like vsnip or luasnip and config it with your completion engine.

https://github.com/hrsh7th/vim-vsnip says it supports vscode style snippets, so apparently you could use https://marketplace.visualstudio.com/items?itemName=kaffeine.advanced-drupal-8-snippets with that plugin.

There's a cmp-icons plugin: https://github.com/onsails/lspkind.nvim and also you can see the cmp documentation inside vim running :h cmp I spend many hours reading each plugin documentation to customize all my plugins. I hope I've helped.

If you are referring specifically to icons in your autocompletion suggestions menu you have to set it to use them. This can be achieved manually with the format key in the nvim-cmp setup (assuming you are using nvim-cmp) or with a plugin like lspkind.nvim

If you use neovim, you can refer to my init.lua; I use vim-go, lsp and other goodies like lspkind to display vscode-like pictograms.

-- Provide some indication that rust-analyzer is busy! local lsp_status = require('lsp-status') lsp_status.register_progress() -- Basic rust/lsp/cmp settings from https://sharksforarms.dev/posts/neovim-rust/ local nvim_lsp = require('lspconfig') local opts = { tools = { -- rust-tools options autoSetHints = true, hover_with_actions = true, inlay_hints = { show_parameter_hints = false, parameter_hints_prefix = "", other_hints_prefix = "=> ", }, }, -- all the opts to send to nvim-lspconfig -- these override the defaults set by rust-tools.nvim -- see https://github.com/neovim/nvim-lspconfig/blob/master/doc/server_configurations.md#rust_analyzer server = { -- on_attach is a callback called when the language server attachs to the buffer on_attach = lsp_status.on_attach, capabilities = lsp_status.capabilities, settings = { -- to enable rust-analyzer settings visit: -- https://github.com/rust-analyzer/rust-analyzer/blob/master/docs/user/generated_config.adoc -- and more: https://github.com/simrat39/rust-tools.nvim/wiki/Server-Configuration-Schema ["rust-analyzer"] = { -- enable clippy on save checkOnSave = { command = "clippy" }, } } }, } require('rust-tools').setup(opts) -- Setup Completion -- See https://github.com/hrsh7th/nvim-cmp#basic-configuration -- Used for super-tab functionality local has_words_before = function() local line, col = unpack(vim.api.nvim_win_get_cursor(0)) return col ~= 0 and vim.api.nvim_buf_get_lines(0, line - 1, line, true)[1]:sub(col, col):match("%s") == nil end local feedkey = function(key, mode) vim.api.nvim_feedkeys(vim.api.nvim_replace_termcodes(key, true, true, true), mode, true) end local lspkind = require('lspkind') local cmp = require'cmp' cmp.setup({ completion = { autocomplete = true }, -- Enable LSP snippets snippet = { expand = function(args) vim.fn["vsnip#anonymous"](args.body) end, }, mapping = { [''] = cmp.mapping.select_prev_item(), [''] = cmp.mapping.select_next_item(), [''] = cmp.mapping.scroll_docs(-4), [''] = cmp.mapping.scroll_docs(4), [''] = cmp.mapping.complete(), [''] = cmp.mapping.close(), [''] = cmp.mapping.confirm({ behavior = cmp.ConfirmBehavior.Insert, select = true, }), -- Add tab support [""] = cmp.mapping(function(fallback) if cmp.visible() then cmp.select_next_item() elseif vim.fn["vsnip#available"](1) == 1 then feedkey("(vsnip-expand-or-jump)", "") elseif has_words_before() then cmp.complete() else fallback() -- The fallback function sends a already mapped key. In this case, it's probably ``. end end, { "i", "s" }), [""] = cmp.mapping(function() if cmp.visible() then cmp.select_prev_item() elseif vim.fn["vsnip#jumpable"](-1) == 1 then feedkey("(vsnip-jump-prev)", "") end end, { "i", "s" }), }, -- Installed sources sources = { { name = 'nvim_lsp' }, --, trigger_characters={'.', ":"} }, { name = 'vsnip' }, { name = 'path' }, { name = 'buffer' }, { name = 'nvim_lsp_signature_help' }, { name = 'nvim_lsp_document_symbol' }, }, -- Fancy symbols formatting = { format = lspkind.cmp_format({ mode = 'symbol_text', -- show both symbol & text for now maxwidth = 50, -- prevent the popup from showing more than provided characters (e.g 50 will not show more than 50 characters) -- The function below will be called before any actual modifications from lspkind -- so that you can provide more controls on popup customization. (See [#30](https://github.com/onsails/lspkind-nvim/pull/30)) --before = function (entry, vim_item) --... --return vim_item --end }) }, completion = { autocomplete = true }, })

All the snippets, mapping, formatting and sources part in the above code snippet is expalained nicely in the plugin's documentation. For above code to work, you also have to install lspkind which provides awesome icons in the code completions.

To style the completion popup, you need to add formatting. Going by the cute little scissors, you probably want to install lsp-kind and add something like this to your cmp.setup

https://github.com/onsails/lspkind-nvim (optionally)

I copy pasted the icons from https://github.com/onsails/lspkind-nvim/blob/master/lua/lspkind/init.lua and added the spaces: