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
When manually running nvim -l build.lua from within the plugin root directory, the .rocks directory ends up in /run/user/1000/luarocks-* instead of within the plugin root directory.
I tested this by I adding a print statement to paths.lua on the plugin_path variable:
When executing the build directly from the plugin root, the plugin path was printed as ".", whereas when run from inside Neovim, it was printed as the full path to the plugin root directory.
I wrote some code to fix the issue and it worked here.
When manually running
nvim -l build.lua
from within the plugin root directory, the .rocks directory ends up in/run/user/1000/luarocks-*
instead of within the plugin root directory.I tested this by I adding a print statement to paths.lua on the plugin_path variable:
When executing the build directly from the plugin root, the plugin path was printed as ".", whereas when run from inside Neovim, it was printed as the full path to the plugin root directory.
I wrote some code to fix the issue and it worked here.
All I did was checking if the first char in the path is a '.' and if it is change the dot for the $PWD or CD for windows.
The text was updated successfully, but these errors were encountered: