From: Carsten Dominik <firstname.lastname@example.org>
To: Samuel Wales <email@example.com>
Subject: Re: bug: using remember can cause data corruption in other buffers
Date: Thu, 26 Mar 2009 04:40:18 +0100 [thread overview]
Message-ID: <9F6B930E-B6C7-4C51-AEFA-B3BAA6E318FF@gmail.com> (raw)
On Mar 26, 2009, at 4:13 AM, Samuel Wales wrote:
> Hi Carsten,
> The following form in org-remember.el appears to set the global value.
> (setq auto-save-visited-file-name t)
> This is the right thing for remember buffers, but it should be
> buffer-local. It could lead to data corruption in other buffers if
> you make changes that you don't intend to be permanent.
> I think that
> (set (make-variable-buffer-local ...) t)
> would fix it.
> This might or might not also fix a bug where emacs thinks that another
> process is locking the file that is currently being edited. I don't
> know why.
> Once this is fixed, I recommend that everybody who used git within the
> last day or so, and I think set the remember directory
Yes, this wil only have caused a problem for people who actually set
prev parent reply other threads:[~2009-03-26 3:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 3:13 bug: using remember can cause data corruption in other buffers Samuel Wales
2009-03-26 3:20 ` Samuel Wales
2009-03-26 3:40 ` Carsten Dominik [this message]
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).