Package: vim
Version: 2:8.2.2367-1
Severity: normal
Dear Maintainer,
Since an update to /some/ part of vim on unstable sometime last weekend I've
encountered new default behaviour that's quite disruptive.
For instance, when I started writing this, as well as every single time this
terminal window gains or loses focus, vim fires a console beep and gives a
popup of the following two lines:
---
/tmp/reportbug-vim-20210119-44233-2mw9ao7j
1: 1 Subject: vim: Change in default vim config causes obnoxious behaviour.
---
(The exact nature of the second line depending on the line my cursor is
currently on)
Worse (from my perspective) it also deliberately drops out of insert mode
and back into command mode.
I'm sure whoever designed this feature felt there was a good use case for it,
but it's quite disruptive to my regular workflow, and when I had cause to use
vim to edit a large file that consisted of one single huge line it was
downright /crippling/.
Worse, despite multiple attempts at googling I haven't even been able to
figure out what this feature is called, much less how to disable it in config
* What led up to the situation?
- A routine upgrade for vim to version 8.2.2367-1. The last version I can
confirm
does not exhibit this new behaviour is 8.2.1913-1
* What exactly did you do (or not do) that was effective (or
ineffective)?
- Disabling the entire config via the methods recommended earlier in
this reporting process does make the behaviour go away, but it also
makes all the behaviour I /do/ want from vim go away.
- Downgrading to the version currently in testing (8.2.1913-1) does not
exhibit the behaviour.
- Running vim in a straight XTERM rather than gnome-terminal does not
exhibit the behaviour
- Running vim in a different 'enhanced' terminal (xfce4-terminal) does
exhibit the behaviour.
Based on this I'm /guessing/ that this feature is activated when vim
detects that its current environment can tell it things about the environment
beyond itself and "helpfully" reacts accordingly.
* What outcome did you expect instead?
I expected vim to keep working as it has for several decades and default
to /not/ cause this new behaviour, or at least properly document the change
so I'd have an idea what feature to turn off.
-- Package-specific info:
--- real paths of main Vim binaries ---
/usr/bin/vi is /usr/bin/vim.basic
/usr/bin/vim is /usr/bin/vim.basic
-- System Information:
Debian Release: bullseye/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (500, 'oldstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-1-amd64 (SMP w/24 CPU threads)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8),
LANGUAGE=en_US:en
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages vim depends on:
ii libacl1 2.2.53-9
ii libc6 2.31-9
ii libcanberra0 0.30-7
ii libgpm2 1.20.7-7
ii libselinux1 3.1-2+b2
ii libtinfo6 6.2+20201114-2
ii vim-common 2:8.2.2367-1
ii vim-runtime 2:8.2.2367-1
vim recommends no packages.
Versions of packages vim suggests:
pn ctags <none>
pn vim-doc <none>
pn vim-scripts <none>
-- no debconf information
