GNU bug report logs - #62106
29.0.60; Emacs 29 changing user option values (?)

Previous Next

Package: emacs;

Reported by: Drew Adams <drew.adams <at> oracle.com>

Date: Fri, 10 Mar 2023 22:17:02 UTC

Severity: normal

Found in version 29.0.60

Fixed in version 29.1

Done: Michael Albinus <michael.albinus <at> gmx.de>

Bug is archived. No further changes may be made.

Full log


View this message in rfc822 format

From: Michael Albinus <michael.albinus <at> gmx.de>
To: Drew Adams <drew.adams <at> oracle.com>
Cc: Michael Heerdegen <michael_heerdegen <at> web.de>, "62106 <at> debbugs.gnu.org" <62106 <at> debbugs.gnu.org>
Subject: bug#62106: 29.0.60; Emacs 29 changing user option values (?)
Date: Sun, 12 Mar 2023 11:09:47 +0100
Drew Adams <drew.adams <at> oracle.com> writes:

Hi Drew,

>> `setopt' does not really help. Using `customize-save-variable' instead
>> of `customize-set-variable' does the trick.
>>
>> Pushed to the emacs-29 branch, closing the bug. Pls reply if it doesn't
>> work as expected.
>
> Thanks for working on this.  Without studying this at all, I'm
> guessing that `customize-save-variable' is the wrong thing to do.
> Doesn't that mean that you're not only changing a user-option value,
> but you're also doing so permanently (persistently)?  If so, isn't
> that even _worse_?

Oops, that's true.

> Wouldn't this be better - pseudo-saving, i.e., making Customize treat a changed option as if it were unchanged, _without_ saving it?
>
> (put SYMBOL 'saved-value
>             (list (custom-quote (default-value SYMBOL)))))

I've tested further, and it looks like `custom-set-variables' does
already what we want. So I've modifed my change in the emacs-29 branch
accordingly.

It would be great if you could counter test once the recent emacs-29
branch is on your laptop.

Best regards, Michael.




This bug report was last modified 2 years and 73 days ago.

Previous Next


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