From: scame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 47316@debbugs.gnu.org
Subject: bug#47316: 27.1; commands with color input should use a common color chooser
Date: Mon, 22 Mar 2021 12:11:56 +0000 [thread overview]
Message-ID: <Du3GmuIlXBWcyjebsmsnNgRCJJ_BRulYpngpA15FMMh_Kw9KhS7SNQPiuOEtw4QqcI42I2FrX-_4SZJ0Zh42CJkZTza0AjBSJ3qOqdHQKlQ=@protonmail.com> (raw)
In-Reply-To: <D162B40F-C219-4AD2-9A60-1F4BBBAA13E3@gnu.org>
> read-color will show you the colors from which you can select if you type '?', the standard Emacs command that requests the list of possible candidate values.
Yes, I mentioned it in my mail:
> > set-foreground-color uses a color chooser: read-color.
But customize use a different implementation, not read-color (at least on 27)
and other commands do not use read-color at all, despite getting color input,
they just list the color names without coloring them.
Other commands which read a face, not a color, show just face names for
completion. Showing face colors and other attributes inline (like in case
of list-faces-display) could be a nice improvement.
next prev parent reply other threads:[~2021-03-22 12:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 11:01 bug#47316: 27.1; commands with color input should use a common color chooser scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-22 11:33 ` Eli Zaretskii
2021-03-22 12:11 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2021-03-22 17:42 ` Eli Zaretskii
2021-03-22 18:49 ` Lars Ingebrigtsen
2021-03-22 19:57 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
2021-03-22 20:01 ` Lars Ingebrigtsen
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='Du3GmuIlXBWcyjebsmsnNgRCJJ_BRulYpngpA15FMMh_Kw9KhS7SNQPiuOEtw4QqcI42I2FrX-_4SZJ0Zh42CJkZTza0AjBSJ3qOqdHQKlQ=@protonmail.com' \
--to=bug-gnu-emacs@gnu.org \
--cc=47316@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=laszlomail@protonmail.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).