From: Yuan Fu <casouri@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Stefan Kangas <stefankangas@gmail.com>,
62562@debbugs.gnu.org, juri@linkov.net
Subject: bug#62562: 30.0.50; [PATCH] Some new SVG icons
Date: Sun, 2 Apr 2023 15:05:13 -0700 [thread overview]
Message-ID: <03B418A7-ACF5-481B-862A-462753D92F8D@gmail.com> (raw)
In-Reply-To: <83wn2uwyox.fsf@gnu.org>
> On Apr 2, 2023, at 12:06 AM, Eli Zaretskii <eliz@gnu.org> wrote:
>
>> From: Yuan Fu <casouri@gmail.com>
>> Date: Sat, 1 Apr 2023 12:38:39 -0700
>> Cc: Stefan Kangas <stefankangas@gmail.com>,
>> 62562@debbugs.gnu.org,
>> Juri Linkov <juri@linkov.net>
>>
>> I wonder if there could be a command like list-icon-images that shows users
>> the icon images they can use?
>
> Isn't that what image-dired does?
I was thinking of a discovery command, which shows package authors what icon images they can use out-of-the-box, and maybe show the path pass to create-image. They could simply go to image-load-path and call image-dired, but that assumes some degree of familiarity with Emacs and how we use icon images.
Yuan
next prev parent reply other threads:[~2023-04-02 22:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-31 5:52 bug#62562: 30.0.50; [PATCH] Some new SVG icons Yuan Fu
2023-03-31 6:12 ` Eli Zaretskii
2023-04-01 19:38 ` Yuan Fu
2023-04-01 19:41 ` Yuan Fu
2023-04-02 6:56 ` Juri Linkov
2023-04-02 7:06 ` Eli Zaretskii
2023-04-02 22:05 ` Yuan Fu [this message]
2023-04-02 16:27 ` Juri Linkov
2023-04-03 6:37 ` Juri Linkov
2023-04-03 7:55 ` Yuan Fu
2023-04-03 16:23 ` Juri Linkov
2023-04-03 20:17 ` Yuan Fu
2023-04-04 6:50 ` Juri Linkov
2023-05-02 17:10 ` Juri Linkov
2023-08-27 17:27 ` Juri Linkov
2023-08-27 21:42 ` Yuan Fu
2023-08-31 21:00 ` Rudolf Adamkovič via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-09-01 6:58 ` Juri Linkov
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=03B418A7-ACF5-481B-862A-462753D92F8D@gmail.com \
--to=casouri@gmail.com \
--cc=62562@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=juri@linkov.net \
--cc=stefankangas@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).