Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: Threading problems
Date: Tue, 11 Feb 2003 19:27:40 +0100	[thread overview]
Message-ID: <v9y94mzn8j.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <868ywn0yqp.fsf@wintermute.g2ctech> (Jorge Godoy's message of "Tue, 11 Feb 2003 10:48:30 -0200")

On Tue, Feb 11 2003, Jorge Godoy wrote:

> Lars Magne Ingebrigtsen <larsi@quimbies.gnus.org> writes:
[...]
>> The References header is supposed to be generated when the message is
>> saved to the draft buffer.  Doesn't this happen to you?
>>
>> (When I pressed `C-x C-s', Emacs generated three new headers --
>> References, From and X-Draft-From.  I hadn't actually seen that in
>> action before.  Neat.  :-)
>
> It does... The 'autosave' (that puts the message on drafts while I'm
> writing it or when there's a crash) doesn't. 

I've seen the same here yesterday: No References in an outgoing
posting after resuming a message from an autosave file.

Jorge, you may set message-generate-headers-first to '(References):

,----[ C-h v message-generate-headers-first RET ]
| message-generate-headers-first's value is (References)
| 
| Documentation:
| [...]
| This can also be a list of headers that should be generated before
| composing.
`----

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo--- PGP key available via WWW   http://rsteib.home.pages.de/



  reply	other threads:[~2003-02-11 18:27 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08 23:04 Jorge Godoy
2003-02-08 23:54 ` Lars Magne Ingebrigtsen
2003-02-08 23:57   ` Jorge Godoy
2003-02-09  0:01     ` Lars Magne Ingebrigtsen
2003-02-09 11:38       ` Jorge Godoy
2003-02-11  1:34         ` Lars Magne Ingebrigtsen
2003-02-11 12:48           ` Jorge Godoy
2003-02-11 18:27             ` Reiner Steib [this message]
2003-02-12  0:48               ` Jorge Godoy

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=v9y94mzn8j.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).