You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
With luasnip installed, if I open up my editor with an empty file, and simply type the letter "d", I see two large popups appear. One with a list of about 15 snippet suggestions, and one that shows the contents of the first snippet in that list.
Part of the reason I'm moving back to vim from VSCode is that I personally find it quite a large hinderance when things are popping up all over the place, obscuring parts of the code, sealing focus, and so on.
Could an option be added to LuaSnip to disable these popups? And so that it can just be used to define and invoke snippets when the invocating key combination is pressed?
The text was updated successfully, but these errors were encountered:
LuaSnip does not open any popups, it is only a snippets engine.
Completions are handled by another plugin which will decide what completions are available and when.
(usually nvim-cmp nowadays)
Then another plugin is involved to add LuaSnip's snippets as a source of items to the completion engine.
It is the completion engine that is responsible for deciding when to ask sources for completion items, and displaying them in 'popups' if any.
So you should configure that, not LuaSnip
With luasnip installed, if I open up my editor with an empty file, and simply type the letter "d", I see two large popups appear. One with a list of about 15 snippet suggestions, and one that shows the contents of the first snippet in that list.
Part of the reason I'm moving back to vim from VSCode is that I personally find it quite a large hinderance when things are popping up all over the place, obscuring parts of the code, sealing focus, and so on.
Could an option be added to LuaSnip to disable these popups? And so that it can just be used to define and invoke snippets when the invocating key combination is pressed?
The text was updated successfully, but these errors were encountered: