Walker, Derek Martin).
<sect1>IRC
<p>
Visit channel <em/#mutt/ on <htmlurl
-url="http://www.openprojects.net" name="OpenProjects.Net
-(www.openprojects.net)"> to chat with other people interested in Mutt.
+url="http://www.freenode.net/" name="irc.freenode.net
+(www.freenode.net)"> to chat with other people interested in Mutt.
<sect1>USENET
<p>
<p><bf/list-reply/<label id="list-reply"> (default: L)<newline>
Reply to the current or tagged message(s) by extracting any addresses which
-match the addresses given by the <ref id="lists" name="lists or subscribe">
+match the regular expressions given by the <ref id="lists" name="lists or subscribe">
commands, but also honor any <tt/Mail-Followup-To/ header(s) if the
<ref id="honor_followup_to" name="$honor_followup_to">
configuration variable is set. Using this when replying to messages posted
sent to a different party, mutt will automatically suggest to send
the response to the original message's recipients -- responding to
yourself won't make much sense in many cases. (See <ref
-id="reply_to" name="$reply_to">.)
+id="reply_to" name="$reply_to">.)
Many users receive e-mail under a number of different addresses. To
fully use mutt's features here, the program must be able to
supported by all mail user agents. Adding it is not bullet-proof against
receiving personal CCs of list messages. Also note that the generation
of the Mail-Followup-To header is controlled by the <ref id="followup_to"
-name="$followup_to"> configuration variable.
+name="$followup_to"> configuration variable.
More precisely, Mutt maintains lists of patterns for the addresses
of known and subscribed mailing lists. Every subscribed mailing
initialization file. To tell mutt that you are subscribed to it,
add ``subscribe mutt-users'' to your initialization file instead.
If you also happen to get mail from someone whose address is
-<em/mutt-users@example.com/, you could use ``lists mutt-users@mutt.org''
-or ``subscribe mutt-users@mutt.org'' to
+<em/mutt-users@example.com/, you could use ``lists mutt-users@mutt\\.org''
+or ``subscribe mutt-users@mutt\\.org'' to
match only mail from the actual list.
The ``unlists'' command is used to remove a token from the list of
See <ref id="pattern_hook" name="Message Matching in Hooks"> for information on the exact format of <em/pattern/.
-Example: <tt/fcc-hook aol.com$ +spammers/
+Example: <tt/fcc-hook [@.]aol\\.com$ +spammers/
The above will save a copy of all messages going to the aol.com domain to
the `+spammers' mailbox by default. Also see the <ref id="fcc-save-hook"
<tscreen><verb>
send-hook . 'unmy_hdr From:'
-send-hook ~Cb@b.b my_hdr from: c@c.c
+send-hook ~C'^b@b\.b$' my_hdr from: c@c.c
</verb></tscreen>
<sect2>Message Matching in Hooks<label id="pattern_hook">
to reply directly to the author in private, since most mail clients
will automatically reply to the address given in the ``Reply-To''
field. Mutt uses the <ref id="reply_to" name="$reply_to">
-variable to help decide which address to use. If set, you will be
+variable to help decide which address to use. If set to <em/ask-yes/ or
+<em/ask-no/, you will be
prompted as to whether or not you would like to use the address given in
the ``Reply-To'' field, or reply directly to the address given in the
-``From'' field. When unset, the ``Reply-To'' field will be used when
+``From'' field. When set to <em/yes/, the ``Reply-To'' field will be used when
present.
The ``X-Label:'' header field can be used to further identify mailing
tag-prefix ; apply next command to tagged entries
tag-prefix-cond not bound apply next function ONLY to tagged messages
top-page H move to the top of the page
+what-key not bound display the keycode for a key press
</verb>
<sect2>index
<p>
{ "move", DT_QUAD, R_NONE, OPT_MOVE, M_ASKNO },
/*
** .pp
- ** Controls whether you will be asked to confirm moving read messages
+ ** Controls whether or not Mutt will move read messages
** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of
** a ``$mbox-hook'' command.
*/
{ "print", DT_QUAD, R_NONE, OPT_PRINT, M_ASKNO },
/*
** .pp
- ** Controls whether or not Mutt asks for confirmation before printing.
- ** This is useful for people (like me) who accidentally hit ``p'' often.
+ ** Controls whether or not Mutt really prints messages.
+ ** This is set to \fIask-no\fP by default, because some people
+ ** accidentally hit ``p'' often (like me).
*/
{ "print_command", DT_PATH, R_NONE, UL &PrintCmd, UL "lpr" },
/*
{ "recall", DT_QUAD, R_NONE, OPT_RECALL, M_ASKYES },
/*
** .pp
- ** Controls whether or not you are prompted to recall postponed messages
+ ** Controls whether or not Mutt recalls postponed messages
** when composing a new message. Also see ``$$postponed''.
** .pp
** Setting this variable to ``yes'' is not generally useful, and thus not
{ "reply_to", DT_QUAD, R_NONE, OPT_REPLYTO, M_ASKYES },
/*
** .pp
- ** If set, Mutt will ask you if you want to use the address listed in the
- ** Reply-To: header field when replying to a message. If you answer no,
+ ** If set, when replying to a message, Mutt will use the address listed
+ ** in the Reply-to: header as the recipient of the reply. If unset,
** it will use the address in the From: header field instead. This
** option is useful for reading a mailing list that sets the Reply-To:
** header field to the list address and you want to send a private
** .dt %m .dd the number of messages in the mailbox *
** .dt %M .dd the number of messages shown (i.e., which match the current limit) *
** .dt %n .dd number of new messages in the mailbox *
- ** .dt %o .dd number of old unread messages
+ ** .dt %o .dd number of old unread messages *
** .dt %p .dd number of postponed messages *
** .dt %P .dd percentage of the way through the index
** .dt %r .dd modified/read-only/won't-write/attach-message indicator,
** .pp
** where \fIsequence_char\fP is a character from the table above, and
** \fIoptional_string\fP is the string you would like printed if
- ** \fIstatus_char\fP is nonzero. \fIoptional_string\fP \fBmay\fP contain
- ** other sequence as well as normal text, but you may \fBnot\fP nest
+ ** \fIsequence_char\fP is nonzero. \fIoptional_string\fP \fBmay\fP contain
+ ** other sequences as well as normal text, but you may \fBnot\fP nest
** optional strings.
** .pp
** Here is an example illustrating how to optionally print the number of
{ "weed", DT_BOOL, R_NONE, OPTWEED, 1 },
/*
** .pp
- ** When set, mutt will weed headers when when displaying, forwarding,
+ ** When set, mutt will weed headers when displaying, forwarding,
** printing, or replying to messages.
*/
{ "wrap_search", DT_BOOL, R_NONE, OPTWRAPSEARCH, 1 },
/*
** .pp
** Controls whether mutt writes out the Bcc header when preparing
- ** messages to be sent. Exim users may wish to use this.
+ ** messages to be sent. Exim users may wish to unset this.
*/
/*--*/
{ NULL }
-e <command>\tspecify a command to be executed after initialization\n\
-f <file>\tspecify which mailbox to read\n\
-F <file>\tspecify an alternate muttrc file\n\
- -H <file>\tspecify a draft file to read header from\n\
- -i <file>\tspecify a file which Mutt should include in the reply\n\
+ -H <file>\tspecify a draft file to read header and body from\n\
+ -i <file>\tspecify a file which Mutt should include in the body\n\
-m <type>\tspecify a default mailbox type\n\
-n\t\tcauses Mutt not to read the system Muttrc\n\
-p\t\trecall a postponed message\n\
projects / mutt / commitdiff