unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 57113@debbugs.gnu.org
Subject: bug#57113: 29.0.50; Confusing icon customization interface
Date: Sat, 13 Aug 2022 20:48:32 +0800	[thread overview]
Message-ID: <87tu6gs40v.fsf@yahoo.com> (raw)
In-Reply-To: <87v8qwgw2l.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 13 Aug 2022 14:35:46 +0200")

Lars Ingebrigtsen <larsi@gnus.org> writes:

> See icons.el.

That doesn't help, since I want to change an existing icon, not
introduce a new one.

> You've probably never seen another system that had just introduced a new
> language level mechanism for icons a couple weeks earlier, either?

Language-level mechanism?

> Like I said, fixing Customize to be less awful would be very welcome.

It's not a problem with Customize.  Customize is for customizing faces
and variables.  `customize-icon' is something new, so the problem is
there.

> Please go ahead.

I'm afraid I don't understand how icons.el is supposed to work, and it
seems overcomplicated.

How about replacing it with something straightforward, such as a single
function insert-icon, which inserts the appropriate icon according to a
list of image specs?  Then, the first image in the list that can be
displayed is inserted into the buffer.

Fallback text can also be supplied as the last element of the list, and
is displayed on terminals that do not support images.





  reply	other threads:[~2022-08-13 12:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87h72kxq18.fsf.ref@yahoo.com>
2022-08-10 12:05 ` bug#57113: 29.0.50; Confusing icon customization interface Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-12 15:32   ` Lars Ingebrigtsen
2022-08-12 17:49     ` Eli Zaretskii
2022-08-13  1:57     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 12:01       ` Lars Ingebrigtsen
2022-08-13 12:14         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 12:23           ` Lars Ingebrigtsen
2022-08-13 12:30             ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-13 12:35               ` Lars Ingebrigtsen
2022-08-13 12:48                 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
2022-08-15  5:45                   ` Lars Ingebrigtsen
2022-08-15  6:51                     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-08-15  6:53                       ` Lars Ingebrigtsen
2022-08-15  7:31                         ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-11-06 11:12   ` Mauro Aranda
2023-11-06 13:00     ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors

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=87tu6gs40v.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=57113@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --cc=luangruo@yahoo.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).