Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#55459 - [vim] auto decrease first number when open file in 8.0.0987-1

Attached to Project: Arch Linux
Opened by Tommy Wong (wx0) - Friday, 01 September 2017, 15:59 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 08 October 2017, 13:54 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Levente Polyak (anthraxx)
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
When using last stable version of vim(8.0.0851-1), everything is fine.
After update to latest stable version(8.0.0987-1), vim will decrease the first number by 1 in a very high probability(almost every time) when opening any file, eg. num0 -> num-1, dev3 -> dev2
Tried remove vim and remove all config file, do not change behavior.
Tried downgrade vim to last stable version(8.0.0851-1), this behavior disappears.


Additional info:
$ uname -a
Linux arch-min 4.12.8-2-ARCH #1 SMP PREEMPT Fri Aug 18 14:08:02 UTC 2017 x86_64 GNU/Linux
packages:
vim-runtime-8.0.0987-1-x86_64
vim-8.0.0987-1-x86_64
Configs:
All default vim config.
~/.bashrc only has some alias. Nothing about vim.
Cygwin and msys2 from windows, ssh connected to 2 arch machines.
Using tuna mirror(checksum is the same with upstream so I think it's not the problem).
Counldn't see any environment variable related to vim.


Steps to reproduce:
[begin]
$ sudo pacman -S vim
***
Packages (2) vim-8.0.0987-1 vim-runtime-8.0.0987-1
***
$ touch text
$ echo num0 > text
$ cat text
num0
$ vim text
num-1
[here vim is showing "num-1", and try to exit using `:q` will pop up "E37: No write since last change"]
:wq
$ cat text
num-1
[end]

Please contact if more info is needed.
Might reply late, apologize for that.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 08 October 2017, 13:54 GMT
Reason for closing:  Fixed
Comment by Christian Kujau (ckujau) - Saturday, 02 September 2017, 08:34 GMT
Hm, I could not reproduce this particular scenario with vim 8.0.0987-1, but this smells an awful lot like the shenanigans vim is playing in https://github.com/vim/vim/issues/2008, where different combinations of terminal capabilities would produce weird display effects. It's said to be fixed in vim-8.0.1027 though.
Comment by Doug Newgard (Scimmia) - Saturday, 02 September 2017, 19:21 GMT
I can't reproduce. I wonder if it has to do with a plugin or config?
Comment by Tommy Wong (wx0) - Sunday, 03 September 2017, 09:45 GMT
Some one told that he can repoduce when using Windows without tmux, so I guess it's related to terminal software.

All configs are deleted before reinstall vim as described, it should be something in the package that cause this problem.

Maybe it's the problem Christian Kujau pointed out. I'll try some other terminal and see if it repoduces.
Comment by Levente Polyak (anthraxx) - Thursday, 05 October 2017, 12:35 GMT
is this still an issue? can you please report it upstream and post the ticket here?
Comment by Tommy Wong (wx0) - Sunday, 08 October 2017, 08:38 GMT
I think it's not an issue now, vim on my arch machine have updated to 8.0.1159 and it's working without problem.

Loading...