-
Notifications
You must be signed in to change notification settings - Fork 14
bug: the plugin directly sources .nvim.lua #44
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
Comments
exrc.mov |
The error shows up immediately on my screen without any other actions. Perhaps this is a difference between 0.11 release and 0.12-dev? |
Here is the example with 0.11, but I notice that you using windows, I don't have win to test :/ exrc.mov |
Oh, I completely forgot to mention the contents of .nvim.lua! -- .nvim.lua
vim.cmd [[MyCommand]] |
Should be fixed, in case you still have an issue re-open this one. |
The fix doesn't seem quite right. Calling Also, the bug I'm reporting is that 'the plugin directly sources .nvim.lua' instead of letting the regular neovim processes source the file. The file gets executed twice in total. I'm not sure what the fix is to get your plugin to work the way you want it to. Perhaps there's an event one could hook into that triggers after reading the .nvim.lua file. |
I agree, this was dirty hack, but the lazy doesn't actually wait for the all runtimes to start, so that was the reason why I have to manually source local |
Neovim version (nvim -v)
NVIM v0.11.0
Error Message
Failed to run
config
for nvim-html-cssvim/_editor.lua:447: C:\Users\shifty\minimal.lua..nvim_exec2() called at C:\Users\shifty\minimal.lua:0, line 1: Vim:E492: Not an editor command: MyCommand echo hello
stacktrace:
Steps To Reproduce
Minimal Configuration
Related Plugins
Additional Information
See
:h 'exrc'
The .nvim.lua file is already sourced by neovim at a later time in the startup sequence and it only does so if the user has set exrc and the .nvim.lua file is in the trusted list. Your plugin should not be sourcing that file directly.
The text was updated successfully, but these errors were encountered: