GNU bug report logs - #59937
28.2; Bad defcustom behavior

Previous Next

Full log

View this message in rfc822 format

From: Mauro Aranda <maurooaranda <at> gmail.com>
To: "59937 <at> debbugs.gnu.org" <59937 <at> debbugs.gnu.org>
Cc: Drew Adams <drew.adams <at> oracle.com>
Subject: bug#59937: 28.2; Bad defcustom behavior
Date: Sun, 16 Jul 2023 20:00:40 -0300

[Message part 1 (text/plain, inline)]

Hi Drew,

I'm sorry it took me so long to actually take a look at this.  I had to
reread the conversation to put myself back into topic.

As I said in https://debbugs.gnu.org/cgi/bugreport.cgi?bug=59937#26
I was looking for a way to:
1. Being able to create the restricted-sexp widget, even if the default
value for it isn't valid.
2. Being able to do it without prompting the user.

That's what the attached patch does.  AFAIU, we both agreed that that
approach was a good enough fix for this bug, so that the behavior of
certain defcustoms is less confusing.  We didn't really agree back then
about the warning, and I'm guessing that we still disagree on that, so I
didn't change anything about the warning.

[0001-Avoid-prompting-when-creating-a-restricted-sexp-widg.patch (text/x-patch, attachment)]

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.