Hi, On Mon, Sep 05, 2022 at 09:47:33AM +0200, Frank Scherrer wrote: > Version: 0+20220824+git7c3a88f+ds-2 > > * What led up to the situation? > An update from version 0+20220402+git3ededae+ds-3, if > snapshot.debian.org is right, there was a version in between.
(Nitpick: There were two versions in between, a -4 revision of your "good" version and a -1 revision of the "bad" one, but that is easy to miss with the version number that large and unwieldy.) > * What exactly did you do (or not do) that was effective (or > ineffective)? > I started vi and tried to move around in a file after pressing return > to all the error messages. That looks indeed bad, but sadly I can't reproduce this manually nor in the automatic tests so far. :( > Here come the error messages: > Error detected while processing CursorMoved Autocommands for "*"..function > <SNR>45_OnCursorMovedNormalMode[1]..<SNR>45_AllowedToCompleteInCurrentBuffer[1]..<SNR>45_AllowedToCompleteInBuffer: > line 12: > E117: Unknown function: youcompleteme#filetypes#AllowedForFiletype 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). 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. … 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?) 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. ;) Best regards David Kalnischkies
signature.asc
Description: PGP signature
