-
Notifications
You must be signed in to change notification settings - Fork 7
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
consider move initialization to lua #10
Comments
Thanks for your interest in this plugin! I will say that I am interested in doing this, since I love Lua. I have been waiting for neovim/neovim#12670 to be resolved before implementing something like this, so I can map the I wonder if putting this logic in the init.lua could be equivalent for our purposes. This would be like lazy-loading and also would be backwards compatible with Neovim 0.4+. We wouldn't need At the moment I'm chugging away on CLInvoice so I'll have to put this on the backlog for now, but I will pick this back up to see what I can see in a little bit! |
I have added a branch which implements this feature. I will merge it after the release of 0.5; feel free to test it! |
I'm getting ready to merge the branch. Can you |
@Iron-E Unfortunately so far I did not configure libmodal. :( |
We now use Lua init as of 2.0.0 Thank you again for the sugggestion! |
I like the plugin very much. Thanks alot for creating! Since you do setups functional anyway, why not provide one for your plugin initialisation?
This would enable stuff like conditional setups for users etc.
Reasons to do:
Another related reason (bad practice/historical reasons): nvim-treesitter/module-template#1
Potentially related discussion for galaxyline: nvimdev/galaxyline.nvim#134
Relevant content for change:
Of course you could also use the more optimal vim.api functions for setting and getting variables as described in the nvim-lua-guide.
The text was updated successfully, but these errors were encountered: