From: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] vim-x11: terminal background leaks into vim's
Date: Sun, 01 May 2022 04:13:53 +0200 [thread overview]
Message-ID: <20220501021353.w205YYXT9JxIcuQKbw-iCe8cpQOxORk9YGiDAW12fSs@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-23497@inbox.vuxu.org>
[-- 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.
prev parent reply other threads:[~2022-05-01 2:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 14:09 [ISSUE] " blehel
2020-07-10 15:45 ` NeelChotai
2020-12-15 7:48 ` biopsin
2020-12-30 7:51 ` blehel
2022-04-17 2:06 ` github-actions
2022-05-01 2:13 ` github-actions [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220501021353.w205YYXT9JxIcuQKbw-iCe8cpQOxORk9YGiDAW12fSs@z \
--to=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).