Bug#1035044: autorandr: recommend libinput-tools missing
Hi On Fri, Apr 28, 2023 at 04:33:50PM -0700, Don Armstrong wrote: > We currently aren't distributing (or installing) autorandr-lid-listener > in the Debian package. My bad. You are right, I was not talking about the package included in debian. Did not realize/remember that I had the package built myself from some instructions on github. Thanks for looking into it! signature.asc Description: PGP signature
Bug#1035044: autorandr: recommend libinput-tools missing
Package: autorandr Version: 1.12.1-27-g4653ea6 Severity: minor Dear Maintainer, first: Thanks for your work, I was missing a tool like autorandr dearly and was so glad I found it. That was years ago. * What led up to the situation? I detected and stored two differend setups of Monitors, both connected to docking-station and external monitor. One with lid closed, one with lid open. * What exactly did you do (or not do) that was effective (or ineffective)? Opening or closing the lid. * What was the outcome of this action? No change of Displays Configuration * What outcome did you expect instead? Change of Displays Configuration * Additional Info apart from default questions Systemd-Service autorandr-lid-listener failed with error: In the journal of autorandr-lid-listener I found autorandr[51936]: stdbuf: failed to run command ‘libinput’: No such file or directory So I installed libinput-tools. Afterwards I could get the service started and the Configuration changed after opening/closing the lid. I suggest to put libinput-tools into the list of recommended packages. Does this sound reasonable? cheers Frank signature.asc Description: PGP signature
Bug#1019188: vim-youcompleteme makes vim show many error messages on start and while using
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
Bug#1019188: vim-youcompleteme makes vim show many error messages on start and while using
Package: vim-youcompleteme Version: 0+20220824+git7c3a88f+ds-2 Severity: normal Dear Maintainer, I think I have discovered an Issue with the latest version of vim-youcompleteme: * 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. * 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. * What was the outcome of this action? The error messages occurred and reoccurred. * What outcome did you expect instead? No errors. Here come the error messages: Error detected while processing CursorMoved Autocommands for "*"..function 45_OnCursorMovedNormalMode[1]..45_AllowedToCompleteInCurrentBuffer[1]..45_AllowedToCompleteInBuffer: line 12: E117: Unknown function: youcompleteme#filetypes#AllowedForFiletype Press ENTER or type command to continue E117: Unknown function: youcompleteme#filetypes#AllowedForFiletype Press ENTER or type command to continue Error detected while processing CursorMoved Autocommands for "*"..function 45_OnCursorMovedNormalMode[1]..45_AllowedToCompleteInCurrentBuffer[1]..45_AllowedToCompleteInBuffer[12]..45_PollServerReady[14]..45_OnFileTypeSet[8]..45_AllowedToComplet eInCurrentBuffer[1]..45_AllowedToCompleteInBuffer: line 14: E121: Undefined variable: allowed Press ENTER or type command to continue Error detected while processing CursorMoved Autocommands for "*"..function 45_OnCursorMovedNormalMode[1]..45_AllowedToCompleteInCurrentBuffer[1]..45_AllowedToCompleteInBuffer[12]..45_PollServerReady[14]..45_OnFileTypeSet[8]..45_AllowedToComplet eInCurrentBuffer[1]..45_AllowedToCompleteInBuffer: line 19: E121: Undefined variable: allowed Press ENTER or type command to continue Error detected while processing CursorMoved Autocommands for "*"..function 45_OnCursorMovedNormalMode[1]..45_AllowedToCompleteInCurrentBuffer[1]..45_AllowedToCompleteInBuffer: line 14: E121: Undefined variable: allowed Press ENTER or type command to continue Error detected while processing CursorMoved Autocommands for "*"..function 45_OnCursorMovedNormalMode[1]..45_AllowedToCompleteInCurrentBuffer[1]..45_AllowedToCompleteInBuffer: line 19: E121: Undefined variable: allowed Press ENTER or type command to continue Pressing ENTER afterwards makes vim look normal until you try to move around or do something else. -- System Information: Debian Release: bookworm/sid APT prefers testing APT policy: (500, 'testing'), (500, 'stable'), (50, 'unstable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.18.0-4-amd64 (SMP w/8 CPU threads; PREEMPT) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /usr/bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages vim-youcompleteme depends on: ii python3 3.10.6-1 ii python3-future0.18.2-6 ii vim-nox [vim-python3] 2:9.0.0242-1 ii ycmd [ycmd-core-version] 0+20220824+git2ee4100+ds-1+b1 Versions of packages vim-youcompleteme recommends: ii ycmd 0+20220824+git2ee4100+ds-1+b1 vim-youcompleteme suggests no packages. -- no debconf information Thank you for using reportbug I have now downgraded to version 0+20220402+git3ededae+ds-3 from snapshot.debian.org which resolves my situation for now. Let me know if I can help resolving this and many thanks in advance. Bear with me, this is my first bugreport. cheers Frank signature.asc Description: PGP signature
