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: Fri, 11 Aug 2023 09:29:24 -0400 [thread overview]
Message-ID: <m3cyztso5n.fsf@fitzsim.org> (raw)
In-Reply-To: <6f1b1234-ed8c-5391-4646-2e7db5dfa8d0@gmail.com> (Mauro Aranda's message of "Thu, 10 Aug 2023 19:58:24 -0300")
Mauro Aranda <maurooaranda@gmail.com> writes:
> Thomas Fitzsimmons <fitzsim@fitzsim.org> writes:
>
>> Hi Mauro,
>>
>> Mauro Aranda <maurooaranda@gmail.com> writes:
>>
>>> 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)?
>
> I think this ammended patch fixes it. Since we want
> widget-list-default-get to respect a nil :value property, the
> alist widget needs to be modified so that its default value is
> nil.
With the updated patch, when I select "EWS URL OAuth 2.0 settings
(no autodiscovery)", all the widgets are disabled. The blank
values are no longer added though. However, if I then set the
value, without configuring anything, excorporate-configuration
stays nil. So I don't think the patch is correct yet.
Thomas
next prev parent reply other threads:[~2023-08-11 13:29 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
2023-08-10 22:58 ` Mauro Aranda
2023-08-11 13:29 ` Thomas Fitzsimmons [this message]
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=m3cyztso5n.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).