From: Po Lu <luangruo@yahoo.com>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Shynur Xie <one.last.kiss@outlook.com>,
Eli Zaretskii <eliz@gnu.org>,
"emacs-devel@gnu.org" <emacs-devel@gnu.org>
Subject: Re: Bug?
Date: Sun, 07 May 2023 20:05:33 +0800 [thread overview]
Message-ID: <87wn1kibxu.fsf@yahoo.com> (raw)
In-Reply-To: <7C681179-89A6-4BBA-9B31-11C13B2EEFF1@acm.org> ("Mattias Engdegård"'s message of "Sun, 7 May 2023 13:08:17 +0200")
Mattias Engdegård <mattiase@acm.org> writes:
> 6 maj 2023 kl. 16.58 skrev Shynur Xie <one.last.kiss@outlook.com>:
>
>> But did you notice that all the faces defined in
>> <lisp/faces.el> use "pre-defined color names" instead of "#RRGGBB"?
>> I'm a little worried that if we use "#RRGGBB", it might be not
>> intuitive and not fit with the overall style of <lisp/faces.el>.
>
> I have no opinion on the matter. I suppose `darkskyblue4` is the
> closest. Which colour would you prefer?
Please try very hard to avoid using device or intensity specifications
for colors. This is because many vendors of X servers perform color
calibration for graphics devices by editing the list of pre-defined X
colors.
In addition, using non-predefined colors means that you will be more
likely to allocate a color cell in the default colormap which no other
program can use. While not as important as it used to be, excessive
color use is still something to keep in mind when writing programs.
next prev parent reply other threads:[~2023-05-07 12:05 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875y9aciir.fsf.ref@yahoo.com>
2023-05-03 1:26 ` Bug? Po Lu
2023-05-03 9:40 ` Bug? Mattias Engdegård
2023-05-03 10:12 ` Bug? Mattias Engdegård
2023-05-03 11:24 ` Bug? Shynur Xie
2023-05-03 12:27 ` Bug? Mattias Engdegård
2023-05-03 17:22 ` Bug? Juri Linkov
2023-05-03 11:24 ` Bug? Eli Zaretskii
2023-05-03 11:26 ` Bug? Shynur Xie
2023-05-04 8:35 ` Bug? Shynur Xie
2023-05-04 20:57 ` Bug? Shynur Xie
2023-05-05 4:41 ` Bug? Eli Zaretskii
2023-05-05 16:18 ` Bug? Shynur Xie
2023-05-06 10:44 ` Bug? Mattias Engdegård
2023-05-06 14:58 ` Bug? Shynur Xie
2023-05-06 15:24 ` Bug? Eli Zaretskii
2023-05-07 11:08 ` Bug? Mattias Engdegård
2023-05-07 12:05 ` Po Lu [this message]
2023-05-07 12:17 ` Bug? Eli Zaretskii
2023-05-07 12:54 ` Bug? Po Lu
2023-05-07 13:36 ` Bug? Shynur Xie
2023-05-07 13:51 ` Bug? Mattias Engdegård
2023-05-07 14:42 ` Bug? Shynur Xie
2023-05-07 15:06 ` Bug? Eli Zaretskii
2023-05-03 11:23 ` Bug? Eli Zaretskii
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=87wn1kibxu.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=mattiase@acm.org \
--cc=one.last.kiss@outlook.com \
/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).