From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: org-check.org confusion
Date: Sat, 30 Mar 2013 08:38:21 +0100 [thread overview]
Message-ID: <867gkps5g2.fsf@somewhere.org> (raw)
In-Reply-To: FCEE4469EE8B234199968ECA9B0661E208CD85AE@STNEEX10MB02.stone.ne.gov
Hi David,
"Loyall, David" wrote:
> 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 ^^^.)
When you open f.org, if there is an #f.org# file, Emacs will let you know:
You should recover this file
is displayed in the echo area.
Then, simply type M-x recover-this-file, and answer:
- yes, to overwrite f.org with that auto-saved version
- no, to simply delete #f.org#
FYI, I've customized the color `recover-this-file' with an orange background
in order to clearly see that Emacs has something to tell me, even if I
overlooked the msg in the echo area:
... (recover-this-file ((,class (:background "white" :background "#FF3F3F"))))
Best regards,
Seb
--
Sebastien Vauban
prev parent reply other threads:[~2013-03-30 7:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 20:06 org-check.org confusion Lawrence Bottorff
2013-03-20 20:18 ` Loyall, David
2013-03-20 20:32 ` Christopher Schmidt
2013-03-20 20:41 ` Lawrence Bottorff
2013-03-29 22:15 ` Loyall, David
2013-03-30 7:38 ` Sebastien Vauban [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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=867gkps5g2.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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/org-mode.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).