From: Stefan Kangas <stefan@marxist.se>
To: Eli Zaretskii <eliz@gnu.org>
Cc: jporterbugs@gmail.com, 51556@debbugs.gnu.org, kevin.legouguec@gmail.com
Subject: bug#51556: 29.0.50; Poor contrast of Customize SVG icons with dark backgrounds
Date: Tue, 2 Nov 2021 12:44:45 -0700 [thread overview]
Message-ID: <CADwFkmnLAEfS+y5bVRS24y_0iAV-_nkSpf024WjAKFXSB2ykXw@mail.gmail.com> (raw)
In-Reply-To: <8335oejrn8.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
>> > If you're the author of a little-known package, you can't really
>> > expect theme authors to provide customized icons for your package that
>> > fit with the theme. However, themes *do* specify at least a handful of
>> > faces. As a package author, it would be convenient to be able to say
>> > "render this icon using the foreground color of the `error' face", for
>> > example. Then your package looks good with most themes without
>> > requiring anyone to provide custom SVGs.
>>
>> Exactly the point. This goes for built-in packages as well.
>
> How come built-in packages qualify as "little-known"?
They don't. I'm saying that the above points apply whether or not a
package is "little-known", "well-known" or even "built-in".
next prev parent reply other threads:[~2021-11-02 19:44 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 17:56 bug#51556: 29.0.50; Poor contrast of Customize SVG icons with dark backgrounds Kévin Le Gouguec
2021-11-01 19:14 ` Eli Zaretskii
2021-11-01 20:10 ` Kévin Le Gouguec
2021-11-02 12:40 ` Eli Zaretskii
2021-11-01 20:49 ` Jim Porter
2021-11-02 12:49 ` Eli Zaretskii
2021-11-02 14:41 ` Stefan Kangas
2021-11-02 14:59 ` Eli Zaretskii
2021-11-02 15:17 ` Stefan Kangas
2021-11-02 15:26 ` Stefan Kangas
2021-11-02 16:38 ` Eli Zaretskii
2021-11-02 16:43 ` Lars Ingebrigtsen
2021-11-02 17:01 ` Stefan Kangas
2021-11-02 17:13 ` Eli Zaretskii
2021-11-02 17:44 ` Stefan Kangas
2021-11-02 18:01 ` Eli Zaretskii
2021-11-02 18:43 ` Stefan Kangas
2021-11-02 18:53 ` Eli Zaretskii
2021-11-02 19:26 ` Stefan Kangas
2021-11-02 18:43 ` Jim Porter
2021-11-02 18:58 ` Stefan Kangas
2021-11-02 19:15 ` Eli Zaretskii
2021-11-02 19:44 ` Stefan Kangas [this message]
2021-11-02 20:19 ` Alan Third
2021-11-02 22:56 ` Kévin Le Gouguec
2021-11-04 8:11 ` Eli Zaretskii
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=CADwFkmnLAEfS+y5bVRS24y_0iAV-_nkSpf024WjAKFXSB2ykXw@mail.gmail.com \
--to=stefan@marxist.se \
--cc=51556@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jporterbugs@gmail.com \
--cc=kevin.legouguec@gmail.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).