unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 9402@debbugs.gnu.org
Subject: bug#9402: list-colors-display
Date: Tue, 30 Aug 2011 00:17:42 +0300	[thread overview]
Message-ID: <8739gjzzm1.fsf@mail.jurta.org> (raw)
In-Reply-To: <838vqcf086.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 29 Aug 2011 23:10:01 +0300")

>> 2. New faces `gtk_selection_fg_color' and `gtk_selection_bg_color'
>> now are available for using on GTK but they are not listed in
>> `list-colors-display', and they can't be selected and completed in
>> `customize-face'.
>
> Did this ever work?  Emacs always had platform-specific colors besides
> those in rgb.txt, I don't think this is something new.

Yes, it never worked.

>> There are more colors that are valid for using but hidden from users
>> such as e.g. on a tty: `unspecified-fg', `unspecified-bg'.
>
> They are meaningless and cannot be set by Emacs.  IOW, they are
> "read-only", as far as Emacs is concerned.  Exposing them to users
> would be confusing.

All colors are "read-only" for users in the sense that users can't
change them.  But platform-specific colors are not different from other
colors in the sense that they are used in face customization.

IOW, when the user types `M-x customize-face RET region RET'
then s?he sees the color name "gtk_selection_fg_color".
Then the user might change it to some other color, but after that
it's difficult to restore the original default color name,
because the user don't remember this color name literally
and can't select it using completion or the "Choose" button
that lists all color names.





  reply	other threads:[~2011-08-29 21:17 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-29 19:27 bug#9402: list-colors-display Juri Linkov
2011-08-29 20:10 ` Eli Zaretskii
2011-08-29 21:17   ` Juri Linkov [this message]
2011-08-30  2:54     ` Eli Zaretskii
2011-08-30  5:40     ` Jan D.
2011-08-30  9:10       ` Juri Linkov
2011-08-30 11:41         ` Eli Zaretskii
2011-08-30 14:15           ` Andreas Schwab
2011-08-30 17:57             ` Eli Zaretskii
2011-08-30  7:44   ` Eli Zaretskii
2011-08-30 17:46     ` Eli Zaretskii
2011-08-31  9:35       ` Juri Linkov
2011-08-31 10:57         ` Eli Zaretskii
2011-08-31 16:17           ` Chong Yidong
2011-08-31 19:02             ` Jan Djärv
2011-09-01  2:12               ` Chong Yidong
2011-08-31 16:27           ` Juri Linkov
2011-08-31 17:40             ` Eli Zaretskii
2011-08-31 18:35               ` Juri Linkov
2011-08-31 19:22                 ` Jan Djärv
2011-08-31 20:14                   ` Eli Zaretskii
2011-08-31 20:28                     ` Juri Linkov
2011-09-01  2:54                       ` Eli Zaretskii
2011-08-31 21:07                     ` Jan Djärv
2011-09-01  2:56                       ` Eli Zaretskii
2011-09-01  2:15                     ` Chong Yidong
2011-09-01  3:07                       ` Eli Zaretskii
2011-08-31 19:17             ` Jan Djärv
2011-08-31 19:11           ` Jan Djärv
2011-08-31 20:00             ` Eli Zaretskii
2011-08-31 20:10               ` Juri Linkov
2011-09-01  2:50                 ` Eli Zaretskii
2011-09-01  8:36                   ` Juri Linkov
2011-09-01 10:06                     ` Eli Zaretskii
2011-08-31 21:06               ` Jan Djärv
2011-08-31 19:09         ` Jan Djärv

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=8739gjzzm1.fsf@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=9402@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    /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).