From: trentbuck@gmail.com (Trent W. Buck)
To: emacs-devel@gnu.org
Subject: Re: How do I avoid purple-on-black and yellow-on-white?
Date: Mon, 03 Feb 2014 10:47:56 +1100 [thread overview]
Message-ID: <87sis1vzyr.fsf@gmail.com> (raw)
In-Reply-To: 52EEBA71.3070202@gmail.com
Bruce Korb <bruce.korb@gmail.com> writes:
> I needed to use emacs in a terminal window that was in reverse mode --
> background black. I was completely unable to read any of the prompts
> without highlighting the text because the prompts are all purple.
> Somehow, those two combinations need to be prevented. Completely.
> Entirely. Never allowed to happen at all. It should not be up to a
> hapless user to figure out how to configure coloration. It's too
> hard. Thanks you! :)
Emacs already does this for red foreground in eight-color terminals,
which IMO is bloody daft. If X on Y is hard to read in your terminal,
FIX YOUR TERMINAL. Don't reconfigure all your apps to avoid X/Y.
For example, I have this in ~/.profile when $TERM is linux:
## Use tango theme in 256-colour framebuffer console.
printf '\033]P%s' \
02E3436 1CC0000 24E9A06 3C4A000 43465A4 575507B 606989A 7D3D7CF \
8555753 9EF2929 A8AE234 BFCE94F C729FCF DAD7FA8 E34E2E2 FEEEEEC
## Use a darker white, so it can be distinguished from
## brightwhite without overstriking. Use *black* black.
printf '\033]P%s' 0000000 7AAAAAA
For urxvt and xterm, use .Xresources; for libvte terminals there is
usually a menu option under something like Edit > Current Profile.
PS: most Emacs modes have two default color schemes -- dark background
and light background. Because it can't ask the terminal, Emacs assumes
all terminals are dark background. The easiest way to override that is
"emacs -fg black -bg white".
PPS: that's from memory, mostly of 22/23, so may be invalid now.
next prev parent reply other threads:[~2014-02-02 23:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-02 21:36 How do I avoid purple-on-black and yellow-on-white? Bruce Korb
2014-02-02 23:47 ` Trent W. Buck [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-02-03 1:52 Barry OReilly
2014-02-04 0:21 ` Trent W. Buck
2014-02-04 0:41 ` Bruce Korb
2014-02-04 3:26 ` Stefan Monnier
2014-02-07 19:54 ` Juri Linkov
2014-02-04 2:53 Barry OReilly
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=87sis1vzyr.fsf@gmail.com \
--to=trentbuck@gmail.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.