From: Mauro Aranda <maurooaranda@gmail.com>
To: Michael Albinus <michael.albinus@gmx.de>
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: Fri, 27 Oct 2023 12:44:17 -0300 [thread overview]
Message-ID: <61df90f1-c097-42cf-97c6-1186e49d2f88@gmail.com> (raw)
In-Reply-To: <874jicgu5w.fsf@gmx.de>
On 27/10/23 08:51, Michael Albinus wrote:
> Mauro Aranda <maurooaranda@gmail.com> writes:
>
> Hi Mauro,
>
>>> custom-set-variables sets the saved-value property of the
>>> variables. This is what is called in connection-local-set-profiles and
>>> connection-local-set-profile-variables.
>>
>> Why do those functions use custom-set-variables, instead of
>> customize-set-variable?
>
> This is what we have used before. Due to bug#62106 we cannot use
> customize-set-variable.
>
I see, thanks. I'll study this more carefully.
next prev parent reply other threads:[~2023-10-27 15:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ae449be5-9a4c-4e7e-b624-deae8a27fbbb@gmail.com>
2023-10-27 10:57 ` bug#63891: 29.0.91; customize-save-variable should not save all variables if a custom file exists Mauro Aranda
2023-10-27 11:51 ` Michael Albinus
2023-10-27 15:44 ` Mauro Aranda [this message]
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
2023-06-04 12:36 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
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
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=61df90f1-c097-42cf-97c6-1186e49d2f88@gmail.com \
--to=maurooaranda@gmail.com \
--cc=63891@debbugs.gnu.org \
--cc=michael.albinus@gmx.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.