From: Juanma Barranquero <lekktu@gmail.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Sean Peters <sean.a.peters@googlemail.com>, 16755-done@debbugs.gnu.org
Subject: bug#16755: 24.3; customize-save-variable saves the wrong value
Date: Wed, 19 Mar 2014 00:32:38 +0100 [thread overview]
Message-ID: <CAAeL0STd_7nGc95Lk28kA1qwcEEWQkw6Kmf0L-hYprouBLUuHQ@mail.gmail.com> (raw)
In-Reply-To: <jwvk3cxmubw.fsf-monnier+emacsbugs@gnu.org>
On Fri, Feb 14, 2014 at 7:23 PM, Stefan Monnier
<monnier@iro.umontreal.ca> wrote:
> So I think the better course is to document that the ":set" function should
> not modify its `val' argument destructively.
Done.
prev parent reply other threads:[~2014-03-18 23:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-14 15:23 bug#16755: 24.3; customize-save-variable saves the wrong value Sean Peters
2014-02-14 18:23 ` Stefan Monnier
2014-03-18 23:32 ` Juanma Barranquero [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=CAAeL0STd_7nGc95Lk28kA1qwcEEWQkw6Kmf0L-hYprouBLUuHQ@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=16755-done@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=sean.a.peters@googlemail.com \
/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).