From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 15977@debbugs.gnu.org, Juri Linkov <juri@linkov.net>
Subject: bug#15977: 24.3.50; enhancement request: `sample' for Customize colors should show fg & bg
Date: Wed, 26 Jan 2022 18:08:15 +0100 [thread overview]
Message-ID: <87v8y6pgqo.fsf@gnus.org> (raw)
In-Reply-To: <87a7c9sydb.fsf@mouse.gnus.org> (Lars Ingebrigtsen's message of "Thu, 15 Aug 2019 18:16:48 -0700")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> Thanks for the recipe. Yes, I agree with you -- it would be better if
> it also showed this colour as a background (i.e., block), which would
> make it easier to determine whether to use the colour. And like Juri
> says, it should probably be two samples, one as a foreground and one as
> a background.
I had a peek at this, and the sample faces come from here:
(define-widget 'color 'editable-field
"Choose a color name (with sample)."
:format "%{%t%}: %v (%{sample%})\n"
:value-create 'widget-color-value-create
:size (1+ (apply #'max 13 ; Longest RGB hex string.
(mapcar #'length (defined-colors))))
:tag "Color"
:value "black"
:completions (defined-colors)
:sample-face-get 'widget-color-sample-face-get
But of course, you can't have two samples in the :format, I think?
So... you'd have to create... er... a sub widget? OK, I give up.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-01-26 17:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 23:09 bug#15977: 24.3.50; enhancement request: `sample' for Customize colors should show fg & bg Drew Adams
2019-08-15 2:35 ` Lars Ingebrigtsen
2019-08-15 4:33 ` Drew Adams
2019-08-15 8:13 ` martin rudalics
2019-08-15 13:56 ` Drew Adams
2019-08-15 18:51 ` Juri Linkov
2019-08-16 1:16 ` Lars Ingebrigtsen
2022-01-26 17:08 ` Lars Ingebrigtsen [this message]
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=87v8y6pgqo.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=15977@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=juri@linkov.net \
/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).