[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#18928: 24.4; viper-save-setting produces invalid configuration file
|
From: |
Keshav Kini |
|
Subject: |
bug#18928: 24.4; viper-save-setting produces invalid configuration file |
|
Date: |
Fri, 4 Dec 2020 03:12:16 -0800 |
|
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0 |
On 12/4/20 2:48 AM, Lars Ingebrigtsen wrote:
> Keshav Kini <keshav.kini@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.
Indeed. Thanks for the fix!
-Keshav