From: Eli Zaretskii <eliz@gnu.org>
To: laszlomail@protonmail.com, 47316@debbugs.gnu.org
Subject: bug#47316: 27.1; commands with color input should use a common color chooser
Date: Mon, 22 Mar 2021 13:33:57 +0200 [thread overview]
Message-ID: <D162B40F-C219-4AD2-9A60-1F4BBBAA13E3@gnu.org> (raw)
In-Reply-To: <azDmfibdsWoEw0cpLFNIxrPECDU-IVoaTdg1tA_KuYrrBPiAyRebyUvhPgjoo6rVKrmqKYhnwyF_2aOrP4n0vmBLkMTA3P4a-WsiZdLSzG0=@protonmail.com>
On March 22, 2021 1:01:13 PM GMT+02:00, "scame via Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org> wrote:
> set-foreground-color uses a color chooser: read-color.
>
> customize-face uses something else which looks more readable IMO,
> though
> the usefulness of the underline is debatable:
>
> https://necromuralist.github.io/posts/changing-emacs-font-colors/color_selector.png
>
> Other commands like set-face-foreground, highlight-regexp and others
> show only
> color names, but not the colors themselves.
>
> All color input commands should use a common color selector which
> shows the
> actual colors too.
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.
next prev parent reply other threads:[~2021-03-22 11:33 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 [this message]
2021-03-22 12:11 ` scame via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=D162B40F-C219-4AD2-9A60-1F4BBBAA13E3@gnu.org \
--to=eliz@gnu.org \
--cc=47316@debbugs.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).