From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Crashing Emacs and unfinished drafts
Date: 07 Mar 2001 17:19:18 +0100 [thread overview]
Message-ID: <vaf8zmhimbd.fsf@lucy.cs.uni-dortmund.de> (raw)
When Emacs crashes while I'm composing a message in Gnus, I expect
the associated auto-save file to appear in the nndraft:drafts group.
It happened to me just a couple of minutes ago.¹ A file
~/News/drafts/drafts/#42#, say, was left behind. However, Gnus does
not recognize this file.
After `mv #42# 42', all is dandy and Gnus sees the draft.
So, we have two alternatives:
(1) Have Emacs auto-save into ~/News/drafts/drafts/42 rather than
~/News/drafts/drafts/#42#.
(2) Have nndraft.el grok the #42# style filenames.
Or should I have done a M-x recover-session RET before starting Gnus?
But Gnus deals automatically with its ~/.newsrc auto-save file,
doesn't it?
kai
--
Be indiscrete. Do it continuously.
next reply other threads:[~2001-03-07 16:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-07 16:19 Kai Großjohann [this message]
2001-03-07 16:36 ` Crashing Emacs and unsaved nnfolders Alan Shutko
2001-03-07 18:31 ` ShengHuo ZHU
2001-03-07 19:12 ` Alan Shutko
2001-03-07 18:20 ` Crashing Emacs and unfinished drafts ShengHuo ZHU
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vaf8zmhimbd.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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 NNTP newsgroup(s).