From: Thomas Fitzsimmons <fitzsim@fitzsim.org>
To: Mauro Aranda <maurooaranda@gmail.com>
Cc: 63290@debbugs.gnu.org
Subject: bug#63290: 30.0.50; Customize UI shows extra fields for (choice (const ...) (alist ...))
Date: Sun, 16 Jul 2023 22:37:21 -0400 [thread overview]
Message-ID: <m31qh76z6m.fsf@fitzsim.org> (raw)
In-Reply-To: <136334d9-262d-e290-cff3-159c2f827b87@gmail.com> (Mauro Aranda's message of "Sun, 16 Jul 2023 10:15:26 -0300")
Mauro Aranda <maurooaranda@gmail.com> writes:
> Thomas Fitzsimmons <fitzsim@fitzsim.org> writes:
[...]
>> It seems like after a const is shown, Customize considers the
>> variable "edited". I don't know why it is adding those extra
>> INS/DEL key/value UI boxes though.
>
> The code currently ignores the value if it's present but
> nil. That's not good, obviously. But it might be tricky to fix
> it because other widgets depend on the code ignoring it...
>
> I think it might be good to have a different property specify a
> default value (defaulting to :value upon creation, if not
> provided), and let :value be treated as of today, like the
> current value holder.
OK, thanks for taking a look; let me know if you want me to try a
patch. Sounds like a good way of maintaining backward
compatibility with respect to other widgets.
Or you can test it against excorporate-configuration in GNU ELPA;
just search for the FIXME that mentions this bug report.
Thanks,
Thomas
next prev parent reply other threads:[~2023-07-17 2:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 6:02 bug#63290: 30.0.50; Customize UI shows extra fields for (choice (const ...) (alist ...)) Thomas Fitzsimmons
2023-07-16 13:15 ` Mauro Aranda
2023-07-17 2:37 ` Thomas Fitzsimmons [this message]
2023-08-09 12:19 ` Mauro Aranda
2023-08-09 12:53 ` Eli Zaretskii
2023-08-09 15:51 ` Thomas Fitzsimmons
2023-08-09 15:56 ` Mauro Aranda
2023-08-09 18:03 ` Mauro Aranda
2023-08-10 22:58 ` Mauro Aranda
2023-08-11 13:29 ` Thomas Fitzsimmons
2023-08-15 22:46 ` Mauro Aranda
2023-08-16 15:16 ` Thomas Fitzsimmons
2023-08-19 8:34 ` Eli Zaretskii
2023-08-21 12:23 ` Mattias Engdegård
2023-08-21 14:43 ` Mauro Aranda
2023-08-21 15:24 ` Mattias Engdegård
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=m31qh76z6m.fsf@fitzsim.org \
--to=fitzsim@fitzsim.org \
--cc=63290@debbugs.gnu.org \
--cc=maurooaranda@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).