From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: help-gnu-emacs@gnu.org
Subject: Re: Crashing Emacs, Auto Save Data and org-mode Links
Date: Sat, 19 Apr 2014 11:01:47 +0800 [thread overview]
Message-ID: <877g6m3tus.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87lhv278da.fsf@quasar.esben-stien.name
Esben Stien <b0ef@esben-stien.name> writes:
> When emacs crashes, it leaves behind auto save files. This is all fine
> and dandy.
>
> However, after you've started emacs after a crash and you hit an
> org-mode link, org-mode opens all kinds of files from everywhere, really
> fast, because it's looking for the ID of the org-mode link.
>
> The scanning actually opens the files and you are not really notified about
> what files has been opened and what files needs a M-x
> recover-this-file.
>
> You get a list in the *Messages* buffer and this list can be really long
> if you've not saved your work.
>
> What is the proper procedure after a crash?
>
> Is there some way to scan directories for auto save files and somehow
> clean up?; ie, to get a diff between the actual file and the auto save
> file.
Try `recover-session' -- my understanding is that a list of all valid
auto save files is kept (in my case in ~/.emacs.d/auto-save-list), and
when you come back up after a crash you can do a bulk recover with that
command.
next prev parent reply other threads:[~2014-04-19 3:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 19:20 Crashing Emacs, Auto Save Data and org-mode Links Esben Stien
2014-04-19 3:01 ` Eric Abrahamsen [this message]
2014-04-19 15:22 ` Esben Stien
2014-04-20 3:14 ` Eric Abrahamsen
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=877g6m3tus.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=help-gnu-emacs@gnu.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.
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).