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 17:26:43 +0300 [thread overview]
Message-ID: <83h6rn5mn0.fsf@gnu.org> (raw)
In-Reply-To: <b29dfb16-e8c1-4a8b-9fce-6f8dc8aeec54@Spark> (message from Jimmy Wong on Sun, 4 Jun 2023 15:00:01 +0100)
> Date: Sun, 4 Jun 2023 15:00:01 +0100
> From: Jimmy Wong <wyuenho@gmail.com>
> Cc: 63891@debbugs.gnu.org
>
> This branch: https://github.com/emacs-mirror/emacs/blob/emacs-29/lisp/cus-edit.el#L1109
I don't know what that is. I'm using the Emacs Git repository, the
emacs-29 branch.
> No it does not saves only one variable to file, it only saves one variable to file if you have only modified
> one variable.
That's not what I see. I've modified several options using the
menu-bar's Options menu, then typed
M-x customize-save-variable RET truncate-lines RET y
and saw that only truncate-lines was written to the custom file.
If you see something else, please show a complete recipe that
reproduces the behavior you see.
> As a matter of fact, custom-variable-save, custom-variable-mark-to-reset-standard,
> custom-face-save, custom-face-mark-to-reset-standard and custom-group-save all have the same
> problem. They all call custom-save-all and they all dump all modified customizable variable values on
> file without regard to whether it’s a single variable, face or a group the user asked Emacs to save.
I wasn't talking about custom-save-all -- that indeed saves all the
options customized in this session. I was talking about
customize-save-variable, which prompts for a single variable and its
value, and saves only that single variable, at least in my testing.
next prev parent reply other threads:[~2023-06-04 14:26 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
2023-06-04 14:00 ` Jimmy Wong
2023-06-04 14:26 ` Eli Zaretskii [this message]
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83h6rn5mn0.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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).