From: Eli Zaretskii <eliz@gnu.org>
Cc: mh-e-devel@lists.sourceforge.net, emacs-devel@gnu.org
Subject: Re: Why min-colors 88?
Date: Sun, 05 Feb 2006 21:55:51 +0200 [thread overview]
Message-ID: <uvevt60mw.fsf@gnu.org> (raw)
In-Reply-To: <87wtgapbup.fsf@olgas.newt.com> (message from Bill Wohler on Sat, 04 Feb 2006 22:18:38 -0800)
> From: Bill Wohler <wohler@newt.com>
> Date: Sat, 04 Feb 2006 22:18:38 -0800
> Cc: mh-e-devel@lists.sourceforge.net
>
> > Because there's an 88-color xterm whose color set is rich enough to
> > support all the colors we use in Emacs' faces.
>
> Or in other words, Emacs' has 88 faces?
No, it has much less. But we tried all the colors in tty-colors.el,
and the 88-color xterm distinguishes them enough for us to decide that
88 colors are like 256 for all practical purposes.
In other words, 88-color xterm will support any faces that could be
defined in the future as well as the X version of Emacs.
> > . find out what colors, in terms of RGB values, are defined on that
> > device
> > . map the colors used by Emacs (e.g. in color-name-rgb-alist) into
> > those 64 colors, using tty-color-translate
> > . see how many Emacs colors map to the same color on the 64-color
> > deives, and
> > . draw the conclusions.
>
> Objectively, if the colors that we use do not map to the same color,
> we should be OK, right?
Yes.
> Subjectively, the MH-E colors should map to a pleasing set.
Yes.
prev parent reply other threads:[~2006-02-05 19:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-03 19:50 Why min-colors 88? Bill Wohler
2006-02-04 11:11 ` Eli Zaretskii
2006-02-05 6:18 ` Bill Wohler
2006-02-05 13:42 ` Stefan Monnier
2006-02-05 17:05 ` Bill Wohler
2006-02-05 18:49 ` Dan Nicolaescu
2006-02-05 22:31 ` Bill Wohler
2006-02-06 1:41 ` Miles Bader
2006-02-06 2:32 ` Stefan Monnier
2006-02-05 19:55 ` Eli Zaretskii [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=uvevt60mw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mh-e-devel@lists.sourceforge.net \
/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.