From: Juri Linkov <juri@linkov.net>
To: Eli Zaretskii <eliz@gnu.org>
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: Fri, 30 Nov 2018 00:29:21 +0200 [thread overview]
Message-ID: <871s73cybi.fsf@mail.linkov.net> (raw)
In-Reply-To: <838t1ce3tw.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 29 Nov 2018 09:32:43 +0200")
>> >>> Maybe something like this, but I'm not sure because the red background would
>> >>> be too glaring on 88 colors, but more readable orchid1 is not quite red.
>> >>
>> >> Is OrangeRed better?
>> >
>> > OrangeRed is not better than red, but simply Orange looks much better,
>> > so a new face could be named hi-orange.
>>
>> After trying to use Orange, I see it's too saturated, that is bad for
>> light backgrounds. But I found a much better color: Gold. It is still
>> related to red because gold can be reddish in an alloy with copper.
>
> I don't see how "gold" can be translated to "red", sorry. It
> translates to yellow shades on both 8- and 16-color TTYs, as expected.
> Did you try "IndianRed" instead?
Unfortunately, "IndianRed" is so dark that it's unreadable.
Whereas "Gold" is so prefect, that I can't find a replacement.
But are translations really required? I created a definition
that works well on all environments (I see that "gold" looks good
on a graphical terminal, but on a 256-color TTY "orange" is better).
Do you see a problem with these best-looking faces?
(defface hi-gold
'((((min-colors 88) (type x w32 ns)) (:background "gold"))
(((min-colors 88)) (:background "orange"))
(((min-colors 16)) (:background "red"))
(t (:background "red")))
"Face for hi-lock mode."
:group 'hi-lock-faces)
(defface hi-aquamarine
'((((min-colors 88)) (:background "aquamarine"))
(((min-colors 16)) (:background "blue"))
(t (:background "blue")))
"Face for hi-lock mode."
:group 'hi-lock-faces)
next prev parent reply other threads:[~2018-11-29 22:29 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 [this message]
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=871s73cybi.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=33398@debbugs.gnu.org \
--cc=eliz@gnu.org \
--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).