From: Eli Zaretskii <eliz@gnu.org>
To: Juri Linkov <juri@linkov.net>
Cc: van@scratch.space, 33398@debbugs.gnu.org
Subject: bug#33398: 26.1, netbsd-8; Hi Lock Faces, Hi Green B, default setting suggestion
Date: Mon, 26 Nov 2018 18:01:17 +0200 [thread overview]
Message-ID: <83h8g3j0aa.fsf@gnu.org> (raw)
In-Reply-To: <87k1l0c3be.fsf@mail.linkov.net> (message from Juri Linkov on Sun, 25 Nov 2018 22:25:25 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: van@scratch.space, 33398@debbugs.gnu.org
> Date: Sun, 25 Nov 2018 22:25:25 +0200
>
> The problem is that the condition '(t (:background "pink"))' is
> automatically translated to "magenta" on a 8-color TTY. And in the
> 'hi-blue' face '(t (:background "light blue"))' is translated to "cyan".
>
> So to add a new face with a "blue" background on a 8-color TTY
> with the condition '(t (:background "blue"))' we have no suitable name
> for a new face, become the most suitable name 'hi-blue' is already
> taken by the existing face that is displayed as "cyan".
>
> The same problem is with 'hi-pink' that is currently translated to
> "magenta", not to "red" on a 8-color TTY.
(Converting "pink" to "magenta" and "lightblue" to "cyan" sounds fine
to me.)
So your problem is with the names of the faces? Then may I suggest to
name the new faces hi-red and hi-deepblue?
> ‘--color=MODE’
> ...
> ‘NUM’
> ...
> Depending on your terminal’s capabilities, Emacs might be able
> to turn on a color mode for 8, 16, 88, or 256 as the value of NUM.
>
> I guess the key point is "Depending on your terminal’s capabilities".
> This might explain why values other than 8 and 256 are not supported.
Right. But this subtlety is slightly misleading.
next prev parent reply other threads:[~2018-11-26 16:01 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 12:58 bug#33398: 26.1, netbsd-8; Hi Lock Faces, Hi Green B, default setting suggestion Van L
2018-11-15 21:25 ` Juri Linkov
2018-11-15 22:13 ` Van L
2018-11-17 20:54 ` Juri Linkov
2018-11-19 3:10 ` Van L
2018-11-19 21:58 ` Juri Linkov
2018-11-20 4:00 ` Van L
2018-11-20 22:59 ` Juri Linkov
2018-11-21 12:23 ` Van L
2018-11-21 22:56 ` Juri Linkov
2018-11-22 0:32 ` Van L
2018-11-22 22:16 ` Juri Linkov
2018-11-23 0:56 ` Van L
2018-11-23 8:38 ` Eli Zaretskii
2018-11-23 11:22 ` Van L
2018-11-23 15:54 ` Eli Zaretskii
2018-11-23 8:35 ` Eli Zaretskii
2018-11-24 21:29 ` Juri Linkov
2018-11-25 16:46 ` Eli Zaretskii
2018-11-25 20:25 ` Juri Linkov
2018-11-26 16:01 ` Eli Zaretskii [this message]
2018-11-26 23:27 ` Juri Linkov
2018-11-27 5:56 ` Eli Zaretskii
2018-11-27 23:49 ` Juri Linkov
2018-11-28 23:06 ` Juri Linkov
2018-11-29 7:32 ` Eli Zaretskii
2018-11-29 22:29 ` Juri Linkov
2018-11-30 7:16 ` Eli Zaretskii
2018-12-19 0:36 ` Juri Linkov
2018-12-19 3:50 ` Van L
2018-12-19 21:37 ` Juri Linkov
2018-12-19 15:19 ` Eli Zaretskii
2018-12-19 21:40 ` Juri Linkov
2018-12-20 0:16 ` Van L
2018-12-20 16:11 ` Eli Zaretskii
2018-12-20 23:01 ` Juri Linkov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h8g3j0aa.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=33398@debbugs.gnu.org \
--cc=juri@linkov.net \
--cc=van@scratch.space \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).