From: Eli Zaretskii <eliz@gnu.org>
To: Jimmy Wong <wyuenho@gmail.com>
Cc: 63891@debbugs.gnu.org
Subject: bug#63891: 29.0.91; customize-save-variable should not save all variables if a custom file exists
Date: Sun, 04 Jun 2023 16:23:56 +0300 [thread overview]
Message-ID: <83jzwj5pjn.fsf@gnu.org> (raw)
In-Reply-To: <28e951a5-7065-4c55-b6d0-88238e8cc5eb@Spark> (message from Jimmy Wong on Sun, 4 Jun 2023 14:02:55 +0100)
> Date: Sun, 4 Jun 2023 14:02:55 +0100
> From: Jimmy Wong <wyuenho@gmail.com>
> Cc: 63891@debbugs.gnu.org
>
> Yes sorry, I mean customize-save-variable, custom-save-variable doesn’t exist. There’s a branch in
> customize-save-variable that saves all previously updated variables to the custom file if it exists.
I don't think I understand. customize-save-variable saves only a
single variable: the one whose name you type, with the value you type.
Which branch there does more, and how can you invoke that branch?
> I just took a look at cus-edit.el, there appears to be no function that can surgically serialize just one
> variable value to the custom file.
customize-save-variable is that function.
next prev parent reply other threads:[~2023-06-04 13:23 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-04 12:36 bug#63891: 29.0.91; customize-save-variable should not save all variables if a custom file exists Jimmy Yuen Ho Wong
2023-06-04 12:56 ` Eli Zaretskii
2023-06-04 13:02 ` Jimmy Wong
2023-06-04 13:23 ` Eli Zaretskii [this message]
2023-06-04 14:00 ` Jimmy Wong
2023-06-04 14:26 ` Eli Zaretskii
2023-06-04 16:49 ` Jimmy Wong
2023-06-06 12:01 ` Michael Albinus
2023-06-06 12:20 ` Eli Zaretskii
2023-06-06 12:36 ` Michael Albinus
[not found] <ae449be5-9a4c-4e7e-b624-deae8a27fbbb@gmail.com>
2023-10-27 10:57 ` Mauro Aranda
2023-10-27 11:51 ` Michael Albinus
2023-10-27 15:44 ` Mauro Aranda
2023-10-28 9:58 ` Mauro Aranda
2023-10-28 18:22 ` Drew Adams
2023-10-28 22:32 ` Mauro Aranda
2023-10-29 2:20 ` Drew Adams
2023-10-29 10:33 ` Mauro Aranda
2023-10-29 11:07 ` Michael Albinus
2023-10-29 11:50 ` Mauro Aranda
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=83jzwj5pjn.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=63891@debbugs.gnu.org \
--cc=wyuenho@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 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.