Hi,
On Mon, Sep 05, 2022 at 08:02:20PM +0200, David Kalnischkies wrote: > Hi, > > On Mon, Sep 05, 2022 at 09:47:33AM +0200, Frank Scherrer wrote: > > ... > > Mhhh. Which filetype (vim tells you if you type ":set filetype?") has > this buffer? Can you perhaps attach a file triggering these error for > you? Perhaps its a problem with a specific filetype/syntax file > (recently there was e.g. a bug in vims typescript syntax file, but you > have a fixed version installed already). I just open vi, no file specified, and still get the errors. So no filetype set at all. > > How are you enabling vim-youcompleteme? I recently switched the package > away from vim-addon-manager, even if it should still be technically > supported (and that was already done before your "good" -3) but perhaps > it broke in a later version. I note that the "bad" versions added a few > experimental features and with it a bit of refactoring and new files. I use vim-addon-manager > > … > > Now, I wanted to ask you to run 'vim -Nu NONE' (starting vim without any > configuration) and then run ':packadd youcompleteme' to see if it is > dependent on your local configuration, but I forgot the 'N' flag and as > a result got similar errors as you got… > Could it be that you run vim in vi compatible mode? (:set compatible?) No, it sais nocompatible. Starting vim in the way you suggested does not result in error messages, even when I add youcompleteme next. So it is my configuration, right? > > Ideally this plugin should really work regardless of compatible mode or > not, but I am not sure upstream agrees and will probably need some time > to dig into what is going on here. > Just wanting to confirm now that I am not following a red herring and > this is indeed the cause of the issue (or if I found another). > > If you are in compatible mode I suppose it is a deliberate choice as > I think it is not Debians default, but on the off chance that it is not > feel free to join the nocompatible side as a possible fix/workaround. > We have cookies. ;) I am nocompatible already ... regarding vim-configuration :-D.. So as I described above I think this is something with my vim-configuration and I digged a bit. This is, what I came up with: I can make the Errors vanish by adding a link: ~/.vim/autoload/youcompleteme -> /usr/share/vim-youcompleteme/autoload/youcompleteme If I understand https://salsa.debian.org/debian/vim-youcompleteme/-/compare/48b92f5f...master?from_project_id=26053#aa93b379d38d836d0026e27ca5e01c0bba4ac1b9_512_576 correct, then s:AllowedToCompleteInBuffer in autoload/youcompleteme.vim of the new version calls another function youcompleteme#filetypes#AllowedForFiletype( filetype ) which is in autoload/youcompleteme/filetypes So my question now is: How should I (un)configure vim-youcompleteme correctly? Thanks again in advance. > > > Best regards > > David Kalnischkies BR Frank
signature.asc
Description: PGP signature
