-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SnipLua break rule of one file one plugin. #1
Comments
Many plugins are dependent. You will not be able to do what you are going to do. You have chosen a complex folder layout. Use something simpler. P.S. |
{ |
Ideally, to follow the rule one plugin one file, lspconfig and cmp should be separated as well but it's very unlikely that you want an lsp without a completion system so it makes sense. I think it's better to break one rule to keep the benefits you're looking for! Similarly, someone working on Neovim who wants to have a snippet engine but no completion system it's probably uncommon.
I find that this system is on the contrary easier to understand and very clever. It makes maintaining and updating the configuration much simpler than the usual mess where you have to grep things to find every mention of a plugin scattered trhough the all config folder each time you just want to change the setting/disable/uninstall it. |
LuaSnip is defined in LSP/init.lua but should have a separate file (according to rule one file one plugin):
nvim/lua/packer/plugs/lsp/init.lua
Lines 10 to 19 in 0c44194
I do not know how to achieve it at this moment since I can call
cmp.setup()
only once and I want to register snippets with LSP.The text was updated successfully, but these errors were encountered: