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 14:19:32 +0300	[thread overview]
Message-ID: <83y1fwql2z.fsf@gnu.org> (raw)
In-Reply-To: <eb62d217-9604-46c8-b075-e9ab6657a8fc@gmail.com> (message from Mauro Aranda on Sat, 21 Oct 2023 07:18:31 -0300)

> Date: Sat, 21 Oct 2023 07:18:31 -0300
> Cc: stefankangas@gmail.com, 66635@debbugs.gnu.org
> From: Mauro Aranda <maurooaranda@gmail.com>
> 
> On 21/10/23 04:35, Eli Zaretskii wrote:
>  > 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?
> 
> I just tested with the button icon, the only one suggested after
> running emacs -Q.  I tested making modifications in the buffer, and that
> the two options (three if not started with -Q) work and do what's
> intended.  Namely:
> - Undo Editions took me back to the STANDARD state.
> - Setting for the session modified the specs for the session and
> correctly displayed the SET state.
> - Saving the setting saved a spec that in a new session (without emacs
> -Q) causes:
> M-x describe-icon RET button
> to show the button customized.  The value I changed for that was from
> LARGE BLUE CIRCLE to LARGE RED SQUARE
> 
> It's important to note that saving the setting shows the SET state
> (rather than the SAVED state), but that's in a FIXME right before
> custom-icon-state.
> 
> I'll do some more testing with the icons defined in outline.el,
> tab-bar.el and warnings.el.  Additionally I'll try to test if
> Customizing an icon interacts good enough with a Theme customizations.
> I'll do that and report back.

Thanks.





      parent reply	other threads:[~2023-10-21 11:19 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
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 [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=83y1fwql2z.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).