From: Mauro Aranda <maurooaranda@gmail.com>
To: Thomas Fitzsimmons <fitzsim@fitzsim.org>
Cc: 63290@debbugs.gnu.org
Subject: bug#63290: 30.0.50; Customize UI shows extra fields for (choice (const ...) (alist ...))
Date: Wed, 9 Aug 2023 15:03:24 -0300 [thread overview]
Message-ID: <e5156a07-ae36-87c5-ff9e-8bbf94c78826@gmail.com> (raw)
In-Reply-To: <m3wmy4rz8b.fsf@fitzsim.org>
Thomas Fitzsimmons <fitzsim@fitzsim.org> writes:
> Hi Mauro,
>
> Mauro Aranda <maurooaranda@gmail.com> writes:
>
>> tags 63290 patch quit I ended up adding a custom :default-get
>> function for the list widget, to make it respect a nil value as the
>> :value. This should be backward compatible with other widgets, and
>> should fix these "ghost" elements insertions. I also added a test
>> for cus-edit-tests.
>
> Can you try this patch with:
>
> M-x package-install RET excorporate RET
>
> Then:
>
> M-x customize-variable RET excorporate-configuration RET
>
> then select "Value Menu" and 3, which is "EWS URL OAuth 2.0 settings
> (no autodiscovery)". With your wis-edit.el patch applied I still get
> empty values for:
>
> INS DEL Argument name: Argument value:
>
> and:
>
> INS DEL OAuth 2.0 setting name: OAuth 2.0 setting
> value:
>
> and when I apply the setting the value contains: (... (... (#1#
> . #1#)) (#1# . #1#))
>
> Maybe this is a more complicated case than the test case I provided
> (which does now work for me with your patch)?
>
> Thanks,
> Thomas
I took a look and this seems to have something to do with how the alist
widget (and almost surely the plist widget) get created when they have
:options. I'm not sure yet, and I don't totally understand what's
happening as of now, but I wanted to report back.
I'll try to investigate and see how this can be fixed, but it's going to
take me some time.
next prev parent reply other threads:[~2023-08-09 18:03 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
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 [this message]
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=e5156a07-ae36-87c5-ff9e-8bbf94c78826@gmail.com \
--to=maurooaranda@gmail.com \
--cc=63290@debbugs.gnu.org \
--cc=fitzsim@fitzsim.org \
/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).