Open andrewferrier opened 2 years ago
For anyone else with the same problem, as a temporary workaround I am explicitly adding vim-repeat
to my runtimepath
for vim-debugstring
to find:
vim.opt.runtimepath:append(
vim.fn.stdpath("data") .. "/site/pack/packer/start/vim-repeat"
)
Hi - I've been using
vim-debugstring
for some years now (we actually met at VimConf in London!) with Vim and more recently NeoVim.I use
vim-debugstring
fairly regularly. However, fairly recently I've noticed that dot-repeat (.
) has stopped working withvim-debugstring
.To be clear,
vim-repeat
is installed. For reference, this is how the relevant section of my packer.nvim config looks:I think I understand the issue though. These lines:
... specifically look for
vim-repeat
in theruntimepath
variable. However, they aren't there, because they are implicitly there through the use of wildcards:In my case,
vim-repeat
ends up in~/.local/share/nvim/site/pack/packer/start/vim-repeat/
. It's there, butvim-debugstring
doesn't detect it. If I comment out theif
guards that check for its existence, repeat goes back to working.I'm not sure of the right way to fix this, but it seems like the check for
vim-repeat
is too naive. I assume this problem could/would occur with Vim as well as NeoVim, maybe it just depends how a plugin manager populatesruntimepath
. I don't thinkpacker.nvim
touches it, so it's just the default value.