GNU bug report logs -
#18928
24.4; viper-save-setting produces invalid configuration file
Previous Next
Reported by: Keshav Kini <keshav.kini <at> gmail.com>
Date: Sun, 2 Nov 2014 20:26:02 UTC
Severity: normal
Tags: fixed
Found in version 24.4
Fixed in version 28.1
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Keshav Kini <keshav.kini <at> gmail.com> writes:
> Steps to reproduce:
>
> 1) Run `emacs -Q`.
> 2) Execute the following elisp in the scratch buffer:
>
> (require 'viper-util)
> (setq x 3)
> (viper-save-setting 'x nil "/tmp/.viper")
> (setq x 4)
> (viper-save-setting 'x nil "/tmp/.viper")
>
> Expected result:
>
> /tmp/.viper should contain "(setq x '4)"
>
> Actual result:
>
> /tmp/.viper contains "(setq x '4 '3)"
(This bug report unfortunately got no response at the time.)
Thanks for the clear recipe. I've now fixed this particular error in
Emacs 28, but as you point out, this really should be fixed in a
different way -- using Customize would be ideal, but there's always
backwards compatibility issues.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
This bug report was last modified 4 years and 250 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.