Copy local plugin directory to remote #190
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I recently got into trying out plugin development for neovim in order to improve my workflow.
To do so I use a local plugins folder that is then used by
lazy.nvim
instead of pulling from github. In order to be able to use these plugins in remote environments, I thus need to copy them over onto the remote, and havelazy.nvim
correctly configure the path there.Thus:
lazy.nvim
as follows to use the proper path on the remote.vim.g.remote_neovim_unique_host_id
to store the name of the running container, which can then be displayed when running any neovim instance connected to the remote. This is helpful when using multiple containers simultaneously to keep track of them.For example for 'mini.nvim'
Retrospectively it might have been better to implement a mechanism to copy any directory onto the remote, not just something specific to the local plugins.
What do you think?