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: Tue, 04 Feb 2014 11:21:33 +1100 [thread overview]
Message-ID: <87r47jybg2.fsf@gmail.com> (raw)
In-Reply-To: CAFM41H3UOOdkjUNq9R-fDfzM1CgmCx85j162yYxk0-M_o5A8AQ@mail.gmail.com
Barry OReilly <gundaetiapo@gmail.com> writes:
> I use graphical most of the time so don't generally notice terminal
> display issues. Under this setup, the terminal colors are very
> different from the graphical, but a brief look didn't uncover any poor
> contrast.
Probably because you were on a terminal that claimed 8-color support (16
if it treats bold as "bright colors"). With 256-color terminals, the
difference is much less noticable.
You can test easily with "tput colors".
With the appropriate package installed (e.g. "ncurses-base" on Debian),
you can change your terminal from e.g. TERM=xterm to
TERM=xterm-256color, and Emacs will use nonstandard escape sequences to
produce eight-bit colors.
If you've also customized the basic 16 colors, this can look strange :-)
M-x list-colors-display RET to have a look.
If that looks mostly blue-green, you're mixing up 256 and 88 color
terminals. This used to arise with urxvt; I don't know if it supports
256 colors yet.
Eight-color sequences are portable between terminals, see tput(1) and
terminfo(5) ref. setaf, setab, bold and sgr0.
88/256 color sequences are not portable, but IME all use the xterm
sequences. For these, M-x find library RET term/xterm RET, also see
xterm(1).
I've avoided 256-color terminals for many years, because they oblige me
to theme apps instead of just the terminal (and 8 colors is usually
enough for me). Back when I did, I wrote some notes:
http://www.cyber.com.au/~twb/doc/term256.txt
Hopefully this brain dump is useful to someone :-)
next prev parent reply other threads:[~2014-02-04 0:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 1:52 How do I avoid purple-on-black and yellow-on-white? Barry OReilly
2014-02-04 0:21 ` Trent W. Buck [this message]
2014-02-04 0:41 ` Bruce Korb
2014-02-04 3:26 ` Stefan Monnier
2014-02-07 19:54 ` Juri Linkov
-- strict thread matches above, loose matches on Subject: below --
2014-02-04 2:53 Barry OReilly
2014-02-02 21:36 Bruce Korb
2014-02-02 23:47 ` Trent W. Buck
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=87r47jybg2.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.