From: Samuel Wales <email@example.com>
Subject: bug: using remember can cause data corruption in other buffers
Date: Wed, 25 Mar 2009 20:13:28 -0700 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
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
Once this is fixed, I recommend that everybody who used git within the
last day or so, and I think set the remember directory, get the fixed
version and check the value of that variable.
Myalgic encephalomyelitis denialism is causing death (decades early;
Jason et al. 2006) and severe suffering (worse than nearly all other
diseases studied; e.g. Schweitzer et al. 1995) and grossly corrupting
next reply other threads:[~2009-03-26 3:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-26 3:13 Samuel Wales [this message]
2009-03-26 3:20 ` bug: using remember can cause data corruption in other buffers Samuel Wales
2009-03-26 3:40 ` Carsten Dominik
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).