Well, to access the documentation about this:
M-: (info "(emacs)Interlocking") <RET>
...This tells us that the file you saw in the directory is a lock.
The solution is to remove the lock, then try again.
But how do I, also an Emacs newbie, know that? Well, lock files aren't
peculiar to Emacs. Have a look:
http://en.wikipedia.org/wiki/File_locking#Lock_files
:)
How do you remove the lock? Well, first close all your Emacs buffers (on any
machine, anywhere) that are pointed at the org-check.org file. Then see if the
lock file is still there. If it's there, and you're not editing the file in an
Emacs buffer, than the lock is stale. Manually delete it. (Alternatively,
Emacs has some user interface for doing this. It is described in that info
page ^^^.)
Incidentally, the #org-check.org# file is some sort of automatically saved
backup.
Hope this helps,
--Dave
p.s. I have no idea what org-check.org is, but I presume that some org process
normally writes to it, and in your case, it respected the lock, but didn't
prompt you, or it did prompt you and you gave some answer other than "steal the
lock".
---------
From: emacs-orgmode-bounces+david.loyall=nebraska....@gnu.org
[mailto:emacs-orgmode-bounces+david.loyall=nebraska....@gnu.org] On Behalf Of
Lawrence Bottorff
Sent: Wednesday, March 20, 2013 15:42 PM
To: emacs-orgmode@gnu.org
Subject: Re: [O] org-check.org confusion
Any details about how this is involved with this issue? I have an
#org-check.org# in this directory too. Being totally a beginner with elisp
hacking, I don't know how to trace out this behavior.
On Wed, Mar 20, 2013 at 3:32 PM, Christopher Schmidt
<christop...@ch.ristopher.com> wrote:
"Loyall, David" <david.loy...@nebraska.gov> writes:
> Dear orgmode users: what does that represent?
(info "(emacs)Interlocking")
Christopher
