Closed mimikun closed 9 months ago
Whether to include doc/tags-ja
in the repository was discussed before: https://github.com/vim-jp/vimdoc-ja-working/issues/268
At that time, we decided to include it because Vim's help recommends to do so. But, this kind of issue has been reported several times: e.g. https://github.com/vim-jp/vimdoc-ja-working/issues/1206 We might need to reconsider it? (I hope plugin managers handle this correctly, though.)
As far as I've researched, there are only a limited number of plugin managers that address this issue.
Is it possible to solve this by creating a branch (e.g. release
) for installation with the plugin manager and setting it to ignore doc/tags-ja
there?
Both dein.vim and dpp.vim also don't have the problem.
Unfortunately, there are more "bad behavior" plugins than "good behavior" plugins.
The reason that plugin managers like lazy generate doc tags for installed/updated plugins, is that 99% of the plugins do not provide doc tags, or ship outdated doc tags.
vimdoc-ja
is in the minority here.
It's also a bad idea to put doc/tags under version control, since they don't really seem to be idempotent.
I'm not planning to add any kind of exceptions for plugin managed doc tags to lazy.nvim
I was able to avoid this issue by implementing a workaround based on https://github.com/delphinus/dotfiles/blob/master/.config/nvim/lua/core/lazy/init.lua.
Thank you!
@mimikun Hmm, I believe merging the PR below resolved this issue. https://github.com/vim-jp/vimdoc-ja-working/pull/1434
Thank you. I'll try it once the changes from that commit are reflected in this repository.
It has already been reflected.
Sometimes updating vimdoc-ja fails.
I need to uninstall and reinstall again. It's very troublesome.
env
Windows
neovim