[ISSUE] vim-x11: terminal background leaks into vim's

[ISSUE] vim-x11: terminal background leaks into vim's

[blehel]

[-- Attachment #1: Type: text/plain, Size: 1783 bytes --]

New issue by blehel on void-packages repository

https://github.com/void-linux/void-packages/issues/23497

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void 5.4.48_1 x86_64 GenuineIntel notuptodate rrFFFF
* package:  
  vim-x11-8.2.1095_1

### Problem description

After upgrading from 8.2.0891_1 to 8.2.1095_1, in urxvt when opening a file in vim, there are some annoying black spots at the top: 
[example1](https://i.imgur.com/DKbjNnJ.png)
[example2](https://i.imgur.com/esyGF8q.png)
[example3](https://i.imgur.com/8iO0KcR.png)
Previously all of this was the blue color of the background. Pressing CTRL-L to redraw the screen or scrolling down until the affected region goes off-screen does away with the problem.
Note that if I change the terminal background to some other color, that will be the color that creates these spots, so this is about the terminal background not being drawn over.

### Steps to reproduce the behavior

1. Edit your vimrc so that you use a colorscheme with a background different to your terminal's. Mine is a custom one based on `blue`, and my terminal background is black.
So for example add `colorscheme blue` to your vimrc. (setting it from the ex prompt does not bring out the issue).
2. Start `urxvt` (although I've seen similar behaviour - black spots appearing in place of the background color - in the past in terminal emulators which do not support the `bce` /background color erase/ terminal capability, like `kitty`).
3. Open something in vim.

I don't exclude this being an rxvt-unicode problem, but it was the vim upgrade which broke things.

Re: vim-x11: terminal background leaks into vim's

[NeelChotai]

[-- Attachment #1: Type: text/plain, Size: 269 bytes --]

New comment by NeelChotai on void-packages repository

https://github.com/void-linux/void-packages/issues/23497#issuecomment-656744223

Comment:
I can reproduce this, it seems to be a Vim issue.

I've fixed this by appending `autocmd VimEnter * redraw!` to my vimrc.

Re: vim-x11: terminal background leaks into vim's

[biopsin]

[-- Attachment #1: Type: text/plain, Size: 394 bytes --]

New comment by biopsin on void-packages repository

https://github.com/void-linux/void-packages/issues/23497#issuecomment-745116665

Comment:
@blehel did you try raise this issue over @ https://github.com/vim/vim/issues ?
I quickly search thru their commits, hoping to spot something in this regards,
but they are releasing daily so this might or not be fixed in one of those lately ones..

Re: vim-x11: terminal background leaks into vim's

[blehel]

[-- Attachment #1: Type: text/plain, Size: 930 bytes --]

New comment by blehel on void-packages repository

https://github.com/void-linux/void-packages/issues/23497#issuecomment-752364235

Comment:
> @blehel did you try raise this issue over @ https://github.com/vim/vim/issues ?
> I quickly search thru their commits, hoping to spot something in this regards,
> but they are releasing daily so this might or not be fixed in one of those lately ones..

No because they were a few releases ahead, and I did not want to report an issue for a release that was not current.
And based on the suggestion above, I found that `autocmd VimEnter * redraw!` provides a workaround for it. 

I checked to see if vim still has the same behavior without this option, and nothing has changed. Did a search through their issues, and found one that basically describes the same problem, even narrowing it down to the exact patch: https://github.com/vim/vim/issues/6607. I'll leave a comment there.

Re: vim-x11: terminal background leaks into vim's

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 293 bytes --]

New comment by github-actions[bot] on void-packages repository

https://github.com/void-linux/void-packages/issues/23497#issuecomment-1100787137

Comment:
Issues become stale 90 days after last activity and are closed 14 days after that.  If this issue is still relevant bump it or assign it.

Re: [ISSUE] [CLOSED] vim-x11: terminal background leaks into vim's

[github-actions]

[-- Attachment #1: Type: text/plain, Size: 1786 bytes --]

Closed issue by blehel on void-packages repository

https://github.com/void-linux/void-packages/issues/23497

Description:
<!-- Don't request update of package. We have a script for that. https://alpha.de.repo.voidlinux.org/void-updates/void-updates.txt . However, a quality pull request may help. -->
### System

* xuname:  
  Void 5.4.48_1 x86_64 GenuineIntel notuptodate rrFFFF
* package:  
  vim-x11-8.2.1095_1

### Problem description

After upgrading from 8.2.0891_1 to 8.2.1095_1, in urxvt when opening a file in vim, there are some annoying black spots at the top: 
[example1](https://i.imgur.com/DKbjNnJ.png)
[example2](https://i.imgur.com/esyGF8q.png)
[example3](https://i.imgur.com/8iO0KcR.png)
Previously all of this was the blue color of the background. Pressing CTRL-L to redraw the screen or scrolling down until the affected region goes off-screen does away with the problem.
Note that if I change the terminal background to some other color, that will be the color that creates these spots, so this is about the terminal background not being drawn over.

### Steps to reproduce the behavior

1. Edit your vimrc so that you use a colorscheme with a background different to your terminal's. Mine is a custom one based on `blue`, and my terminal background is black.
So for example add `colorscheme blue` to your vimrc. (setting it from the ex prompt does not bring out the issue).
2. Start `urxvt` (although I've seen similar behaviour - black spots appearing in place of the background color - in the past in terminal emulators which do not support the `bce` /background color erase/ terminal capability, like `kitty`).
3. Open something in vim.

I don't exclude this being an rxvt-unicode problem, but it was the vim upgrade which broke things.