From: "Alexander V. Lukyanov" <lav@netis.ru>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: Linux kernel mailing list <linux-kernel@vger.kernel.org>,
Ncurses Developers <ncurses-dev@gnu.org>
Subject: Re: linux 2.6.26 vt back_color_erase
Date: Mon, 13 Oct 2008 09:24:38 +0400 [thread overview]
Message-ID: <20081013052437.GA27761@night.netis.ru> (raw)
In-Reply-To: <alpine.LNX.1.10.0810101310400.21097@fbirervta.pbzchgretzou.qr>
On Fri, Oct 10, 2008 at 01:22:08PM -0400, Jan Engelhardt wrote:
> >> Current linux kernel has broken bce semantics. Now insert_line and
> >> delete_line clear the new lines with default color and not with the
> >> current background as they should, and what is expected by ncurses.
>
> I beg to differ. The Linux VT now does exactly what an xterm does,
I have just tested again: my xterm does erase new lines with current color,
just as linux console before the change. My xterm version: XTerm(196).
Please test yours and check the version. Also, please test other terminals
with bce terminfo attribute. I have tested putty and it also erases new
lines with default colors. And gnome-terminal too.
> namely that newly inserted lines do not get filled with the
> background color. And I consider that the right thing, because it
> does not leave ugly color patches lying on your screen when `ls -l`
> overruns the screen width, and someone decided to use a background
> color for his filenames.
Probably color ls -l is just broken and should be fixed. Why was it
necessary to change the console color semantics that was there for years?
> ncurses should not expect anything. Except what is in terminfo.
> Do we need a terminfo db update for the "linux" term?
Sure, unless the change is reverted. The bce attribute will need to be
disabled, which is a pity as it saves traffic for color full screen
applications. And changing terminfo is very inconvenient for remote logins.
--
Alexander.
next prev parent reply other threads:[~2008-10-13 5:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-03 8:11 linux 2.6.26 vt back_color_erase Alexander V. Lukyanov
2008-10-10 16:49 ` Alexander V. Lukyanov
2008-10-10 17:22 ` Jan Engelhardt
2008-10-13 5:24 ` Alexander V. Lukyanov [this message]
2008-10-13 7:40 ` Jan Engelhardt
2008-10-13 8:39 ` Alan Cox
2008-10-14 8:16 ` Alexander V. Lukyanov
2008-10-14 15:33 ` Jan Engelhardt
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=20081013052437.GA27761@night.netis.ru \
--to=lav@netis.ru \
--cc=jengelh@medozas.de \
--cc=linux-kernel@vger.kernel.org \
--cc=ncurses-dev@gnu.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