From: Michael Albinus <michael.albinus@gmx.de>
To: Drew Adams <drew.adams@oracle.com>
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
"62106@debbugs.gnu.org" <62106@debbugs.gnu.org>
Subject: bug#62106: 29.0.60; Emacs 29 changing user option values (?)
Date: Sun, 12 Mar 2023 11:09:47 +0100 [thread overview]
Message-ID: <87a60i46xg.fsf@gmx.de> (raw)
In-Reply-To: <SJ0PR10MB54882A96BE8EDA84CDC14883F3BB9@SJ0PR10MB5488.namprd10.prod.outlook.com> (Drew Adams's message of "Sat, 11 Mar 2023 17:09:42 +0000")
Drew Adams <drew.adams@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.
next prev parent reply other threads:[~2023-03-12 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-10 22:16 bug#62106: 29.0.60; Emacs 29 changing user option values (?) Drew Adams
2023-03-11 2:32 ` Corwin Brust
2023-03-11 3:29 ` Michael Heerdegen
2023-03-11 16:34 ` Michael Albinus
2023-03-11 17:09 ` Drew Adams
2023-03-12 10:09 ` Michael Albinus [this message]
2023-03-12 15:16 ` Drew Adams
2023-03-12 16:37 ` Michael Albinus
2023-03-12 6:19 ` Augusto Stoffel
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a60i46xg.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=62106@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=michael_heerdegen@web.de \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.