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: Wed, 19 Dec 2018 17:19:34 +0200 [thread overview]
Message-ID: <83lg4lcznd.fsf@gnu.org> (raw)
In-Reply-To: <87ftuuwdwu.fsf@mail.linkov.net> (message from Juri Linkov on Wed, 19 Dec 2018 02:36:33 +0200)
> From: Juri Linkov <juri@linkov.net>
> Cc: van@scratch.space, 33398@debbugs.gnu.org
> Date: Wed, 19 Dec 2018 02:36:33 +0200
>
> > Call it "hi-reddish" if you must, just don't have something called
> > "gold" look red on TTYs, please.
>
> We can call it "hi-redgold" because such thing really exists:
> https://en.wikipedia.org/wiki/Red_gold
If that's the best we can do...
> (defface hi-redgold
> '((((min-colors 88) (type x w32 ns)) (:background "gold"))
> (((min-colors 88)) (:background "orange"))
> (((min-colors 16)) (:background "red"))
> (t (:background "red")))
How about this instead:
(defface hi-redgold
'((((min-colors 8)) (:background "red"))
(t (:background "gold")))
"Face for hi-lock mode."
:group 'hi-lock-faces)
I see no reason to use "red" on 16-color terminals, nor "orange" on
color TTYs with at least 88 colors. The translation of "gold" should
be good enough in those cases. Isn't it?
next prev parent reply other threads:[~2018-12-19 15:19 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
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 [this message]
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=83lg4lcznd.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).