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

Previous Next

Full log

Message #50 received at 59937 <at> debbugs.gnu.org (full text, mbox):

From: Drew Adams <drew.adams <at> oracle.com>
To: Mauro Aranda <maurooaranda <at> gmail.com>, "59937 <at> debbugs.gnu.org"
 <59937 <at> debbugs.gnu.org>
Subject: RE: [External] : Re: bug#59937: 28.2; Bad defcustom behavior
Date: Mon, 17 Jul 2023 15:30:09 +0000

> 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.

I had to reread it just now, to remind myself what
this is all about. ;-)

> 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.

Thanks, Mauro.  I don't have the time now to
check the result, but I have no problem at all
with whatever fix you implemented.  If later
(probably much later) I find something I think
could be improved more in this regard, I'll
file a new enhancement/bug request.

Thx!

Previous Next

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