From: fatiparty--- via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: Fatiparty <fatiparty@tutanota.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Help Gnu Emacs <help-gnu-emacs@gnu.org>
Subject: min-colors 88
Date: Fri, 28 Jan 2022 14:55:34 +0100 (CET) [thread overview]
Message-ID: <MuVy3gh--3-2@tutanota.com> (raw)
In-Reply-To: <MuVkMCN--3-2@tutanota.com-MuVxLzA----2>
Jan 29, 2022, 00:55 by help-gnu-emacs@gnu.org:
> Jan 29, 2022, 00:16 by eliz@gnu.org:
>
>>> Date: Fri, 28 Jan 2022 12:54:49 +0100 (CET)
>>> From: fatiparty@tutanota.com
>>> Cc: Help Gnu Emacs <help-gnu-emacs@gnu.org>
>>>
>>> For instance I can invent a code #d166ff
>>> ( ((class color) (min-colors 88) (background dark))
>>> :foreground "#d166ff" )
>>>
>>> That would not mean that #d166ff actually exists for 256 colour availability.
>>>
>>
>> It doesn't matter. Emacs will find a color that is the closest to
>> that RGB value, and use it. See tty-colors.el.
>>
>
> Are there more colours available than those in the color-name-rgb-alist ?
>
I have called xdpyinfo, getting (1, 4, 8, 15, 16, 24, 32)
xdpyinfo | awk '$1=="depth" && sub(/,$/, "", $2) {print $2}'
next prev parent reply other threads:[~2022-01-28 13:55 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-27 6:14 min-colors 88 fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 6:33 ` Yuri Khan
2022-01-27 11:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 12:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
[not found] ` <CAP_d_8U3E=FAQJ7XiNMnCi-Y4Gneo69KmEKVTuWWHOA7EVz7Gg@mail.gmail.com-MuPEX1J--7-2>
2022-01-27 6:39 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 6:46 ` Eli Zaretskii
2022-01-27 8:43 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 9:56 ` Eli Zaretskii
2022-01-27 10:44 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 10:54 ` Bastian Beranek
2022-01-27 11:01 ` Eli Zaretskii
2022-01-27 11:43 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 11:49 ` Eli Zaretskii
2022-01-27 12:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 12:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 11:47 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 11:50 ` Eli Zaretskii
2022-01-27 13:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 13:03 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 13:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 15:14 ` Eli Zaretskii
2022-01-27 18:09 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 18:30 ` Eli Zaretskii
2022-01-27 18:43 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 18:46 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-27 19:46 ` Eli Zaretskii
2022-01-27 18:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-28 7:58 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 8:07 ` Eli Zaretskii
2022-01-28 8:59 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 11:36 ` Eli Zaretskii
2022-01-28 11:54 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 12:16 ` Eli Zaretskii
2022-01-28 12:55 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 13:19 ` Eli Zaretskii
[not found] ` <MuVkMCN--3-2@tutanota.com-MuVxLzA----2>
2022-01-28 13:55 ` fatiparty--- via Users list for the GNU Emacs text editor [this message]
2022-01-28 21:27 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-28 12:53 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 13:17 ` Eli Zaretskii
2022-01-28 13:49 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 14:34 ` Eli Zaretskii
2022-01-28 15:12 ` fatiparty--- via Users list for the GNU Emacs text editor
2022-01-28 16:56 ` Eli Zaretskii
2022-01-28 21:21 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 18:42 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 11:59 ` Emanuel Berg via Users list for the GNU Emacs text editor
2022-01-27 11:50 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=MuVy3gh--3-2@tutanota.com \
--to=help-gnu-emacs@gnu.org \
--cc=eliz@gnu.org \
--cc=fatiparty@tutanota.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.
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).