From: Juri Linkov <juri@linkov.net>
To: Van L <van@scratch.space>
Cc: 33398@debbugs.gnu.org
Subject: bug#33398: 26.1, netbsd-8; Hi Lock Faces, Hi Green B, default setting suggestion
Date: Thu, 22 Nov 2018 00:56:19 +0200 [thread overview]
Message-ID: <87sgzuca5o.fsf@mail.linkov.net> (raw)
In-Reply-To: <740AF1DA-7EDB-4310-8C6E-F7944D714513@scratch.space> (Van L.'s message of "Wed, 21 Nov 2018 23:23:44 +1100")
> 'darkgreen'
> was what we could agree on for `Hi Green B’
'darkgreen' is almost black, and indistinguishable from
the default black foreground color. A better color
for `Hi Green B' is 'green3'.
>> The same way as hi-yellow is defined to use yellow, and hi-green
>> to use green, we can define hi-blue to use blue color, and
>> hi-pink to use red color. This will free cyan and magenta
>> to use.
I guess there are no hi-magenta and hi-cyan faces because
Isearch uses the magenta color for the current match and the
cyan color for lazy-highlighted matches.
But OTOH, on TTY magenta and cyan are used from hi-pink and hi-blue,
and there is no problem, so we can define two new hi-lock faces.
> The rainbow/artist’s coloring pencils theme for hi-faces is nicer to
> have for the wm-frame-windowing environment.
emacs/lisp/textmodes/artist.el doesn't have many colors,
and colors from the rainbow-delimiters packages are too dull.
next prev parent reply other threads:[~2018-11-21 22:56 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 [this message]
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
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=87sgzuca5o.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=33398@debbugs.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).