Scrollback Buffer Issue in Vim / Neovim

[PerryCodes]

This is happening in a recently installed Mint 22 Cinnamon. I compiled Ghostty according to the Debian/Ubuntu instructions for dependencies and Zig 0.13 using:
zig build -p $HOME/.local -Doptimize=ReleaseFast

My term is set to 'xterm-256color'. Someone suggested I change term to 'xterm-ghostty', but this results in the same behavior.

1. Start with a multiline file in Vim:
   

2. Position the cursor on Line 1 and join any number of times with J:
   

3. Finally, left-click and drag up - seeing each state of the first line prior being joined:
   

Note: this doesn't happen if I perform the join on any line except Line 1.

[PerryCodes]

Are Linux issues being addressed?

[PerryCodes]

Bug still exists.

[rhodes-b]

Are Linux issues being addressed?

Yes please be patient as you can see there are many many reports to go through

[PerryCodes]

I honestly would have been happy with a simple acknowledgement over the past two weeks. When you see posts 4 hours old being responded to, it makes you wonder what the method is and whether something posted two weeks ago will ever be seen because, as I can see, there are many many reports - and the rate isn't slowing down.

[dragonJACson]

I'm on macOS, after viewing and scrolling through multiple files in vim, the mouse selection (left-click and drag up) during this issue can even expose contents from previously viewed files in the scrollback buffer.

Recording.at.2025-01-15.10.00.47.mp4

[PerryCodes]

Thank you for checking on this. I was worried that this was a Linux-specific dependency-related issue that may have also been version-specific as well. The fact that the buffer also contains previously opened files may further open this up to being a security concern.

Title has been modified to more accurately reflect the issue.

[00-kat]

I can reproduce this in both Vim and Neovim, but interestingly I can't in Helix or Kakoune.

[dragonJACson]

I have another vim-specific scrollback issue (#4802) exists that cannot be reproduced with Helix editor, these problems might be linked to vim's terminal control sequence handling? 🤔