From: Lars Ingebrigtsen <larsi@gnus.org>
To: Marius Hofert <marius.hofert@math.ethz.ch>
Cc: Emacs Gnus <info-gnus-english@gnu.org>
Subject: Re: How to avoid "Empty header for Subject; enter value:"?
Date: Mon, 24 Dec 2012 17:12:39 +0100 [thread overview]
Message-ID: <87623r4efc.fsf@gnus.org> (raw)
In-Reply-To: <mailman.11884.1351461630.855.info-gnus-english@gnu.org> (Marius Hofert's message of "Sun, 28 Oct 2012 23:00:20 +0100")
Marius Hofert <marius.hofert@math.ethz.ch> writes:
> Is there a way to tell Gnus not to ask for a subject ("Empty header
> for Subject; enter value:") if there is none specified?
Sure. Just delete `Subject' from `message-required-mail-headers'.
--
(domestic pets only, the antidote for overdose, milk.)
http://lars.ingebrigtsen.no * Lars Magne Ingebrigtsen
next parent reply other threads:[~2012-12-24 16:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.11884.1351461630.855.info-gnus-english@gnu.org>
2012-12-24 16:12 ` Lars Ingebrigtsen [this message]
2012-10-28 22:00 Marius Hofert
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=87623r4efc.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=info-gnus-english@gnu.org \
--cc=marius.hofert@math.ethz.ch \
/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).