GNU bug report logs - #63891
29.0.91; customize-save-variable should not save all variables if a custom file exists

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Michael Albinus <michael.albinus <at> gmx.de>
Cc: wyuenho <at> gmail.com, 63891 <at> debbugs.gnu.org
Subject: bug#63891: 29.0.91; customize-save-variable should not save all variables if a custom file exists
Date: Tue, 06 Jun 2023 15:20:03 +0300

> From: Michael Albinus <michael.albinus <at> gmx.de>
> Cc: Jimmy Wong <wyuenho <at> gmail.com>,  63891 <at> debbugs.gnu.org
> Date: Tue, 06 Jun 2023 14:01:22 +0200
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> Hi Eli,
> 
> >> 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.
> 
> custom-set-variables

That's a different function.  I was talking about
customize-save-variable.

Previous Next

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