From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Missing `References:' header after crash
Date: Mon, 21 Apr 2003 22:21:14 +0200 [thread overview]
Message-ID: <v98yu38uv9.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3y92vlz10.fsf@quimbies.gnus.org>
On Tue, Apr 01 2003, Lars Magne Ingebrigtsen wrote:
> deskpot@despammed.com (Vasily Korytov) writes:
>
>> IMHO, a proper solution is to dump all the buffer-local varibables (for
>> the message buffer) in another file (so it gets autosaved). Say
>> drafts/env/42 or drafts/drafts/42-env, where 42 is the number, same as
>> in drafts/drafts.
>
> I think that's a good idea.
I've set the default of message-generate-headers-first to
'(references) now.
If somebody implements the proper solution, we can change it back to
nil.
Bye, Reiner.
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
prev parent reply other threads:[~2003-04-21 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-31 21:18 Reiner Steib
2003-03-31 21:34 ` Vasily Korytov
2003-04-01 2:41 ` Lars Magne Ingebrigtsen
2003-04-21 20:21 ` Reiner Steib [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=v98yu38uv9.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.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).