Hi, On Tue, Sep 06, 2022 at 10:34:46AM +0200, Emmanuel Thomé wrote: > On the other hand, enabling youcompleteme via :packadd youcompleteme > seems to work without error.
Thanks for looking into it! The problem seems indeed to effect vim-addon-manager only: Upstream added/split out two new files which I had not recorded for install by v-a-m, so it could indeed not be found. Me fixing the registry entry doesn't resolve the problem completely through as you will have to then reinstall the plugin with v-a-m (that is inherent in its design). Looks like this patch would resolve it: diff --git a/debian/vim-youcompleteme.yaml b/debian/vim-youcompleteme.yaml index 57d1c6f..b00ebad 100644 --- a/debian/vim-youcompleteme.yaml +++ b/debian/vim-youcompleteme.yaml @@ -3,5 +3,7 @@ description: fast, as-you-type, fuzzy-search code completion engine basedir: /usr/share/vim-youcompleteme files: - autoload/youcompleteme.vim + - autoload/youcompleteme/finder.vim + - autoload/youcompleteme/filetypes.vim - doc/youcompleteme.txt - plugin/youcompleteme.vim On your system the file is installed as /usr/share/vim/registry/vim-youcompleteme.yaml I will see if I can come up with a little autopkgtest to ensure not breaking that too often in the future. I suggest looking into transitioning away from v-a-m through as Debian seems to slowly do this as a whole (#1015149). Best regards David Kalnischkies
signature.asc
Description: PGP signature
