Closed matu3ba closed 2 years ago
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 plugin
directory directly to the lua
folder. It seems like this will be a 0.6 feature, though.
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 if vim.g.loaded_libmodal
, since init.lua
s are only loaded once.
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 checkout
the branch and tell me if there are any breakages? I've tested from my side and things are fine, but it's good to check.
@Iron-E Unfortunately so far I did not configure libmodal. :( Currently I am focusing on REPL and per-project configuration and more minimal tasks, once I have some spare time.
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: https://github.com/glepnir/galaxyline.nvim/issues/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.