none-ls and luasnip completion #130
ikirudennis
started this conversation in
General
Replies: 1 comment 1 reply
-
You don't need This is only useful when your completion plugin doesn't support LuaSnip (e.g. mini.complete). |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I've been a longtime vim user, and have been working on migrating my setup over to neovim. I followed some youtube tutorials on how to get lsp and completion working, but I ran into some trouble with trying to enable the none-ls builtin completion for luasnip.
I spent some time digging into this, and I eventually found that this line:
none-ls.nvim/lua/null-ls/builtins/completion/luasnip.lua
Line 47 in 3767179
detail
to be a string. I also tried looking into the file history, but the line linked above pre-dates luasnip 1.0.0, so it's hard to say whatdetail
ordescription
were really intended to do. I found that either commenting out the linked line or changing it tosnip.description[1]
was effective at getting none-ls to work as a completion system. But ultimately, I found it to be redunant, and luasnip was actually providing snippets properly, so I just removednull_ls.builtins.completion.luasnip
from my config.This raises a few questions:
snip.description[1]
or maybe hard-coding the detail to"none-ls luasnip completion"
so a user can at least know which completion system is producing the given snippet (This is one change I tried to confirm which snippet system was causing trouble)? The description is included in the documentation, so it's a bit redundant.null_ls.builtins.comnpletion.luasnip
even needed anymore?Beta Was this translation helpful? Give feedback.
All reactions