From: Hanak David <dhanak@inf.bme.hu>
Subject: Required mail & news headers
Date: Tue, 10 Jun 2003 12:03:32 +0200 [thread overview]
Message-ID: <m2znkqb66j.fsf@maui.hanak.hu> (raw)
Hi,
I discovered, that the contents of 'message-required-headers' are always
rendered *before* composing the message, as opposed to
'message-required-news-headers' and 'message-required-mail-headers', which
are affected by the value of 'message-generate-headers-first':
/----
| message-generate-headers-first's value is (references)
|
| Documentation:
| *If non-nil, generate all required headers before composing.
| The variables `message-required-news-headers' and
| `message-required-mail-headers' specify which headers to generate.
| This can also be a list of headers that should be generated before
| composing.
\----
I don't want to see that X-Draft-From line, nor the From header, nor the
very long Face header whilst composing my message. The latter can be
hidden by adding it both to ...mail-headers and ...news-headers instead of
adding it once to ...required-headers, but that doesn't seem nice.
'message-generate-headers' is readded to the headers-to-be-inserted list
(after being filtered by 'message-headers-to-generate'):
/----
| (defun message-generate-headers (headers)
| "Prepare article HEADERS.
| Headers already prepared in the buffer are not modified."
| (setq headers (append headers message-required-headers)) ; <---- !!!!
| (save-restriction
| (message-narrow-to-headers)
| (let* ((Date (message-make-date))
| (Message-ID (message-make-message-id))
\----
If I remove the line marked with !!!!, these headers are lost, because they
are not added later, as opposed to ...news-headers and ...mail-headers.
Unfortunately, these variables are not very well documented. :-(. So, why
is this difference? Is it on purpose?
David
next reply other threads:[~2003-06-10 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-10 10:03 Hanak David [this message]
2003-10-18 0:58 ` Lars Magne Ingebrigtsen
2003-10-18 10:22 ` Romain FRANCOISE
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=m2znkqb66j.fsf@maui.hanak.hu \
--to=dhanak@inf.bme.hu \
/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).