unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: stefankangas@gmail.com, 66635@debbugs.gnu.org
Subject: bug#66635: 30.0.50; customize-icon State button doesn't work (never did)
Date: Sat, 21 Oct 2023 10:35:09 +0300	[thread overview]
Message-ID: <83cyx8sa1e.fsf@gnu.org> (raw)
In-Reply-To: <1034a4cb-217a-4e60-a474-bf07948e3dd1@gmail.com> (message from Mauro Aranda on Fri, 20 Oct 2023 21:21:34 -0300)

> Date: Fri, 20 Oct 2023 21:21:34 -0300
> From: Mauro Aranda <maurooaranda@gmail.com>
> 
> On 20/10/23 18:08, Stefan Kangas wrote:
>  > Mauro Aranda <maurooaranda@gmail.com> writes:
>  >
>  >> I attach a patch to address the more important issues for now.  That is,
>  >> at least have a working State button and rudimentary state checking.
>  >>
>  >> Setting and Saving icon specifications through the State button should
>  >> work now, by adding the custom-icon-action function.
>  >
>  >
>  > Thanks for working on this.
>  >
>  > Do you propose this patch for emacs-29?  It seems quite intrusive on the
>  > face of it, but OTOH `customize-icon' is new in Emacs 29, so there is no
>  > risk of regressions if this stuff never worked in the first place.  Or
>  > is that wrong?
> 
> I'm not aware of all things you and Eli have to take into account when
> deciding whether a patch is good for emacs-29.  I know the non-intrusive
> or localized, and the safe part.  This patch is certainly neither, but
> it's the minimum (OK, maybe not the bare minimum) to make customizing
> icons work for an user.  I think that's a good reason for the patch to
> go into emacs-29, but I won't be insisting on it, specially if it is a
> burden, considering 29.1.90 pretest is out.

icons.el is a new package in Emacs 29, so maybe such changes in it to
fix a serious problem are okay even at this stage.

How well is the fix tested?  Did you test it with several icons
introduced in Emacs 29 in various modes?  If not, would you please
test those and see the changes work well enough there to be
appropriate for a bug-fix release?

Thanks.





  reply	other threads:[~2023-10-21  7:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-19 11:18 bug#66635: 30.0.50; customize-icon State button doesn't work (never did) Mauro Aranda
2023-10-19 11:53 ` Mauro Aranda
2023-10-20 21:08   ` Stefan Kangas
2023-10-21  0:21     ` Mauro Aranda
2023-10-21  7:35       ` Eli Zaretskii [this message]
2023-10-21 10:18         ` Mauro Aranda
2023-10-21 11:09           ` Mauro Aranda
2023-10-21 11:17             ` Stefan Kangas
2023-10-21 11:33               ` Eli Zaretskii
2023-10-21 11:51                 ` Stefan Kangas
2023-10-21 12:28                   ` Mauro Aranda
2023-10-22 12:09                     ` Stefan Kangas
2023-10-22 12:46                       ` Mauro Aranda
2023-10-22 16:51                         ` Stefan Kangas
2023-10-21 11:19           ` 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=83cyx8sa1e.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=66635@debbugs.gnu.org \
    --cc=maurooaranda@gmail.com \
    --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).