I was trying to debug an issue with https://github.com/neo451/feed.nvim (it creates folders in current directory instead of in stdconfig("data")).
I enabled dev mode with https://github.com/lumen-oss/rocks-dev.nvim:
[plugins."feed.nvim"]
# version = "2.19.2"
dev = true
dir = "/home/teto/neovim/feed.nvim"
and witnessed incoherent behavior (I would remove a file/function yet neovim could still load it).
Turns out neovim would load the code from /home/teto/.local/share/nvim/rocks/rocks_rtp/feed.nvim, done by
|
return create_symlink_sync(site_link_dir, rock.name, rock_version_dir) |
I am not sure what a proper fix is, can we skip symlinking it if the plugin is in dev mode for instance ?
Not sure if it's the same as #497
I was trying to debug an issue with https://github.com/neo451/feed.nvim (it creates folders in current directory instead of in stdconfig("data")).
I enabled dev mode with https://github.com/lumen-oss/rocks-dev.nvim:
and witnessed incoherent behavior (I would remove a file/function yet neovim could still load it).
Turns out neovim would load the code from /home/teto/.local/share/nvim/rocks/rocks_rtp/feed.nvim, done by
rocks.nvim/lua/rocks/adapter.lua
Line 154 in cfacf14
I am not sure what a proper fix is, can we skip symlinking it if the plugin is in dev mode for instance ?
Not sure if it's the same as #497