unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Keshav Kini <keshav.kini@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 18928@debbugs.gnu.org
Subject: bug#18928: 24.4; viper-save-setting produces invalid configuration file
Date: Fri, 4 Dec 2020 03:12:16 -0800	[thread overview]
Message-ID: <5829dbcb-5f0d-c195-3ff5-614fae34fbda@gmail.com> (raw)
In-Reply-To: <87h7p1lud9.fsf@gnus.org>

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






      reply	other threads:[~2020-12-04 11:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-02 20:24 bug#18928: 24.4; viper-save-setting produces invalid configuration file Keshav Kini
2020-12-04 10:48 ` Lars Ingebrigtsen
2020-12-04 11:12   ` Keshav Kini [this message]

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=5829dbcb-5f0d-c195-3ff5-614fae34fbda@gmail.com \
    --to=keshav.kini@gmail.com \
    --cc=18928@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    /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).