mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Jan Engelhardt <jengelh@linux01.gwdg.de>
Cc: Thomas Fazekas <thomas.fazekas@gmail.com>,
	linux-kernel@vger.kernel.org, arch@archlinux.org
Subject: Re: Modify setterm color palette
Date: Sun, 15 Jan 2006 13:16:20 +0000	[thread overview]
Message-ID: <20060115131620.GA24976@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.61.0601151313360.4174@yvahk01.tjqt.qr>

On Sun, Jan 15, 2006 at 01:15:23PM +0100, Jan Engelhardt wrote:
> drivers/char/vt.c: default_red, default_grn, default_blu
> 
> You can also change them with `echo -en "\e]PXRRGGBB"`, where X is a hex 
> digit (range 0-F), and RGB are the components. Check console_codes(4) and 
> go figure. :)

I for one prefer the standard VT100 yellow instead of brown, and I
have an escape sequence to do that similar to the one you show above.

However, there's one major flaw - programs recently (and by that I mean
FC2-like recently) have started to do complete console resets, which
result in the users settings being completely wiped out.

For instance, I have:

if [ "$TERM" = "linux" ]; then
  echo -ne '\e]P3aaaa00'
fi

in the bash login scripts.  Run mutt 1.4 and that gets wiped out.
Previous version of mutt (1.2?) didn't do this.

So, in essence, this is a completely useless solution.  I think we need
a separate escape sequence to modify the system default so that peoples
preferences do not get inadvertently wiped out by programs.

(I have also considered writing a module to locate the default palette
and "correct" it.)

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  parent reply	other threads:[~2006-01-15 13:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-15 12:07 Thomas Fazekas
2006-01-15 12:15 ` Jan Engelhardt
2006-01-15 12:55   ` Willy Tarreau
2006-01-15 13:16   ` Russell King [this message]
2006-01-15 13:35     ` Willy Tarreau
2006-01-15 21:14       ` Jan Engelhardt
2006-01-16  9:54     ` Pavel Machek

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=20060115131620.GA24976@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=arch@archlinux.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thomas.fazekas@gmail.com \
    /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

all inboxes | Powered by JetHome®