Control: reassign -1 vim 2:9.0.1000-2 Control: forcemerge 1027766 -1 On 2023-01-03 14:48 +1100, Craig Small wrote:
> For some reason the issue is not vim-ale its something broken in the
> generic vim infrastructure.
Indeed.
> debian.vim sets nocompatible which is supposed to stop the issue but it
> doesn't
> running vim -N or putting "set nocompatible" in ~/.vimrc fixes it
The problem is that vim 2:9.0.1000-2 put debian.vim into the wrong
directory where vim does not find it.
Cheers,
Sven
