The Mutt E-Mail Client
by Michael Elkins <me@cs.hmc.edu>
- version 1.5.6
+ version 1.5.7
``All mail clients suck. This one just sucks less.'' -me, circa 1995
______________________________________________________________________
3.21 Adding key sequences to the keyboard buffer
3.22 Executing functions
3.23 Message Scoring
- 3.24 Setting variables
- 3.25 Reading initialization commands from another file
- 3.26 Removing hooks
+ 3.24 Spam detection
+ 3.25 Setting variables
+ 3.26 Reading initialization commands from another file
+ 3.27 Removing hooks
4. Advanced Usage
______________________________________________________________________
- 1\b1.\b. I\bIn\bnt\btr\bro\bod\bdu\buc\bct\bti\bio\bon\bn
+ \e[1m1. Introduction\e[0m
- M\bMu\but\btt\bt is a small but very powerful text-based MIME mail client. Mutt
+ \e[1mMutt \e[22mis a small but very powerful text-based MIME mail client. Mutt
is highly configurable, and is well suited to the mail power user with
advanced features like key bindings, keyboard macros, mail threading,
regular expression searches and a powerful pattern matching language
for selecting groups of messages.
- 1\b1.\b.1\b1.\b. M\bMu\but\btt\bt H\bHo\bom\bme\be P\bPa\bag\bge\be
+ \e[1m1.1. Mutt Home Page\e[0m
http://www.mutt.org/
- 1\b1.\b.2\b2.\b. M\bMa\bai\bil\bli\bin\bng\bg L\bLi\bis\bst\bts\bs
+ \e[1m1.2. Mailing Lists\e[0m
To subscribe to one of the following mailing lists, send a message
- with the word _\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be in the body to list-name_\b-_\br_\be_\bq_\bu_\be_\bs_\bt@mutt.org.
+ with the word \e[4msubscribe\e[24m in the body to list-name\e[4m-request\e[24m@mutt.org.
· mutt-announce@mutt.org -- low traffic list for announcements
· mutt-dev@mutt.org -- development mailing list
- N\bNo\bot\bte\be:\b: all messages posted to _\bm_\bu_\bt_\bt_\b-_\ba_\bn_\bn_\bo_\bu_\bn_\bc_\be are automatically forwarded
- to _\bm_\bu_\bt_\bt_\b-_\bu_\bs_\be_\br_\bs, so you do not need to be subscribed to both lists.
+ \e[1mNote: \e[22mall messages posted to \e[4mmutt-announce\e[24m are automatically forwarded
+ to \e[4mmutt-users\e[24m, so you do not need to be subscribed to both lists.
- 1\b1.\b.3\b3.\b. S\bSo\bof\bft\btw\bwa\bar\bre\be D\bDi\bis\bst\btr\bri\bib\bbu\but\bti\bio\bon\bn S\bSi\bit\bte\bes\bs
+ \e[1m1.3. Software Distribution Sites\e[0m
· ftp://ftp.mutt.org/mutt/
For a list of mirror sites, please refer to
http://www.mutt.org/download.html.
- 1\b1.\b.4\b4.\b. I\bIR\bRC\bC
+ \e[1m1.4. IRC\e[0m
- Visit channel _\b#_\bm_\bu_\bt_\bt on OpenProjects.Net (www.openprojects.net) to chat
+ Visit channel \e[4m#mutt\e[24m on OpenProjects.Net (www.openprojects.net) to chat
with other people interested in Mutt.
- 1\b1.\b.5\b5.\b. U\bUS\bSE\bEN\bNE\bET\bT
+ \e[1m1.5. USENET\e[0m
See the newsgroup comp.mail.mutt.
- 1\b1.\b.6\b6.\b. C\bCo\bop\bpy\byr\bri\big\bgh\bht\bt
+ \e[1m1.6. Copyright\e[0m
Mutt is Copyright (C) 1996-2000 Michael R. Elkins <me@cs.hmc.edu> and
others
along with this program; if not, write to the Free Software
Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA.
- 2\b2.\b. G\bGe\bet\btt\bti\bin\bng\bg S\bSt\bta\bar\brt\bte\bed\bd
+ \e[1m2. Getting Started\e[0m
This section is intended as a brief overview of how to use Mutt.
There are many other features which are described elsewhere in the
at the command line. There are various command-line options, see
either the mutt man page or the ``reference''.
- 2\b2.\b.1\b1.\b. M\bMo\bov\bvi\bin\bng\bg A\bAr\bro\bou\bun\bnd\bd i\bin\bn M\bMe\ben\bnu\bus\bs
+ \e[1m2.1. Moving Around in Menus\e[0m
Information is presented in menus, very similar to ELM. Here is a
table showing the common keys used to navigate menus in Mutt.
\ toggle search pattern coloring
^ jump to the top of the message
- In addition, many of the functions from the _\bi_\bn_\bd_\be_\bx are available in the
- pager, such as _\bd_\be_\bl_\be_\bt_\be_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be or _\bc_\bo_\bp_\by_\b-_\bm_\be_\bs_\bs_\ba_\bg_\be (this is one advantage
+ In addition, many of the functions from the \e[4mindex\e[24m are available in the
+ pager, such as \e[4mdelete-message\e[24m or \e[4mcopy-message\e[24m (this is one advantage
over using an external pager to view messages).
Also, the internal pager supports a couple other advanced features.
See also: ``$strict_threads''.
- 2\b2.\b.3\b3.\b.4\b4.\b. M\bMi\bis\bsc\bce\bel\bll\bla\ban\bne\beo\bou\bus\bs F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs
+ \e[1m2.3.4. Miscellaneous Functions\e[0m
- c\bcr\bre\bea\bat\bte\be-\b-a\bal\bli\bia\bas\bs (default: a)
+ \e[1mcreate-alias \e[22m(default: a)
Creates a new alias based upon the current message (or prompts for a
new one). Once editing is complete, an ``alias'' command is added to
the file specified by the ``$alias_file'' variable for future use.
- N\bNo\bot\bte\be:\b: Specifying an ``$alias_file'' does not add the aliases specified
+ \e[1mNote: \e[22mSpecifying an ``$alias_file'' does not add the aliases specified
there-in, you must also ``source'' the file.
- c\bch\bhe\bec\bck\bk-\b-t\btr\bra\bad\bdi\bit\bti\bio\bon\bna\bal\bl-\b-p\bpg\bgp\bp (default: ESC P)
+ \e[1mcheck-traditional-pgp \e[22m(default: ESC P)
This function will search the current message for content signed or
encrypted with PGP the "traditional" way, that is, without proper MIME
content types of the body parts containing PGP data; this is similar
to the ``edit-type'' function's effect.
- d\bdi\bis\bsp\bpl\bla\bay\by-\b-t\bto\bog\bgg\bgl\ble\be-\b-w\bwe\bee\bed\bd (default: h)
+ \e[1mdisplay-toggle-weed \e[22m(default: h)
Toggles the weeding of message header fields specified by ``ignore''
commands.
- e\bed\bdi\bit\bt (default: e)
+ \e[1medit \e[22m(default: e)
This command (available in the ``index'' and ``pager'') allows you to
edit the raw current message as it's present in the mail folder.
to the current folder, and the original message will be marked for
deletion.
- e\bed\bdi\bit\bt-\b-t\bty\byp\bpe\be
+ \e[1medit-type\e[0m
(default: ^E on the attachment menu, and in the pager and index menus;
^T on the compose menu)
There, it's used to fine-tune the properties of attachments you are
going to send.
- e\ben\bnt\bte\ber\br-\b-c\bco\bom\bmm\bma\ban\bnd\bd (default: ``:'')
+ \e[1menter-command \e[22m(default: ``:'')
This command is used to execute any command you would normally put in
a configuration file. A common use is to check the settings of
variables, or in conjunction with ``macros'' to change settings on the
fly.
- e\bex\bxt\btr\bra\bac\bct\bt-\b-k\bke\bey\bys\bs (default: ^K)
+ \e[1mextract-keys \e[22m(default: ^K)
This command extracts PGP public keys from the current or tagged
message(s) and adds them to your PGP public key ring.
- f\bfo\bor\brg\bge\bet\bt-\b-p\bpa\bas\bss\bsp\bph\bhr\bra\bas\bse\be (default: ^F)
+ \e[1mforget-passphrase \e[22m(default: ^F)
This command wipes the passphrase(s) from memory. It is useful, if you
misspelled the passphrase.
- l\bli\bis\bst\bt-\b-r\bre\bep\bpl\bly\by (default: L)
+ \e[1mlist-reply \e[22m(default: L)
Reply to the current or tagged message(s) by extracting any addresses
which match the addresses given by the ``lists or subscribe''
replying to messages posted to mailing lists helps avoid duplicate
copies being sent to the author of the message you are replying to.
- p\bpi\bip\bpe\be-\b-m\bme\bes\bss\bsa\bag\bge\be (default: |)
+ \e[1mpipe-message \e[22m(default: |)
Asks for an external Unix command and pipes the current or tagged
message(s) to it. The variables ``$pipe_decode'', ``$pipe_split'',
``$pipe_sep'' and ``$wait_key'' control the exact behaviour of this
function.
- r\bre\bes\bse\ben\bnd\bd-\b-m\bme\bes\bss\bsa\bag\bge\be (default: ESC e)
+ \e[1mresend-message \e[22m(default: ESC e)
With resend-message, mutt takes the current message as a template for
a new message. This function is best described as "recall from
``$status_format'' will change to a 'A' to indicate that you are in
attach-message mode.
- 2\b2.\b.4\b4.\b.1\b1.\b. E\bEd\bdi\bit\bti\bin\bng\bg t\bth\bhe\be m\bme\bes\bss\bsa\bag\bge\be h\bhe\bea\bad\bde\ber\br
+ \e[1m2.4.1. Editing the message header\e[0m
When editing the header of your outgoing message, there are a couple
of special features available.
If you specify
- Fcc: _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
- Mutt will pick up _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be just as if you had used the _\be_\bd_\bi_\bt_\b-_\bf_\bc_\bc
- function in the _\bc_\bo_\bm_\bp_\bo_\bs_\be menu.
+ Fcc: \e[4mfilename\e[0m
+ Mutt will pick up \e[4mfilename\e[24m just as if you had used the \e[4medit-fcc\e[0m
+ function in the \e[4mcompose\e[24m menu.
You can also attach files to your message by specifying
- Attach: _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be [ _\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn ]
- where _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be is the file to attach and _\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn is an optional
+ Attach: \e[4mfilename\e[24m [ \e[4mdescription\e[24m ]
+ where \e[4mfilename\e[24m is the file to attach and \e[4mdescription\e[24m is an optional
string to use as the description of the attached file.
- When replying to messages, if you remove the _\bI_\bn_\b-_\bR_\be_\bp_\bl_\by_\b-_\bT_\bo_\b: field from
- the header field, Mutt will not generate a _\bR_\be_\bf_\be_\br_\be_\bn_\bc_\be_\bs_\b: field, which
+ When replying to messages, if you remove the \e[4mIn-Reply-To:\e[24m field from
+ the header field, Mutt will not generate a \e[4mReferences:\e[24m field, which
allows you to create a new message thread.
Also see ``edit_headers''.
- 2\b2.\b.4\b4.\b.2\b2.\b. U\bUs\bsi\bin\bng\bg M\bMu\but\btt\bt w\bwi\bit\bth\bh P\bPG\bGP\bP
+ \e[1m2.4.2. Using Mutt with PGP\e[0m
If you want to use PGP, you can specify
- Pgp: [ E | S | S<id> ]
+ Pgp: [ E | S | S\e[4m<id>\e[24m ]
``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key,
setting ``$pgp_sign_as'' permanently.
The capabilities field (%c) expands to a two-character sequence
representing a key's capabilities. The first character gives the
- key's encryption capabilities: A minus sign (-\b-) means that the key
- cannot be used for encryption. A dot (.\b.) means that it's marked as a
+ key's encryption capabilities: A minus sign (\e[1m-\e[22m) means that the key
+ cannot be used for encryption. A dot (\e[1m.\e[22m) means that it's marked as a
signature key in one of the user IDs, but may also be used for
- encryption. The letter e\be indicates that this key can be used for
+ encryption. The letter \e[1me \e[22mindicates that this key can be used for
encryption.
The second character indicates the key's signing capabilities. Once
- again, a ``-\b-'' implies ``not for signing'', ``.\b.'' implies that the key
- is marked as an encryption key in one of the user-ids, and ``s\bs''
+ again, a ``\e[1m-\e[22m'' implies ``not for signing'', ``\e[1m.\e[22m'' implies that the key
+ is marked as an encryption key in one of the user-ids, and ``\e[1ms\e[22m''
denotes a key which can be used for signing.
Finally, the validity field (%t) indicates how well-certified a user-
- id is. A question mark (?\b?) indicates undefined validity, a minus
- character (-\b-) marks an untrusted association, a space character means
- a partially trusted association, and a plus character (+\b+) indicates
+ id is. A question mark (\e[1m?\e[22m) indicates undefined validity, a minus
+ character (\e[1m-\e[22m) marks an untrusted association, a space character means
+ a partially trusted association, and a plus character (\e[1m+\e[22m) indicates
complete validity.
- 2\b2.\b.4\b4.\b.3\b3.\b. S\bSe\ben\bnd\bdi\bin\bng\bg a\ban\bno\bon\bny\bym\bmo\bou\bus\bs m\bme\bes\bss\bsa\bag\bge\bes\bs v\bvi\bia\ba m\bmi\bix\bxm\bma\bas\bst\bte\ber\br.\b.
+ \e[1m2.4.3. Sending anonymous messages via mixmaster.\e[0m
You may also have configured mutt to co-operate with Mixmaster, an
anonymous remailer. Mixmaster permits you to send your messages
the other capabilities, please have a look at the mixmaster
documentation.
- 2\b2.\b.5\b5.\b. F\bFo\bor\brw\bwa\bar\brd\bdi\bin\bng\bg a\ban\bnd\bd B\bBo\bou\bun\bnc\bci\bin\bng\bg M\bMa\bai\bil\bl
+ \e[1m2.5. Forwarding and Bouncing Mail\e[0m
Bouncing and forwarding let you send an existing message to recipients
that you specify. Bouncing a message uses the ``sendmail'' command to
variable. Decoding of attachments, like in the pager, can be
controlled by the ``$forward_decode'' and ``$mime_forward_decode''
variables, respectively. The desired forwarding format may depend on
- the content, therefore _\b$_\bm_\bi_\bm_\be_\b__\bf_\bo_\br_\bw_\ba_\br_\bd is a quadoption which, for
+ the content, therefore \e[4m$mime_forward\e[24m is a quadoption which, for
example, can be set to ``ask-no''.
The inclusion of headers is controlled by the current setting of the
.muttrc is the file where you will usually place your ``commands'' to
configure Mutt.
-
In addition, mutt supports version specific configuration files that
are parsed instead of the default files as explained above. For
instance, if your system has a Muttrc-0.88 file in the system
number is the same which is visible using the ``-v'' ``command line''
switch or using the show-version key (default: V) from the index menu.
- 3\b3.\b.1\b1.\b. S\bSy\byn\bnt\bta\bax\bx o\bof\bf I\bIn\bni\bit\bti\bia\bal\bli\biz\bza\bat\bti\bio\bon\bn F\bFi\bil\ble\bes\bs
+ \e[1m3.1. Syntax of Initialization Files\e[0m
An initialization file consists of a series of ``commands''. Each
line of the file may contain one or more commands. When multiple
literal string (one that is not interpreted for shell variables or
quoting with a backslash [see next paragraph]), while double quotes
indicate a string for which should be evaluated. For example,
- backtics are evaluated inside of double quotes, but n\bno\bot\bt for single
+ backtics are evaluated inside of double quotes, but \e[1mnot \e[22mfor single
quotes.
\ quotes the next character, just as in shells such as bash and zsh.
The commands understood by mutt are explained in the next paragraphs.
For a complete list, see the ``command reference''.
- 3\b3.\b.2\b2.\b. D\bDe\bef\bfi\bin\bni\bin\bng\bg/\b/U\bUs\bsi\bin\bng\bg a\bal\bli\bia\bas\bse\bes\bs
+ \e[1m3.2. Defining/Using aliases\e[0m
- Usage: alias _\bk_\be_\by _\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\ba_\bd_\bd_\br_\be_\bs_\bs, ... ]
+ Usage: alias \e[4mkey\e[24m \e[4maddress\e[24m [ , \e[4maddress\e[24m, ... ]
It's usually very cumbersome to remember or type out the address of
someone you are communicating with. Mutt allows you to create
``aliases'' which map a short string to a full address.
- N\bNo\bot\bte\be:\b: if you want to create an alias for a group (by specifying more
- than one address), you m\bmu\bus\bst\bt separate the addresses with a comma
+ \e[1mNote: \e[22mif you want to create an alias for a group (by specifying more
+ than one address), you \e[1mmust \e[22mseparate the addresses with a comma
(``,'').
To remove an alias or aliases (``*'' means all aliases):
- unalias [ * | _\bk_\be_\by _\b._\b._\b. ]
+ unalias [ * | \e[4mkey\e[24m \e[4m...\e[24m ]
alias muttdude me@cs.hmc.edu (Michael Elkins)
alias theguys manny, moe, jack
that Mutt will happily append aliases to any file, but in order for
the new aliases to take effect you need to explicitly ``source'' this
file too.
-
For example:
source /usr/local/share/Mutt.aliases
set alias_file=~/.mail_aliases
To use aliases, you merely use the alias at any place in mutt where
- mutt prompts for addresses, such as the _\bT_\bo_\b: or _\bC_\bc_\b: prompt. You can
+ mutt prompts for addresses, such as the \e[4mTo:\e[24m or \e[4mCc:\e[24m prompt. You can
also enter aliases in your editor at the appropriate headers if you
have the ``$edit_headers'' variable set.
or after a comma denoting multiple addresses.
In the alias menu, you can select as many aliases as you want with the
- _\bs_\be_\bl_\be_\bc_\bt_\b-_\be_\bn_\bt_\br_\by key (default: RET), and use the _\be_\bx_\bi_\bt key (default: q) to
+ \e[4mselect-entry\e[24m key (default: RET), and use the \e[4mexit\e[24m key (default: q) to
return to the address prompt.
- 3\b3.\b.3\b3.\b. C\bCh\bha\ban\bng\bgi\bin\bng\bg t\bth\bhe\be d\bde\bef\bfa\bau\bul\blt\bt k\bke\bey\by b\bbi\bin\bnd\bdi\bin\bng\bgs\bs
+ \e[1m3.3. Changing the default key bindings\e[0m
- Usage: bind _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
+ Usage: bind \e[4mmap\e[24m \e[4mkey\e[24m \e[4mfunction\e[0m
This command allows you to change the default key bindings (operation
invoked when pressing a key).
- _\bm_\ba_\bp specifies in which menu the binding belongs. The currently
- defined maps are:
+ \e[4mmap\e[24m specifies in which menu the binding belongs. Multiple maps may be
+ specified by separating them with commas (no additional whitespace is
+ allowed). The currently defined maps are:
- g\bge\ben\bne\ber\bri\bic\bc
+ \e[1mgeneric\e[0m
This is not a real menu, but is used as a fallback for all of
the other menus except for the pager and editor modes. If a key
is not defined in another menu, Mutt will look for a binding to
function in multiple menus instead of having multiple bind
statements to accomplish the same task.
- a\bal\bli\bia\bas\bs
+ \e[1malias\e[0m
The alias menu is the list of your personal aliases as defined
in your muttrc. It is the mapping from a short alias name to
the full email address(es) of the recipient(s).
- a\bat\btt\bta\bac\bch\bh
+ \e[1mattach\e[0m
The attachment menu is used to access the attachments on
received messages.
- b\bbr\bro\bow\bws\bse\ber\br
+ \e[1mbrowser\e[0m
The browser is used for both browsing the local directory
structure, and for listing all of your incoming mailboxes.
- e\bed\bdi\bit\bto\bor\br
+ \e[1meditor\e[0m
The editor is the line-based editor the user enters text data.
- i\bin\bnd\bde\bex\bx
+ \e[1mindex\e[0m
The index is the list of messages contained in a mailbox.
- c\bco\bom\bmp\bpo\bos\bse\be
+ \e[1mcompose\e[0m
The compose menu is the screen used when sending a new message.
- p\bpa\bag\bge\ber\br
+ \e[1mpager\e[0m
The pager is the mode used to display message/attachment data,
and help listings.
- p\bpg\bgp\bp
+ \e[1mpgp\e[0m
The pgp menu is used to select the OpenPGP keys used for
encrypting outgoing messages.
- p\bpo\bos\bst\btp\bpo\bon\bne\be
+ \e[1mpostpone\e[0m
The postpone menu is similar to the index menu, except is used
when recalling a message the user was composing, but saved until
later.
- _\bk_\be_\by is the key (or key sequence) you wish to bind. To specify a
- control character, use the sequence _\b\_\bC_\bx, where _\bx is the letter of the
+ \e[4mkey\e[24m is the key (or key sequence) you wish to bind. To specify a
+ control character, use the sequence \e[4m\Cx\e[24m, where \e[4mx\e[24m is the letter of the
control character (for example, to specify control-A use ``\Ca'').
- Note that the case of _\bx as well as _\b\_\bC is ignored, so that _\b\_\bC_\bA_\b, _\b\_\bC_\ba_\b,
- _\b\_\bc_\bA and _\b\_\bc_\ba are all equivalent. An alternative form is to specify the
+ Note that the case of \e[4mx\e[24m as well as \e[4m\C\e[24m is ignored, so that \e[4m\CA\e[24m, \e[4m\Ca\e[24m,
+ \e[4m\cA\e[24m and \e[4m\ca\e[24m are all equivalent. An alternative form is to specify the
key as a three digit octal number prefixed with a ``\'' (for example
- _\b\_\b1_\b7_\b7 is equivalent to _\b\_\bc_\b?).
-
- In addition, _\bk_\be_\by may consist of:
-
- \t tab
- <tab> tab
- \r carriage return
- \n newline
- \e escape
- <esc> escape
- <up> up arrow
- <down> down arrow
- <left> left arrow
- <right> right arrow
- <pageup> Page Up
- <pagedown> Page Down
- <backspace> Backspace
- <delete> Delete
- <insert> Insert
- <enter> Enter
- <return> Return
- <home> Home
- <end> End
- <space> Space bar
- <f1> function key 1
- <f10> function key 10
-
- _\bk_\be_\by does not need to be enclosed in quotes unless it contains a space
+ \e[4m\177\e[24m is equivalent to \e[4m\c?\e[24m).
+
+ In addition, \e[4mkey\e[24m may consist of:
+
+ \t tab
+ <tab> tab
+ \r carriage return
+ \n newline
+ \e escape
+ <esc> escape
+ <up> up arrow
+ <down> down arrow
+ <left> left arrow
+ <right> right arrow
+ <backspace> Backspace
+ <delete> Delete
+ <insert> Insert
+ <enter> Enter
+ <return> Return
+ <home> Home
+ <end> End
+ <space> Space bar
+ <f1> function key 1
+ <f10> function key 10
+
+ \e[4mkey\e[24m does not need to be enclosed in quotes unless it contains a space
(`` '').
- _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn specifies which action to take when _\bk_\be_\by is pressed. For a
+ \e[4mfunction\e[24m specifies which action to take when \e[4mkey\e[24m is pressed. For a
complete list of functions, see the ``reference''. The special
function noop unbinds the specified key sequence.
- 3\b3.\b.4\b4.\b. D\bDe\bef\bfi\bin\bni\bin\bng\bg a\bal\bli\bia\bas\bse\bes\bs f\bfo\bor\br c\bch\bha\bar\bra\bac\bct\bte\ber\br s\bse\bet\bts\bs
+ \e[1m3.4. Defining aliases for character sets\e[0m
- Usage: charset-hook _\ba_\bl_\bi_\ba_\bs _\bc_\bh_\ba_\br_\bs_\be_\bt
- Usage: iconv-hook _\bc_\bh_\ba_\br_\bs_\be_\bt _\bl_\bo_\bc_\ba_\bl_\b-_\bc_\bh_\ba_\br_\bs_\be_\bt
+ Usage: charset-hook \e[4malias\e[24m \e[4mcharset\e[0m
+ Usage: iconv-hook \e[4mcharset\e[24m \e[4mlocal-charset\e[0m
The charset-hook command defines an alias for a character set. This
is useful to properly display messages which are tagged with a
set. This is helpful when your systems character conversion library
insists on using strange, system-specific names for character sets.
- 3\b3.\b.5\b5.\b. S\bSe\bet\btt\bti\bin\bng\bg v\bva\bar\bri\bia\bab\bbl\ble\bes\bs b\bba\bas\bse\bed\bd u\bup\bpo\bon\bn m\bma\bai\bil\blb\bbo\box\bx
+ \e[1m3.5. Setting variables based upon mailbox\e[0m
- Usage: folder-hook [!]_\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ Usage: folder-hook [!]\e[4mregexp\e[24m \e[4mcommand\e[0m
It is often desirable to change settings based on which mailbox you
are reading. The folder-hook command provides a method by which you
- can execute any configuration command. _\br_\be_\bg_\be_\bx_\bp is a regular expression
- specifying in which mailboxes to execute _\bc_\bo_\bm_\bm_\ba_\bn_\bd before loading. If a
+ can execute any configuration command. \e[4mregexp\e[24m is a regular expression
+ specifying in which mailboxes to execute \e[4mcommand\e[24m before loading. If a
mailbox matches multiple folder-hook's, they are executed in the order
given in the muttrc.
- N\bNo\bot\bte\be:\b: if you use the ``!'' shortcut for ``$spoolfile'' at the
+ \e[1mNote: \e[22mif you use the ``!'' shortcut for ``$spoolfile'' at the
beginning of the pattern, you must place it inside of double or single
- quotes in order to distinguish it from the logical _\bn_\bo_\bt operator for
+ quotes in order to distinguish it from the logical \e[4mnot\e[24m operator for
the expression.
- Note that the settings are _\bn_\bo_\bt restored when you leave the mailbox.
+ Note that the settings are \e[4mnot\e[24m restored when you leave the mailbox.
For example, a command action to perform is to change the sorting
method based upon the mailbox being read:
folder-hook mutt set sort=threads
However, the sorting method is not restored to its previous value when
- reading a different mailbox. To specify a _\bd_\be_\bf_\ba_\bu_\bl_\bt command, use the
+ reading a different mailbox. To specify a \e[4mdefault\e[24m command, use the
pattern ``.'':
folder-hook . set sort=date-sent
- 3\b3.\b.6\b6.\b. K\bKe\bey\byb\bbo\boa\bar\brd\bd m\bma\bac\bcr\bro\bos\bs
+ \e[1m3.6. Keyboard macros\e[0m
- Usage: macro _\bm_\be_\bn_\bu _\bk_\be_\by _\bs_\be_\bq_\bu_\be_\bn_\bc_\be [ _\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn ]
+ Usage: macro \e[4mmenu\e[24m \e[4mkey\e[24m \e[4msequence\e[24m [ \e[4mdescription\e[24m ]
Macros are useful when you would like a single key to perform a series
- of actions. When you press _\bk_\be_\by in menu _\bm_\be_\bn_\bu, Mutt will behave as if
- you had typed _\bs_\be_\bq_\bu_\be_\bn_\bc_\be. So if you have a common sequence of commands
+ of actions. When you press \e[4mkey\e[24m in menu \e[4mmenu\e[24m, Mutt will behave as if
+ you had typed \e[4msequence\e[24m. So if you have a common sequence of commands
you type, you can create a macro to execute those commands with a
single key.
- _\bk_\be_\by and _\bs_\be_\bq_\bu_\be_\bn_\bc_\be are expanded by the same rules as the ``key
+ \e[4mmenu\e[24m is the ``map'' which the macro will be bound. Multiple maps may
+ be specified by separating multiple menu arguments by commas.
+ Whitespace may not be used in between the menu arguments and the
+ commas separating them.
+
+ \e[4mkey\e[24m and \e[4msequence\e[24m are expanded by the same rules as the ``key
bindings''. There are some additions however. The first is that
- control characters in _\bs_\be_\bq_\bu_\be_\bn_\bc_\be can also be specified as _\b^_\bx. In order
- to get a caret (`^'') you need to use _\b^_\b^. Secondly, to specify a
- certain key such as _\bu_\bp or to invoke a function directly, you can use
- the format _\b<_\bk_\be_\by _\bn_\ba_\bm_\be_\b> and _\b<_\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn _\bn_\ba_\bm_\be_\b>. For a listing of key names
+ control characters in \e[4msequence\e[24m can also be specified as \e[4m^x\e[24m. In order
+ to get a caret (`^'') you need to use \e[4m^^\e[24m. Secondly, to specify a
+ certain key such as \e[4mup\e[24m or to invoke a function directly, you can use
+ the format \e[4m<key\e[24m \e[4mname>\e[24m and \e[4m<function\e[24m \e[4mname>\e[24m. For a listing of key names
see the section on ``key bindings''. Functions are listed in the
``function reference''.
them more robust and portable, and also facilitates defining of macros
in files used by more than one user (eg. the system Muttrc).
- Optionally you can specify a descriptive text after _\bs_\be_\bq_\bu_\be_\bn_\bc_\be, which is
+ Optionally you can specify a descriptive text after \e[4msequence\e[24m, which is
shown in the help screens.
- N\bNo\bot\bte\be:\b: Macro definitions (if any) listed in the help screen(s), are
+ \e[1mNote: \e[22mMacro definitions (if any) listed in the help screen(s), are
silently truncated at the screen width, and are not wrapped.
- 3\b3.\b.7\b7.\b. U\bUs\bsi\bin\bng\bg c\bco\bol\blo\bor\br a\ban\bnd\bd m\bmo\bon\bno\bo v\bvi\bid\bde\beo\bo a\bat\btt\btr\bri\bib\bbu\but\bte\bes\bs
+ \e[1m3.7. Using color and mono video attributes\e[0m
- Usage: color _\bo_\bb_\bj_\be_\bc_\bt _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd [ _\br_\be_\bg_\be_\bx_\bp ]
- Usage: color index _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd _\bp_\ba_\bt_\bt_\be_\br_\bn
- Usage: uncolor index _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ Usage: color \e[4mobject\e[24m \e[4mforeground\e[24m \e[4mbackground\e[24m [ \e[4mregexp\e[24m ]
+ Usage: color index \e[4mforeground\e[24m \e[4mbackground\e[24m \e[4mpattern\e[0m
+ Usage: uncolor index \e[4mpattern\e[24m [ \e[4mpattern\e[24m ... ]
If your terminal supports color, you can spice up Mutt by creating
your own color scheme. To define the color of an object (type of
- information), you must specify both a foreground color a\ban\bnd\bd a
+ information), you must specify both a foreground color \e[1mand \e[22ma
background color (it is not possible to only specify one or the
other).
- _\bo_\bb_\bj_\be_\bc_\bt can be one of:
+ \e[4mobject\e[24m can be one of:
· attachment
- · body (match _\br_\be_\bg_\be_\bx_\bp in the body of messages)
+ · body (match \e[4mregexp\e[24m in the body of messages)
· bold (hiliting bold patterns in the body of messages)
· error (error messages printed by Mutt)
- · header (match _\br_\be_\bg_\be_\bx_\bp in the message header)
+ · header (match \e[4mregexp\e[24m in the message header)
· hdrdefault (default color of the message header in the pager)
- · index (match _\bp_\ba_\bt_\bt_\be_\br_\bn in the message index)
+ · index (match \e[4mpattern\e[24m in the message index)
· indicator (arrow or bar used to indicate the current item in a
menu)
· quoted (text matching ``$quote_regexp'' in the body of a message)
- · quoted1, quoted2, ..., quotedN\bN (higher levels of quoting)
+ · quoted1, quoted2, ..., quoted\e[1mN \e[22m(higher levels of quoting)
· search (hiliting of words in the pager)
· underline (hiliting underlined patterns in the body of messages)
- _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd and _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd can be one of the following:
+ \e[4mforeground\e[24m and \e[4mbackground\e[24m can be one of the following:
· white
· default
- · color_\bx
+ · color\e[4mx\e[0m
- _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd can optionally be prefixed with the keyword bright to make
+ \e[4mforeground\e[24m can optionally be prefixed with the keyword bright to make
the foreground color boldfaced (e.g., brightred).
- If your terminal supports it, the special keyword _\bd_\be_\bf_\ba_\bu_\bl_\bt can be used
- as a transparent color. The value _\bb_\br_\bi_\bg_\bh_\bt_\bd_\be_\bf_\ba_\bu_\bl_\bt is also valid. If
- Mutt is linked against the _\bS_\b-_\bL_\ba_\bn_\bg library, you also need to set the
- _\bC_\bO_\bL_\bO_\bR_\bF_\bG_\bB_\bG environment variable to the default colors of your terminal
+ If your terminal supports it, the special keyword \e[4mdefault\e[24m can be used
+ as a transparent color. The value \e[4mbrightdefault\e[24m is also valid. If
+ Mutt is linked against the \e[4mS-Lang\e[24m library, you also need to set the
+ \e[4mCOLORFGBG\e[24m environment variable to the default colors of your terminal
for this to work; for example (for Bourne-like shells):
set COLORFGBG="green;black"
export COLORFGBG
- N\bNo\bot\bte\be:\b: The _\bS_\b-_\bL_\ba_\bn_\bg library requires you to use the _\bl_\bi_\bg_\bh_\bt_\bg_\br_\ba_\by and _\bb_\br_\bo_\bw_\bn
- keywords instead of _\bw_\bh_\bi_\bt_\be and _\by_\be_\bl_\bl_\bo_\bw when setting this variable.
+ \e[1mNote: \e[22mThe \e[4mS-Lang\e[24m library requires you to use the \e[4mlightgray\e[24m and \e[4mbrown\e[0m
+ keywords instead of \e[4mwhite\e[24m and \e[4myellow\e[24m when setting this variable.
- N\bNo\bot\bte\be:\b: The uncolor command can be applied to the index object only. It
- removes entries from the list. You m\bmu\bus\bst\bt specify the same pattern
+ \e[1mNote: \e[22mThe uncolor command can be applied to the index object only. It
+ removes entries from the list. You \e[1mmust \e[22mspecify the same pattern
specified in the color command for it to be removed. The pattern
``*'' is a special token which means to clear the color index list of
all entries.
- Mutt also recognizes the keywords _\bc_\bo_\bl_\bo_\br_\b0, _\bc_\bo_\bl_\bo_\br_\b1, ..., _\bc_\bo_\bl_\bo_\brN\bN-\b-1\b1 (N\bN
+ Mutt also recognizes the keywords \e[4mcolor0\e[24m, \e[4mcolor1\e[24m, ..., \e[4mcolor\e[24m\e[1mN-1 \e[22m(\e[1mN\e[0m
being the number of colors supported by your terminal). This is
useful when you remap the colors for your display (for example by
- changing the color associated with _\bc_\bo_\bl_\bo_\br_\b2 for your xterm), since color
+ changing the color associated with \e[4mcolor2\e[24m for your xterm), since color
names may then lose their normal meaning.
If your terminal does not support color, it is still possible change
the video attributes through the use of the ``mono'' command:
- Usage: mono _\b<_\bo_\bb_\bj_\be_\bc_\bt_\b> _\b<_\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be_\b> [ _\br_\be_\bg_\be_\bx_\bp ]
- Usage: mono index _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be _\bp_\ba_\bt_\bt_\be_\br_\bn
- Usage: unmono index _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ Usage: mono \e[4m<object>\e[24m \e[4m<attribute>\e[24m [ \e[4mregexp\e[24m ]
+ Usage: mono index \e[4mattribute\e[24m \e[4mpattern\e[0m
+ Usage: unmono index \e[4mpattern\e[24m [ \e[4mpattern\e[24m ... ]
- where _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be is one of the following:
+ where \e[4mattribute\e[24m is one of the following:
· none
· standout
- 3\b3.\b.8\b8.\b. I\bIg\bgn\bno\bor\bri\bin\bng\bg (\b(w\bwe\bee\bed\bdi\bin\bng\bg)\b) u\bun\bnw\bwa\ban\bnt\bte\bed\bd m\bme\bes\bss\bsa\bag\bge\be h\bhe\bea\bad\bde\ber\brs\bs
+ \e[1m3.8. Ignoring (weeding) unwanted message headers\e[0m
- Usage: [un]ignore _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ Usage: [un]ignore \e[4mpattern\e[24m [ \e[4mpattern\e[24m ... ]
Messages often have many header fields added by automatic processing
systems, or which may not seem useful to display on the screen. This
unignore organization organisation x-mailer: x-newsreader: x-mailing-list:
unignore posted-to:
- 3\b3.\b.9\b9.\b. A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be a\bad\bdd\bdr\bre\bes\bss\bse\bes\bs
+ \e[1m3.9. Alternative addresses\e[0m
- Usage: [un]alternates _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ Usage: [un]alternates \e[4mregexp\e[24m [ \e[4mregexp\e[24m ... ]
With various functions, mutt will treat messages differently,
depending on whether you sent them or whether you received them from
To remove a regular expression from this list, use the unalternates
command.
- 3\b3.\b.1\b10\b0.\b. M\bMa\bai\bil\bli\bin\bng\bg l\bli\bis\bst\bts\bs
+ \e[1m3.10. Mailing lists\e[0m
- Usage: [un]lists _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
- Usage: [un]subscribe _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ Usage: [un]lists \e[4mregexp\e[24m [ \e[4mregexp\e[24m ... ]
+ Usage: [un]subscribe \e[4mregexp\e[24m [ \e[4mregexp\e[24m ... ]
Mutt has a few nice features for ``handling mailing lists''. In order
to take advantage of them, you must specify which addresses belong to
Specify as much of the address as you need to to remove ambiguity.
For example, if you've subscribed to the Mutt mailing list, you will
- receive mail addresssed to _\bm_\bu_\bt_\bt_\b-_\bu_\bs_\be_\br_\bs_\b@_\bm_\bu_\bt_\bt_\b._\bo_\br_\bg. So, to tell Mutt that
+ receive mail addresssed to \e[4mmutt-users@mutt.org\e[24m. So, to tell Mutt that
this is a mailing list, you could add ``lists mutt-users'' to your
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 _\bm_\bu_\bt_\bt_\b-
- _\bu_\bs_\be_\br_\bs_\b@_\be_\bx_\ba_\bm_\bp_\bl_\be_\b._\bc_\bo_\bm, you could use ``lists mutt-users@mutt.org'' or
+ also happen to get mail from someone whose address is \e[4mmutt-\e[0m
+ \e[4musers@example.com\e[24m, you could use ``lists mutt-users@mutt.org'' or
``subscribe mutt-users@mutt.org'' to match only mail from the actual
list.
To remove a mailing list from the list of subscribed mailing lists,
but keep it on the list of known mailing lists, use ``unsubscribe''.
- 3\b3.\b.1\b11\b1.\b. U\bUs\bsi\bin\bng\bg M\bMu\bul\blt\bti\bip\bpl\ble\be s\bsp\bpo\boo\bol\bl m\bma\bai\bil\blb\bbo\box\bxe\bes\bs
+ \e[1m3.11. Using Multiple spool mailboxes\e[0m
- Usage: mbox-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ Usage: mbox-hook [!]\e[4mpattern\e[24m \e[4mmailbox\e[0m
This command is used to move read messages from a specified mailbox to
a different mailbox automatically when you quit or change folders.
- _\bp_\ba_\bt_\bt_\be_\br_\bn is a regular expression specifying the mailbox to treat as a
- ``spool'' mailbox and _\bm_\ba_\bi_\bl_\bb_\bo_\bx specifies where mail should be saved
+ \e[4mpattern\e[24m is a regular expression specifying the mailbox to treat as a
+ ``spool'' mailbox and \e[4mmailbox\e[24m specifies where mail should be saved
when read.
- Unlike some of the other _\bh_\bo_\bo_\bk commands, only the _\bf_\bi_\br_\bs_\bt matching
+ Unlike some of the other \e[4mhook\e[24m commands, only the \e[4mfirst\e[24m matching
pattern is used (it is not possible to save read mail in more than a
single mailbox).
- 3\b3.\b.1\b12\b2.\b. D\bDe\bef\bfi\bin\bni\bin\bng\bg m\bma\bai\bil\blb\bbo\box\bxe\bes\bs w\bwh\bhi\bic\bch\bh r\bre\bec\bce\bei\biv\bve\be m\bma\bai\bil\bl
+ \e[1m3.12. Defining mailboxes which receive mail\e[0m
- Usage: [un]mailboxes [!]_\bf_\bi_\bl_\be_\bn_\ba_\bm_\be [ _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ... ]
+ Usage: [un]mailboxes [!]\e[4mfilename\e[24m [ \e[4mfilename\e[24m ... ]
This command specifies folders which can receive mail and which will
be checked for new messages. By default, the main menu status bar
displays how many of these folders have new messages.
- When changing folders, pressing _\bs_\bp_\ba_\bc_\be will cycle through folders with
+ When changing folders, pressing \e[4mspace\e[24m will cycle through folders with
new mail.
Pressing TAB in the directory browser will bring up a menu showing the
folders which receive mail. Use ``unmailboxes *'' to remove all
tokens.
- N\bNo\bot\bte\be:\b: new mail is detected by comparing the last modification time to
+ \e[1mNote: \e[22mnew mail is detected by comparing the last modification time to
the last access time. Utilities like biff or frm or any other program
which accesses the mailbox might cause Mutt to never detect new mail
for that mailbox if they do not properly reset the access time.
Backup tools are another common reason for updated access times.
- N\bNo\bot\bte\be:\b: the filenames in the mailboxes command are resolved when the
+ \e[1mNote: \e[22mthe filenames in the mailboxes command are resolved when the
command is executed, so if these names contain ``shortcut characters''
(such as ``='' and ``!''), any variable definition that affect these
characters (like ``$folder'' and ``$spoolfile'') should be executed
before the mailboxes command.
- 3\b3.\b.1\b13\b3.\b. U\bUs\bse\ber\br d\bde\bef\bfi\bin\bne\bed\bd h\bhe\bea\bad\bde\ber\brs\bs
+ \e[1m3.13. User defined headers\e[0m
Usage:
- my_hdr _\bs_\bt_\br_\bi_\bn_\bg
- unmy_hdr _\bf_\bi_\be_\bl_\bd [ _\bf_\bi_\be_\bl_\bd ... ]
+ my_hdr \e[4mstring\e[0m
+ unmy_hdr \e[4mfield\e[24m [ \e[4mfield\e[24m ... ]
The ``my_hdr'' command allows you to create your own header fields
which will be added to every message you send.
in your .muttrc.
- N\bNo\bot\bte\be:\b: space characters are _\bn_\bo_\bt allowed between the keyword and the
+ \e[1mNote: \e[22mspace characters are \e[4mnot\e[24m allowed between the keyword and the
colon (``:''). The standard for electronic mail (RFC822) says that
space is illegal there, so Mutt enforces the rule.
If you would like to add a header field to a single message, you
- should either set the ``edit_headers'' variable, or use the _\be_\bd_\bi_\bt_\b-
- _\bh_\be_\ba_\bd_\be_\br_\bs function (default: ``E'') in the send-menu so that you can
+ should either set the ``edit_headers'' variable, or use the \e[4medit-\e[0m
+ \e[4mheaders\e[24m function (default: ``E'') in the send-menu so that you can
edit the header of your message along with the body.
To remove user defined header fields, use the ``unmy_hdr'' command.
unmy_hdr to cc
- 3\b3.\b.1\b14\b4.\b. D\bDe\bef\bfi\bin\bni\bin\bng\bg t\bth\bhe\be o\bor\brd\bde\ber\br o\bof\bf h\bhe\bea\bad\bde\ber\brs\bs w\bwh\bhe\ben\bn v\bvi\bie\bew\bwi\bin\bng\bg m\bme\bes\bss\bsa\bag\bge\bes\bs
+ \e[1m3.14. Defining the order of headers when viewing messages\e[0m
- Usage: hdr_order _\bh_\be_\ba_\bd_\be_\br_\b1 _\bh_\be_\ba_\bd_\be_\br_\b2 _\bh_\be_\ba_\bd_\be_\br_\b3
+ Usage: hdr_order \e[4mheader1\e[24m \e[4mheader2\e[24m \e[4mheader3\e[0m
With this command, you can specify an order in which mutt will attempt
to present headers to you when viewing messages.
hdr_order From Date: From: To: Cc: Subject:
- 3\b3.\b.1\b15\b5.\b. S\bSp\bpe\bec\bci\bif\bfy\by d\bde\bef\bfa\bau\bul\blt\bt s\bsa\bav\bve\be f\bfi\bil\ble\ben\bna\bam\bme\be
+ \e[1m3.15. Specify default save filename\e[0m
- Usage: save-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ Usage: save-hook [!]\e[4mpattern\e[24m \e[4mfilename\e[0m
This command is used to override the default filename used when saving
- messages. _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be will be used as the default filename if the
- message is _\bF_\br_\bo_\bm_\b: an address matching _\br_\be_\bg_\be_\bx_\bp or if you are the author
- and the message is addressed _\bt_\bo_\b: something matching _\br_\be_\bg_\be_\bx_\bp.
+ messages. \e[4mfilename\e[24m will be used as the default filename if the
+ message is \e[4mFrom:\e[24m an address matching \e[4mregexp\e[24m or if you are the author
+ and the message is addressed \e[4mto:\e[24m something matching \e[4mregexp\e[24m.
See ``Message Matching in Hooks'' for information on the exact format
- of _\bp_\ba_\bt_\bt_\be_\br_\bn.
+ of \e[4mpattern\e[24m.
Examples:
Also see the ``fcc-save-hook'' command.
- 3\b3.\b.1\b16\b6.\b. S\bSp\bpe\bec\bci\bif\bfy\by d\bde\bef\bfa\bau\bul\blt\bt F\bFc\bcc\bc:\b: m\bma\bai\bil\blb\bbo\box\bx w\bwh\bhe\ben\bn c\bco\bom\bmp\bpo\bos\bsi\bin\bng\bg
+ \e[1m3.16. Specify default Fcc: mailbox when composing\e[0m
- Usage: fcc-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ Usage: fcc-hook [!]\e[4mpattern\e[24m \e[4mmailbox\e[0m
This command is used to save outgoing mail in a mailbox other than
``$record''. Mutt searches the initial list of message recipients for
- the first matching _\br_\be_\bg_\be_\bx_\bp and uses _\bm_\ba_\bi_\bl_\bb_\bo_\bx as the default Fcc:
+ the first matching \e[4mregexp\e[24m and uses \e[4mmailbox\e[24m as the default Fcc:
mailbox. If no match is found the message will be saved to
``$record'' mailbox.
See ``Message Matching in Hooks'' for information on the exact format
- of _\bp_\ba_\bt_\bt_\be_\br_\bn.
+ of \e[4mpattern\e[24m.
Example: fcc-hook aol.com$ +spammers
to the `+spammers' mailbox by default. Also see the ``fcc-save-hook''
command.
- 3\b3.\b.1\b17\b7.\b. S\bSp\bpe\bec\bci\bif\bfy\by d\bde\bef\bfa\bau\bul\blt\bt s\bsa\bav\bve\be f\bfi\bil\ble\ben\bna\bam\bme\be a\ban\bnd\bd d\bde\bef\bfa\bau\bul\blt\bt F\bFc\bcc\bc:\b: m\bma\bai\bil\blb\bbo\box\bx a\bat\bt o\bon\bnc\bce\be
+ \e[1m3.17. Specify default save filename and default Fcc: mailbox at once\e[0m
- Usage: fcc-save-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ Usage: fcc-save-hook [!]\e[4mpattern\e[24m \e[4mmailbox\e[0m
This command is a shortcut, equivalent to doing both a ``fcc-hook''
and a ``save-hook'' with its arguments.
- 3\b3.\b.1\b18\b8.\b. C\bCh\bha\ban\bng\bge\be s\bse\bet\btt\bti\bin\bng\bgs\bs b\bba\bas\bse\bed\bd u\bup\bpo\bon\bn m\bme\bes\bss\bsa\bag\bge\be r\bre\bec\bci\bip\bpi\bie\ben\bnt\bts\bs
+ \e[1m3.18. Change settings based upon message recipients\e[0m
- Usage: reply-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
- Usage: send-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ Usage: reply-hook [!]\e[4mpattern\e[24m \e[4mcommand\e[0m
+ Usage: send-hook [!]\e[4mpattern\e[24m \e[4mcommand\e[0m
+ Usage: send2-hook [!]\e[4mpattern\e[24m \e[4mcommand\e[0m
These commands can be used to execute arbitrary configuration commands
- based upon recipients of the message. _\bp_\ba_\bt_\bt_\be_\br_\bn is a regular expression
- matching the desired address. _\bc_\bo_\bm_\bm_\ba_\bn_\bd is executed when _\br_\be_\bg_\be_\bx_\bp matches
+ based upon recipients of the message. \e[4mpattern\e[24m is a regular expression
+ matching the desired address. \e[4mcommand\e[24m is executed when \e[4mregexp\e[24m matches
recipients of the message.
- reply-hook is matched against the message you are _\br_\be_\bp_\bl_\by_\bi_\bn_\bg t\bto\bo, instead
- of the message you are _\bs_\be_\bn_\bd_\bi_\bn_\bg. send-hook is matched against all
- messages, both _\bn_\be_\bw and _\br_\be_\bp_\bl_\bi_\be_\bs. N\bNo\bot\bte\be:\b: reply-hooks are matched b\bbe\bef\bfo\bor\bre\be
- the send-hook, r\bre\beg\bga\bar\brd\bdl\ble\bes\bss\bs of the order specified in the users's
+ reply-hook is matched against the message you are \e[4mreplying\e[24m \e[1mto\e[22m, instead
+ of the message you are \e[4msending\e[24m. send-hook is matched against all
+ messages, both \e[4mnew\e[24m and \e[4mreplies\e[24m. \e[1mNote: \e[22mreply-hooks are matched \e[1mbefore\e[0m
+ the send-hook, \e[1mregardless \e[22mof the order specified in the users's
configuration file.
- For each type of send-hook or reply-hook, When multiple matches occur,
+ send2-hook is matched every time a message is changed, either by
+ editing it, or by using the compose menu to change its recipients or
+ subject. send2-hook is executed after send-hook, and can, e.g., be
+ used to set parameters such as the ``$sendmail'' variable depending on
+ the message's sender address.
+
+ For each type of send-hook or reply-hook, when multiple matches occur,
commands are executed in the order they are specified in the muttrc
(for that type of hook).
See ``Message Matching in Hooks'' for information on the exact format
- of _\bp_\ba_\bt_\bt_\be_\br_\bn.
+ of \e[4mpattern\e[24m.
Example: send-hook mutt "set mime_forward signature=''"
change the language of the attributions and signatures based upon the
recipients.
- N\bNo\bot\bte\be:\b: the send-hook's are only executed ONCE after getting the initial
+ \e[1mNote: \e[22mthe send-hook's are only executed ONCE after getting the initial
list of recipients. Adding a recipient after replying or editing the
message will NOT cause any send-hook to be executed. Also note that
my_hdr commands which modify recipient headers, or the message's
subject, don't have any effect on the current message when executed
from a send-hook.
- 3\b3.\b.1\b19\b9.\b. C\bCh\bha\ban\bng\bge\be s\bse\bet\btt\bti\bin\bng\bgs\bs b\bbe\bef\bfo\bor\bre\be f\bfo\bor\brm\bma\bat\btt\bti\bin\bng\bg a\ba m\bme\bes\bss\bsa\bag\bge\be
+ \e[1m3.19. Change settings before formatting a message\e[0m
- Usage: message-hook [!]_\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ Usage: message-hook [!]\e[4mpattern\e[24m \e[4mcommand\e[0m
This command can be used to execute arbitrary configuration commands
before viewing or formatting a message based upon information about
- the message. _\bc_\bo_\bm_\bm_\ba_\bn_\bd is executed if the _\bp_\ba_\bt_\bt_\be_\br_\bn matches the message
+ the message. \e[4mcommand\e[24m is executed if the \e[4mpattern\e[24m matches the message
to be displayed. When multiple matches occur, commands are executed in
the order they are specified in the muttrc.
See ``Message Matching in Hooks'' for information on the exact format
- of _\bp_\ba_\bt_\bt_\be_\br_\bn.
+ of \e[4mpattern\e[24m.
Example:
message-hook ~A 'set pager=builtin'
message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""'
- 3\b3.\b.2\b20\b0.\b. C\bCh\bho\boo\bos\bsi\bin\bng\bg t\bth\bhe\be c\bcr\bry\byp\bpt\bto\bog\bgr\bra\bap\bph\bhi\bic\bc k\bke\bey\by o\bof\bf t\bth\bhe\be r\bre\bec\bci\bip\bpi\bie\ben\bnt\bt
+ \e[1m3.20. Choosing the cryptographic key of the recipient\e[0m
- Usage: crypt-hook _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\bi_\bd
+ Usage: crypt-hook \e[4mpattern\e[24m \e[4mkeyid\e[0m
When encrypting messages with PGP or OpenSSL, you may want to
associate a certain key with a given e-mail address automatically,
can either put a numerical key ID here, an e-mail address, or even
just a real name.
- 3\b3.\b.2\b21\b1.\b. A\bAd\bdd\bdi\bin\bng\bg k\bke\bey\by s\bse\beq\bqu\bue\ben\bnc\bce\bes\bs t\bto\bo t\bth\bhe\be k\bke\bey\byb\bbo\boa\bar\brd\bd b\bbu\buf\bff\bfe\ber\br
+ \e[1m3.21. Adding key sequences to the keyboard buffer\e[0m
- Usage: push _\bs_\bt_\br_\bi_\bn_\bg
+ Usage: push \e[4mstring\e[0m
This command adds the named string to the keyboard buffer. The string
may contain control characters, key names and function names like the
automatically run a sequence of commands at startup, or when entering
certain folders.
- 3\b3.\b.2\b22\b2.\b. E\bEx\bxe\bec\bcu\but\bti\bin\bng\bg f\bfu\bun\bnc\bct\bti\bio\bon\bns\bs
+ \e[1m3.22. Executing functions\e[0m
- Usage: exec _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn [ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn ... ]
+ Usage: exec \e[4mfunction\e[24m [ \e[4mfunction\e[24m ... ]
This command can be used to execute any function. Functions are listed
in the ``function reference''. ``exec function'' is equivalent to
``push <function>''.
+ \e[1m3.23. Message Scoring\e[0m
- 3\b3.\b.2\b23\b3.\b. M\bMe\bes\bss\bsa\bag\bge\be S\bSc\bco\bor\bri\bin\bng\bg
-
- Usage: score _\bp_\ba_\bt_\bt_\be_\br_\bn _\bv_\ba_\bl_\bu_\be
- Usage: unscore _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ Usage: score \e[4mpattern\e[24m \e[4mvalue\e[0m
+ Usage: unscore \e[4mpattern\e[24m [ \e[4mpattern\e[24m ... ]
- The score commands adds _\bv_\ba_\bl_\bu_\be to a message's score if _\bp_\ba_\bt_\bt_\be_\br_\bn matches
- it. _\bp_\ba_\bt_\bt_\be_\br_\bn is a string in the format described in the ``patterns''
+ The score commands adds \e[4mvalue\e[24m to a message's score if \e[4mpattern\e[24m matches
+ it. \e[4mpattern\e[24m is a string in the format described in the ``patterns''
section (note: For efficiency reasons, patterns which scan information
not available in the index, such as ~b, ~B or ~h, may not be used).
- _\bv_\ba_\bl_\bu_\be is a positive or negative integer. A message's final score is
+ \e[4mvalue\e[24m is a positive or negative integer. A message's final score is
the sum total of all matching score entries. However, you may
- optionally prefix _\bv_\ba_\bl_\bu_\be with an equal sign (=) to cause evaluation to
+ optionally prefix \e[4mvalue\e[24m with an equal sign (=) to cause evaluation to
stop at a particular entry if there is a match. Negative final scores
are rounded up to 0.
- The unscore command removes score entries from the list. You m\bmu\bus\bst\bt
+ The unscore command removes score entries from the list. You \e[1mmust\e[0m
specify the same pattern specified in the score command for it to be
removed. The pattern ``*'' is a special token which means to clear
the list of all score entries.
- 3\b3.\b.2\b24\b4.\b. S\bSe\bet\btt\bti\bin\bng\bg v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
-
- Usage: set [no|inv]_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be[=_\bv_\ba_\bl_\bu_\be] [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- Usage: toggle _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- Usage: unset _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
- Usage: reset _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ \e[1m3.24. Spam detection\e[0m
+
+ Usage: spam \e[4mpattern\e[24m \e[4mformat\e[0m
+ Usage: nospam \e[4mpattern\e[0m
+
+ Mutt has generalized support for external spam-scoring filters. By
+ defining your spam patterns with the spam and nospam commands, you can
+ \e[4mlimit\e[24m, \e[4msearch\e[24m, and \e[4msort\e[24m your mail based on its spam attributes, as
+ determined by the external filter. You also can display the spam
+ attributes in your index display using the %H selector in the
+ ``$index_format'' variable. (Tip: try %?H?[%H] ? to display spam tags
+ only when they are defined for a given message.)
+
+ Your first step is to define your external filter's spam patterns
+ using the spam command. \e[4mpattern\e[24m should be a regular expression that
+ matches a header in a mail message. If any message in the mailbox
+ matches this regular expression, it will receive a ``spam tag'' or
+ ``spam attribute'' (unless it also matches a nospam pattern -- see
+ below.) The appearance of this attribute is entirely up to you, and is
+ governed by the \e[4mformat\e[24m parameter. \e[4mformat\e[24m can be any static text, but
+ it also can include back-references from the \e[4mpattern\e[24m expression. (A
+ regular expression ``back-reference'' refers to a sub-expression
+ contained within parentheses.) %1 is replaced with the first back-
+ reference in the regex, %2 with the second, etc.
+
+ If you're using multiple spam filters, a message can have more than
+ one spam-related header. You can define spam patterns for each filter
+ you use. If a message matches two or more of these patterns, and the
+ $spam_separator variable is set to a string, then the message's spam
+ tag will consist of all the \e[4mformat\e[24m strings joined together, with the
+ value of $spam_separator separating them.
+
+ For example, suppose I use DCC, SpamAssassin, and PureMessage. I might
+ define these spam settings:
+
+ spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1"
+ spam "X-Spam-Status: Yes" "90+/SA"
+ spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM"
+ set spam_separator=", "
+
+ If I then received a message that DCC registered with ``many'' hits
+ under the ``Fuz2'' checksum, and that PureMessage registered with a
+ 97% probability of being spam, that message's spam tag would read
+ 90+/DCC-Fuz2, 97/PM. (The four characters before ``=many'' in a DCC
+ report indicate the checksum used -- in this case, ``Fuz2''.)
+
+ If the $spam_separator variable is unset, then each spam pattern match
+ supercedes the previous one. Instead of getting joined \e[4mformat\e[24m strings,
+ you'll get only the last one to match.
+
+ The spam tag is what will be displayed in the index when you use %H in
+ the $index_format variable. It's also the string that the ~H pattern-
+ matching expression matches against for \e[4msearch\e[24m and \e[4mlimit\e[24m functions.
+ And it's what sorting by spam attribute will use as a sort key.
+
+ That's a pretty complicated example, and most people's actual
+ environments will have only one spam filter. The simpler your
+ configuration, the more effective mutt can be, especially when it
+ comes to sorting.
+
+ Generally, when you sort by spam tag, mutt will sort \e[4mlexically\e[24m -- that
+ is, by ordering strings alphnumerically. However, if a spam tag begins
+ with a number, mutt will sort numerically first, and lexically only
+ when two numbers are equal in value. (This is like UNIX's sort -n.) A
+ message with no spam attributes at all -- that is, one that didn't
+ match \e[4many\e[24m of your spam patterns -- is sorted at lowest priority.
+ Numbers are sorted next, beginning with 0 and ranging upward. Finally,
+ non-numeric strings are sorted, with ``a'' taking lower priority than
+ ``z''. Clearly, in general, sorting by spam tags is most effective
+ when you can coerce your filter to give you a raw number. But in case
+ you can't, mutt can still do something useful.
+
+ The nospam command can be used to write exceptions to spam patterns.
+ If a header pattern matches something in a spam command, but you
+ nonetheless do not want it to receive a spam tag, you can list a more
+ precise pattern under a nospam command.
+
+ If the \e[4mpattern\e[24m given to nospam is exactly the same as the \e[4mpattern\e[24m on
+ an existing spam list entry, the effect will be to remove the entry
+ from the spam list, instead of adding an exception. Likewise, if the
+ \e[4mpattern\e[24m for a spam command matches an entry on the nospam list, that
+ nospam entry will be removed. If the \e[4mpattern\e[24m for nospam is ``*'', \e[4mall\e[0m
+ \e[4mentries\e[24m \e[4mon\e[24m \e[4mboth\e[24m \e[4mlists\e[24m will be removed. This might be the default
+ action if you use spam and nospam in conjunction with a folder-hook.
+
+ You can have as many spam or nospam commands as you like. You can
+ even do your own primitive spam detection within mutt -- for example,
+ if you consider all mail from MAILER-DAEMON to be spam, you can use a
+ spam command like this:
+
+ spam "^From: .*MAILER-DAEMON" "999"
+
+ \e[1m3.25. Setting variables\e[0m
+
+ Usage: set [no|inv]\e[4mvariable\e[24m[=\e[4mvalue\e[24m] [ \e[4mvariable\e[24m ... ]
+ Usage: toggle \e[4mvariable\e[24m [\e[4mvariable\e[24m ... ]
+ Usage: unset \e[4mvariable\e[24m [\e[4mvariable\e[24m ... ]
+ Usage: reset \e[4mvariable\e[24m [\e[4mvariable\e[24m ... ]
This command is used to set (and unset) ``configuration variables''.
There are four basic types of variables: boolean, number, string and
- quadoption. _\bb_\bo_\bo_\bl_\be_\ba_\bn variables can be _\bs_\be_\bt (true) or _\bu_\bn_\bs_\be_\bt (false).
- _\bn_\bu_\bm_\bb_\be_\br variables can be assigned a positive integer value.
+ quadoption. \e[4mboolean\e[24m variables can be \e[4mset\e[24m (true) or \e[4munset\e[24m (false).
+ \e[4mnumber\e[24m variables can be assigned a positive integer value.
- _\bs_\bt_\br_\bi_\bn_\bg variables consist of any number of printable characters.
- _\bs_\bt_\br_\bi_\bn_\bg_\bs must be enclosed in quotes if they contain spaces or tabs.
- You may also use the ``C'' escape sequences \\b\n\bn and \\b\t\bt for newline and
+ \e[4mstring\e[24m variables consist of any number of printable characters.
+ \e[4mstrings\e[24m must be enclosed in quotes if they contain spaces or tabs.
+ You may also use the ``C'' escape sequences \e[1m\n \e[22mand \e[1m\t \e[22mfor newline and
tab, respectively.
- _\bq_\bu_\ba_\bd_\bo_\bp_\bt_\bi_\bo_\bn variables are used to control whether or not to be prompted
- for certain actions, or to specify a default action. A value of _\by_\be_\bs
+ \e[4mquadoption\e[24m variables are used to control whether or not to be prompted
+ for certain actions, or to specify a default action. A value of \e[4myes\e[0m
will cause the action to be carried out automatically as if you had
- answered yes to the question. Similarly, a value of _\bn_\bo will cause the
+ answered yes to the question. Similarly, a value of \e[4mno\e[24m will cause the
the action to be carried out as if you had answered ``no.'' A value
- of _\ba_\bs_\bk_\b-_\by_\be_\bs will cause a prompt with a default answer of ``yes'' and
- _\ba_\bs_\bk_\b-_\bn_\bo will provide a default answer of ``no.''
+ of \e[4mask-yes\e[24m will cause a prompt with a default answer of ``yes'' and
+ \e[4mask-no\e[24m will provide a default answer of ``no.''
Prefixing a variable with ``no'' will unset it. Example: set
noaskbcc.
- For _\bb_\bo_\bo_\bl_\be_\ba_\bn variables, you may optionally prefix the variable name
+ For \e[4mboolean\e[24m variables, you may optionally prefix the variable name
with inv to toggle the value (on or off). This is useful when writing
macros. Example: set invsmart_wrap.
The unset command automatically prepends the no prefix to all
specified variables.
- Using the enter-command function in the _\bi_\bn_\bd_\be_\bx menu, you can query the
+ Using the enter-command function in the \e[4mindex\e[24m menu, you can query the
value of a variable by prefixing the name of the variable with a
question mark:
With the reset command there exists the special variable ``all'',
which allows you to reset all variables to their system defaults.
- 3\b3.\b.2\b25\b5.\b. R\bRe\bea\bad\bdi\bin\bng\bg i\bin\bni\bit\bti\bia\bal\bli\biz\bza\bat\bti\bio\bon\bn c\bco\bom\bmm\bma\ban\bnd\bds\bs f\bfr\bro\bom\bm a\ban\bno\bot\bth\bhe\ber\br f\bfi\bil\ble\be
+ \e[1m3.26. Reading initialization commands from another file\e[0m
- Usage: source _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ Usage: source \e[4mfilename\e[0m
This command allows the inclusion of initialization commands from
other files. For example, I place all of my aliases in
If the filename begins with a tilde (``~''), it will be expanded to
the path of your home directory.
- If the filename ends with a vertical bar (|), then _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be is
+ If the filename ends with a vertical bar (|), then \e[4mfilename\e[24m is
considered to be an executable program from which to read input (eg.
- source ~bin/myscript|/).
+ source ~/bin/myscript|).
- 3\b3.\b.2\b26\b6.\b. R\bRe\bem\bmo\bov\bvi\bin\bng\bg h\bho\boo\bok\bks\bs
+ \e[1m3.27. Removing hooks\e[0m
- Usage: unhook [ * | _\bh_\bo_\bo_\bk_\b-_\bt_\by_\bp_\be ]
+ Usage: unhook [ * | \e[4mhook-type\e[24m ]
This command permits you to flush hooks you have previously defined.
You can either remove all hooks by giving the ``*'' character as an
argument, or you can remove all hooks of a specific type by saying
something like unhook send-hook.
- 4\b4.\b. A\bAd\bdv\bva\ban\bnc\bce\bed\bd U\bUs\bsa\bag\bge\be
+ \e[1m4. Advanced Usage\e[0m
- 4\b4.\b.1\b1.\b. R\bRe\beg\bgu\bul\bla\bar\br E\bEx\bxp\bpr\bre\bes\bss\bsi\bio\bon\bns\bs
+ \e[1m4.1. Regular Expressions\e[0m
All string patterns in Mutt including those in more complex
``patterns'' must be specified using regular expressions (regexp) in
A list of characters enclosed by ``['' and ``]'' matches any single
character in that list; if the first character of the list is a caret
- ``^'' then it matches any character n\bno\bot\bt in the list. For example, the
- regular expression [\b[0\b01\b12\b23\b34\b45\b56\b67\b78\b89\b9]\b] matches any single digit. A range of
+ ``^'' then it matches any character \e[1mnot \e[22min the list. For example, the
+ regular expression \e[1m[0123456789] \e[22mmatches any single digit. A range of
ASCII characters may be specified by giving the first and last
characters, separated by a hyphen ``-''. Most metacharacters lose
their special meaning inside lists. To include a literal ``]'' place
consist of ``[:'', a keyword denoting the class, and ``:]''. The
following classes are defined by the POSIX standard:
- [\b[:\b:a\bal\bln\bnu\bum\bm:\b:]\b]
+ \e[1m[:alnum:]\e[0m
Alphanumeric characters.
- [\b[:\b:a\bal\blp\bph\bha\ba:\b:]\b]
+ \e[1m[:alpha:]\e[0m
Alphabetic characters.
- [\b[:\b:b\bbl\bla\ban\bnk\bk:\b:]\b]
+ \e[1m[:blank:]\e[0m
Space or tab characters.
- [\b[:\b:c\bcn\bnt\btr\brl\bl:\b:]\b]
+ \e[1m[:cntrl:]\e[0m
Control characters.
- [\b[:\b:d\bdi\big\bgi\bit\bt:\b:]\b]
+ \e[1m[:digit:]\e[0m
Numeric characters.
- [\b[:\b:g\bgr\bra\bap\bph\bh:\b:]\b]
+
+ \e[1m[:graph:]\e[0m
Characters that are both printable and visible. (A space is
printable, but not visible, while an ``a'' is both.)
- [\b[:\b:l\blo\bow\bwe\ber\br:\b:]\b]
+ \e[1m[:lower:]\e[0m
Lower-case alphabetic characters.
- [\b[:\b:p\bpr\bri\bin\bnt\bt:\b:]\b]
+ \e[1m[:print:]\e[0m
Printable characters (characters that are not control
characters.)
- [\b[:\b:p\bpu\bun\bnc\bct\bt:\b:]\b]
+ \e[1m[:punct:]\e[0m
Punctuation characters (characters that are not letter, digits,
control characters, or space characters).
- [\b[:\b:s\bsp\bpa\bac\bce\be:\b:]\b]
+ \e[1m[:space:]\e[0m
Space characters (such as space, tab and formfeed, to name a
few).
- [\b[:\b:u\bup\bpp\bpe\ber\br:\b:]\b]
+ \e[1m[:upper:]\e[0m
Upper-case alphabetic characters.
- [\b[:\b:x\bxd\bdi\big\bgi\bit\bt:\b:]\b]
+ \e[1m[:xdigit:]\e[0m
Characters that are hexadecimal digits.
A character class is only valid in a regular expression inside the
brackets of a character list. Note that the brackets in these class
names are part of the symbolic names, and must be included in addition
- to the brackets delimiting the bracket list. For example, [\b[[\b[:\b:d\bdi\big\bgi\bit\bt:\b:]\b]]\b]
- is equivalent to [\b[0\b0-\b-9\b9]\b].
+ to the brackets delimiting the bracket list. For example, \e[1m[[:digit:]]\e[0m
+ is equivalent to \e[1m[0-9]\e[22m.
Two additional special sequences can appear in character lists. These
apply to non-ASCII character sets, which can have single symbols
character, as well as several characters that are equivalent for
collating or sorting purposes:
- C\bCo\bol\bll\bla\bat\bti\bin\bng\bg S\bSy\bym\bmb\bbo\bol\bls\bs
+ \e[1mCollating Symbols\e[0m
A collating symbol is a multi-character collating element
enclosed in ``[.'' and ``.]''. For example, if ``ch'' is a
- collating element, then [\b[[\b[.\b.c\bch\bh.\b.]\b]]\b] is a regexp that matches this
- collating element, while [\b[c\bch\bh]\b] is a regexp that matches either
+ collating element, then \e[1m[[.ch.]] \e[22mis a regexp that matches this
+ collating element, while \e[1m[ch] \e[22mis a regexp that matches either
``c'' or ``h''.
- E\bEq\bqu\bui\biv\bva\bal\ble\ben\bnc\bce\be C\bCl\bla\bas\bss\bse\bes\bs
+ \e[1mEquivalence Classes\e[0m
An equivalence class is a locale-specific name for a list of
characters that are equivalent. The name is enclosed in ``[=''
and ``=]''. For example, the name ``e'' might be used to
- represent all of ``è'' ``é'' and ``e''. In this case, [\b[[\b[=\b=e\be=\b=]\b]]\b]
+ represent all of ``è'' ``é'' and ``e''. In this case, \e[1m[[=e=]]\e[0m
is a regexp that matches any of ``è'', ``é'' and ``e''.
-
A regular expression matching a single character may be followed by
one of several repetition operators:
- ?\b? The preceding item is optional and matched at most once.
+ \e[1m? \e[22mThe preceding item is optional and matched at most once.
- *\b* The preceding item will be matched zero or more times.
+ \e[1m* \e[22mThe preceding item will be matched zero or more times.
- +\b+ The preceding item will be matched one or more times.
+ \e[1m+ \e[22mThe preceding item will be matched one or more times.
- {\b{n\bn}\b}
- The preceding item is matched exactly _\bn times.
+ \e[1m{n}\e[0m
+ The preceding item is matched exactly \e[4mn\e[24m times.
- {\b{n\bn,\b,}\b}
- The preceding item is matched _\bn or more times.
+ \e[1m{n,}\e[0m
+ The preceding item is matched \e[4mn\e[24m or more times.
- {\b{,\b,m\bm}\b}
- The preceding item is matched at most _\bm times.
+ \e[1m{,m}\e[0m
+ The preceding item is matched at most \e[4mm\e[24m times.
- {\b{n\bn,\b,m\bm}\b}
- The preceding item is matched at least _\bn times, but no more than
- _\bm times.
+ \e[1m{n,m}\e[0m
+ The preceding item is matched at least \e[4mn\e[24m times, but no more than
+ \e[4mm\e[24m times.
Two regular expressions may be concatenated; the resulting regular
expression matches any string formed by concatenating two substrings
precedence over alternation. A whole subexpression may be enclosed in
parentheses to override these precedence rules.
- N\bNo\bot\bte\be:\b: If you compile Mutt with the GNU _\br_\bx package, the following
+ \e[1mNote: \e[22mIf you compile Mutt with the GNU \e[4mrx\e[24m package, the following
operators may also be used in regular expressions:
- \\b\\\b\y\by
+ \e[1m\\y\e[0m
Matches the empty string at either the beginning or the end of a
word.
- \\b\\\b\B\bB
+ \e[1m\\B\e[0m
Matches the empty string within a word.
- \\b\\\b\<\b<
+ \e[1m\\<\e[0m
Matches the empty string at the beginning of a word.
- \\b\\\b\>\b>
+ \e[1m\\>\e[0m
Matches the empty string at the end of a word.
- \\b\\\b\w\bw
+ \e[1m\\w\e[0m
Matches any word-constituent character (letter, digit, or
underscore).
- \\b\\\b\W\bW
+ \e[1m\\W\e[0m
Matches any character that is not word-constituent.
- \\b\\\b\`\b`
+ \e[1m\\`\e[0m
Matches the empty string at the beginning of a buffer (string).
- \\b\\\b\'\b'
+ \e[1m\\'\e[0m
Matches the empty string at the end of a buffer.
Please note however that these operators are not defined by POSIX, so
they may or may not be available in stock libraries on various
systems.
- 4\b4.\b.2\b2.\b. P\bPa\bat\btt\bte\ber\brn\bns\bs
+ \e[1m4.2. Patterns\e[0m
Many of Mutt's commands allow you to specify a pattern to match
(limit, tag-pattern, delete-pattern, etc.). There are several ways to
select messages:
- ~A all messages
- ~b EXPR messages which contain EXPR in the message body
- ~B EXPR messages which contain EXPR in the whole message
- ~c USER messages carbon-copied to USER
- ~C EXPR message is either to: or cc: EXPR
- ~D deleted messages
- ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range
- ~E expired messages
- ~e EXPR message which contains EXPR in the ``Sender'' field
- ~F flagged messages
- ~f USER messages originating from USER
- ~g cryptographically signed messages
- ~G cryptographically encrypted messages
- ~h EXPR messages which contain EXPR in the message header
- ~k message contains PGP key material
- ~i ID message which match ID in the ``Message-ID'' field
- ~L EXPR message is either originated or received by EXPR
- ~l message is addressed to a known mailing list
- ~m [MIN]-[MAX] message in the range MIN to MAX *)
- ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
- ~N new messages
- ~O old messages
- ~p message is addressed to you (consults alternates)
- ~P message is from you (consults alternates)
- ~Q messages which have been replied to
- ~R read messages
- ~r [MIN]-[MAX] messages with ``date-received'' in a Date range
- ~S superseded messages
- ~s SUBJECT messages having SUBJECT in the ``Subject'' field.
- ~T tagged messages
- ~t USER messages addressed to USER
- ~U unread messages
- ~v message is part of a collapsed thread.
- ~V cryptographically verified messages
- ~x EXPR messages which contain EXPR in the `References' field
- ~y EXPR messages which contain EXPR in the `X-Label' field
- ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
- ~= duplicated messages (see $duplicate_threads)
+ ~A all messages
+ ~b EXPR messages which contain EXPR in the message body
+ ~B EXPR messages which contain EXPR in the whole message
+ ~c USER messages carbon-copied to USER
+ ~C EXPR message is either to: or cc: EXPR
+ ~D deleted messages
+ ~d [MIN]-[MAX] messages with ``date-sent'' in a Date range
+ ~E expired messages
+ ~e EXPR message which contains EXPR in the ``Sender'' field
+ ~F flagged messages
+ ~f USER messages originating from USER
+ ~g cryptographically signed messages
+ ~G cryptographically encrypted messages
+ ~H EXPR messages with a spam attribute matching EXPR
+ ~h EXPR messages which contain EXPR in the message header
+ ~k message contains PGP key material
+ ~i ID message which match ID in the ``Message-ID'' field
+ ~L EXPR message is either originated or received by EXPR
+ ~l message is addressed to a known mailing list
+ ~m [MIN]-[MAX] message in the range MIN to MAX *)
+ ~n [MIN]-[MAX] messages with a score in the range MIN to MAX *)
+ ~N new messages
+ ~O old messages
+ ~p message is addressed to you (consults alternates)
+ ~P message is from you (consults alternates)
+ ~Q messages which have been replied to
+ ~R read messages
+ ~r [MIN]-[MAX] messages with ``date-received'' in a Date range
+ ~S superseded messages
+ ~s SUBJECT messages having SUBJECT in the ``Subject'' field.
+ ~T tagged messages
+ ~t USER messages addressed to USER
+ ~U unread messages
+ ~v message is part of a collapsed thread.
+ ~V cryptographically verified messages
+ ~x EXPR messages which contain EXPR in the `References' field
+ ~y EXPR messages which contain EXPR in the `X-Label' field
+ ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *)
+ ~= duplicated messages (see $duplicate_threads)
+ ~$ unreferenced messages (requires threaded view)
Where EXPR, USER, ID, and SUBJECT are ``regular expressions''.
Special attention has to be made when using regular expressions inside
*) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too.
- 4\b4.\b.2\b2.\b.1\b1.\b. P\bPa\bat\btt\bte\ber\brn\bn M\bMo\bod\bdi\bif\bfi\bie\ber\br
+ \e[1m4.2.1. Pattern Modifier\e[0m
Note that patterns matching 'lists' of addresses (notably c,C,p,P and
t) match if there is at least one match in the whole list. If you want
^~C \.de$
- 4\b4.\b.2\b2.\b.2\b2.\b. C\bCo\bom\bmp\bpl\ble\bex\bx P\bPa\bat\btt\bte\ber\brn\bns\bs
+ \e[1m4.2.2. Complex Patterns\e[0m
Logical AND is performed by specifying more than one criterion. For
example:
~t mutt ~f elkins
would select messages which contain the word ``mutt'' in the list of
- recipients a\ban\bnd\bd that have the word ``elkins'' in the ``From'' header
+ recipients \e[1mand \e[22mthat have the word ``elkins'' in the ``From'' header
field.
Mutt also recognizes the following operators to create more complex
'~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")'
Note that if a regular expression contains parenthesis, or a veritical
- bar ("|"), you m\bmu\bus\bst\bt enclose the expression in double or single quotes
+ bar ("|"), you \e[1mmust \e[22menclose the expression in double or single quotes
since those characters are also used to separate different parts of
Mutt's pattern language. For example,
~f "me@(mutt\.org|cs\.hmc\.edu)"
- Without the quotes, the parenthesis would truncate the regular
- expression to simply _\bm_\be_\b@, which is probably not what you want.
+ Without the quotes, the parenthesis wouldn't end. This would be
+ seperated to two OR'd patterns: \e[4m~f\e[24m \e[4mme@(mutt\.org\e[24m and \e[4mcs\.hmc\.edu)\e[24m.
+ They are never what you want.
- 4\b4.\b.2\b2.\b.3\b3.\b. S\bSe\bea\bar\brc\bch\bhi\bin\bng\bg b\bby\by D\bDa\bat\bte\be
+ \e[1m4.2.3. Searching by Date\e[0m
- Mutt supports two types of dates, _\ba_\bb_\bs_\bo_\bl_\bu_\bt_\be and _\br_\be_\bl_\ba_\bt_\bi_\bv_\be.
+ Mutt supports two types of dates, \e[4mabsolute\e[24m and \e[4mrelative\e[24m.
- A\bAb\bbs\bso\bol\blu\but\bte\be. Dates m\bmu\bus\bst\bt be in DD/MM/YY format (month and year are
+ \e[1mAbsolute\e[22m. Dates \e[1mmust \e[22mbe in DD/MM/YY format (month and year are
optional, defaulting to the current month and year). An example of a
valid range of dates is:
Limit to messages matching: ~d 20/1/95-31/10
If you omit the minimum (first) date, and just specify ``-DD/MM/YY'',
- all messages _\bb_\be_\bf_\bo_\br_\be the given date will be selected. If you omit the
- maximum (second) date, and specify ``DD/MM/YY-'', all messages _\ba_\bf_\bt_\be_\br
+ all messages \e[4mbefore\e[24m the given date will be selected. If you omit the
+ maximum (second) date, and specify ``DD/MM/YY-'', all messages \e[4mafter\e[0m
the given date will be selected. If you specify a single date with no
dash (``-''), only messages sent on the given date will be selected.
- E\bEr\brr\bro\bor\br M\bMa\bar\brg\bgi\bin\bns\bs. You can add error margins to absolute dates. An error
+ \e[1mError Margins\e[22m. You can add error margins to absolute dates. An error
margin is a sign (+ or -), followed by a digit, followed by one of the
following units:
Limit to messages matching: ~d 15/1/2001*2w
- R\bRe\bel\bla\bat\bti\biv\bve\be. This type of date is relative to the current date, and may
+ \e[1mRelative\e[22m. This type of date is relative to the current date, and may
be specified as:
- · >_\bo_\bf_\bf_\bs_\be_\bt (messages older than _\bo_\bf_\bf_\bs_\be_\bt units)
+ · >\e[4moffset\e[24m (messages older than \e[4moffset\e[24m units)
- · <_\bo_\bf_\bf_\bs_\be_\bt (messages newer than _\bo_\bf_\bf_\bs_\be_\bt units)
+ · <\e[4moffset\e[24m (messages newer than \e[4moffset\e[24m units)
- · =_\bo_\bf_\bf_\bs_\be_\bt (messages exactly _\bo_\bf_\bf_\bs_\be_\bt units old)
+ · =\e[4moffset\e[24m (messages exactly \e[4moffset\e[24m units old)
- _\bo_\bf_\bf_\bs_\be_\bt is specified as a positive number with one of the following
+ \e[4moffset\e[24m is specified as a positive number with one of the following
units:
y years
Example: to select messages less than 1 month old, you would use
- Limit to messages matching: ~d <1m
+ Limit to messages matching: ~d <1m
- N\bNo\bot\bte\be:\b: all dates used when searching are relative to the l\blo\boc\bca\bal\bl time
+ \e[1mNote: \e[22mall dates used when searching are relative to the \e[1mlocal \e[22mtime
zone, so unless you change the setting of your ``$index_format'' to
- include a %[...] format, these are n\bno\bot\bt the dates shown in the main
+ include a %[...] format, these are \e[1mnot \e[22mthe dates shown in the main
index.
- 4\b4.\b.3\b3.\b. U\bUs\bsi\bin\bng\bg T\bTa\bag\bgs\bs
+ \e[1m4.3. Using Tags\e[0m
Sometimes it is desirable to perform an operation on a group of
messages all at once rather than one at a time. An example might be
Once you have tagged the desired messages, you can use the ``tag-
prefix'' operator, which is the ``;'' (semicolon) key by default.
- When the ``tag-prefix'' operator is used, the n\bne\bex\bxt\bt operation will be
+ When the ``tag-prefix'' operator is used, the \e[1mnext \e[22moperation will be
applied to all tagged messages if that operation can be used in that
manner. If the ``$auto_tag'' variable is set, the next operation
applies to the tagged messages automatically, without requiring the
``tag-prefix''.
- 4\b4.\b.4\b4.\b. U\bUs\bsi\bin\bng\bg H\bHo\boo\bok\bks\bs
+ In ``macros'' or ``push'' commands, you can use the ``tag-prefix-
+ cond'' operator. If there are no tagged messages, mutt will "eat" the
+ rest of the macro to abort it's execution. Mutt will stop "eating"
+ the macro when it encounters the ``end-cond'' operator; after this
+ operator the rest of the macro will be executed as normal.
+
+ \e[1m4.4. Using Hooks\e[0m
- A _\bh_\bo_\bo_\bk is a concept borrowed from the EMACS editor which allows you to
+ A \e[4mhook\e[24m is a concept borrowed from the EMACS editor which allows you to
execute arbitrary commands before performing some operation. For
example, you may wish to tailor your configuration based upon which
mailbox you are reading, or to whom you are sending mail. In the Mutt
- world, a _\bh_\bo_\bo_\bk consists of a ``regular expression'' or ``pattern''
+ world, a \e[4mhook\e[24m consists of a ``regular expression'' or ``pattern''
along with a configuration option/command. See
· ``folder-hook''
· ``fcc-save-hook''
- for specific details on each type of _\bh_\bo_\bo_\bk available.
+ for specific details on each type of \e[4mhook\e[24m available.
- N\bNo\bot\bte\be:\b: if a hook changes configuration settings, these changes remain
+ \e[1mNote: \e[22mif a hook changes configuration settings, these changes remain
effective until the end of the current mutt session. As this is
generally not desired, a default hook needs to be added before all
other hooks to restore configuration defaults. Here is an example with
send-hook . 'unmy_hdr From:'
send-hook ~Cb@b.b my_hdr from: c@c.c
- 4\b4.\b.4\b4.\b.1\b1.\b. M\bMe\bes\bss\bsa\bag\bge\be M\bMa\bat\btc\bch\bhi\bin\bng\bg i\bin\bn H\bHo\boo\bok\bks\bs
+ \e[1m4.4.1. Message Matching in Hooks\e[0m
Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-
hook) are evaluated in a slightly different manner. For the other
Mutt allows the use of the ``search pattern'' language for matching
messages in hook commands. This works in exactly the same way as it
- would when _\bl_\bi_\bm_\bi_\bt_\bi_\bn_\bg or _\bs_\be_\ba_\br_\bc_\bh_\bi_\bn_\bg the mailbox, except that you are
+ would when \e[4mlimiting\e[24m or \e[4msearching\e[24m the mailbox, except that you are
restricted to those operators which match information mutt extracts
from the header of the message (i.e. from, to, cc, date, subject,
etc.).
send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User <user@host>'
which would execute the given command when sending mail to
- _\bm_\be_\b@_\bc_\bs_\b._\bh_\bm_\bc_\b._\be_\bd_\bu.
+ \e[4mme@cs.hmc.edu\e[24m.
However, it is not required that you write the pattern to match using
- the full searching language. You can still specify a simple _\br_\be_\bg_\bu_\bl_\ba_\br
- _\be_\bx_\bp_\br_\be_\bs_\bs_\bi_\bo_\bn like the other hooks, in which case Mutt will translate
+ the full searching language. You can still specify a simple \e[4mregular\e[0m
+ \e[4mexpression\e[24m like the other hooks, in which case Mutt will translate
your pattern into the full language, using the translation specified
by the ``$default_hook'' variable. The pattern is translated at the
time the hook is declared, so the value of ``$default_hook'' that is
in effect at that time will be used.
- 4\b4.\b.5\b5.\b. E\bEx\bxt\bte\ber\brn\bna\bal\bl A\bAd\bdd\bdr\bre\bes\bss\bs Q\bQu\bue\ber\bri\bie\bes\bs
+ \e[1m4.5. External Address Queries\e[0m
Mutt supports connecting to external directory databases such as LDAP,
ph/qi, bbdb, or NIS through a wrapper script which connects to mutt
An example multiple response output:
- Searching database ... 20 entries ... 3 matching:
- me@cs.hmc.edu Michael Elkins mutt dude
- blong@fiction.net Brandon Long mutt and more
- roessler@guug.de Thomas Roessler mutt pgp
+ Searching database ... 20 entries ... 3 matching:
+ me@cs.hmc.edu Michael Elkins mutt dude
+ blong@fiction.net Brandon Long mutt and more
+ roessler@guug.de Thomas Roessler mutt pgp
There are two mechanisms for accessing the query function of mutt.
One is to do a query from the index menu using the query function
(default: Q). This will prompt for a query, then bring up the query
menu which will list the matching responses. From the query menu, you
can select addresses to create aliases, or to mail. You can tag
- multiple messages to mail, start a new query, or have a new query
+ multiple addresses to mail, start a new query, or have a new query
appended to the current responses.
The other mechanism for accessing the query function is for address
will activate the query menu. At the query menu, you can select one
or more addresses to be added to the prompt.
- 4\b4.\b.6\b6.\b. M\bMa\bai\bil\blb\bbo\box\bx F\bFo\bor\brm\bma\bat\bts\bs
+ \e[1m4.6. Mailbox Formats\e[0m
Mutt supports reading and writing of four different mailbox formats:
mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so
creating new mailboxes, Mutt uses the default specified with the
``$mbox_type'' variable.
- m\bmb\bbo\box\bx. This is the most widely used mailbox format for UNIX. All
+ \e[1mmbox\e[22m. This is the most widely used mailbox format for UNIX. All
messages are stored in a single file. Each message has a line of the
form:
to denote the start of a new message (this is often referred to as the
``From_'' line).
- M\bMM\bMD\bDF\bF. This is a variant of the _\bm_\bb_\bo_\bx format. Each message is
+ \e[1mMMDF\e[22m. This is a variant of the \e[4mmbox\e[24m format. Each message is
surrounded by lines containing ``^A^A^A^A'' (four control-A's).
- M\bMH\bH. A radical departure from _\bm_\bb_\bo_\bx and _\bM_\bM_\bD_\bF, a mailbox consists of a
+ \e[1mMH\e[22m. A radical departure from \e[4mmbox\e[24m and \e[4mMMDF\e[24m, a mailbox consists of a
directory and each message is stored in a separate file. The filename
indicates the message number (however, this is may not correspond to
the message number Mutt displays). Deleted messages are renamed with a
- comma (,) prepended to the filename. N\bNo\bot\bte\be:\b: Mutt detects this type of
+ comma (,) prepended to the filename. \e[1mNote: \e[22mMutt detects this type of
mailbox by looking for either .mh_sequences or .xmhcache (needed to
distinguish normal directories from MH mailboxes).
- M\bMa\bai\bil\bld\bdi\bir\br. The newest of the mailbox formats, used by the Qmail MTA (a
- replacement for sendmail). Similar to _\bM_\bH, except that it adds three
- subdirectories of the mailbox: _\bt_\bm_\bp, _\bn_\be_\bw and _\bc_\bu_\br. Filenames for the
+ \e[1mMaildir\e[22m. The newest of the mailbox formats, used by the Qmail MTA (a
+ replacement for sendmail). Similar to \e[4mMH\e[24m, except that it adds three
+ subdirectories of the mailbox: \e[4mtmp\e[24m, \e[4mnew\e[24m and \e[4mcur\e[24m. Filenames for the
messages are chosen in such a way they are unique, even when two
programs are writing the mailbox over NFS, which means that no file
locking is needed.
- 4\b4.\b.7\b7.\b. M\bMa\bai\bil\blb\bbo\box\bx S\bSh\bho\bor\brt\btc\bcu\but\bts\bs
+
+ \e[1m4.7. Mailbox Shortcuts\e[0m
There are a number of built in shortcuts which refer to specific
mailboxes. These shortcuts can be used anywhere you are prompted for
· = or + -- refers to your ``$folder'' directory
- · @_\ba_\bl_\bi_\ba_\bs -- refers to the ``default save folder'' as determined by
+ · @\e[4malias\e[24m -- refers to the ``default save folder'' as determined by
the address of the alias
- 4\b4.\b.8\b8.\b. H\bHa\ban\bnd\bdl\bli\bin\bng\bg M\bMa\bai\bil\bli\bin\bng\bg L\bLi\bis\bst\bts\bs
+ \e[1m4.8. Handling Mailing Lists\e[0m
Mutt has a few configuration options that make dealing with large
amounts of mail easier. The first thing you must do is to let Mutt
Now that Mutt knows what your mailing lists are, it can do several
things, the first of which is the ability to show the name of a list
through which you received a message (i.e., of a subscribed list) in
- the _\bi_\bn_\bd_\be_\bx menu display. This is useful to distinguish between
+ the \e[4mindex\e[24m menu display. This is useful to distinguish between
personal and list mail in the same mailbox. In the ``$index_format''
variable, the escape ``%L'' will return the string ``To <list>'' when
``list'' appears in the ``To'' field, and ``Cc <list>'' when it
to get quite large. Most people do not bother to remove the author of
the message they are reply to from the list, resulting in two or more
copies being sent to that person. The ``list-reply'' function, which
- by default is bound to ``L'' in the _\bi_\bn_\bd_\be_\bx menu and _\bp_\ba_\bg_\be_\br, helps reduce
+ by default is bound to ``L'' in the \e[4mindex\e[24m menu and \e[4mpager\e[24m, helps reduce
the clutter by only replying to the known mailing list addresses
instead of all recipients (except as specified by Mail-Followup-To,
see below).
individually). The ``$index_format'' variable's ``%y'' and ``%Y''
escapes can be used to expand ``X-Label:'' fields in the index, and
Mutt's pattern-matcher can match regular expressions to ``X-Label:''
- fields with the `` y'' selector. ``X-Label:'' is not a standard
+ fields with the ``y'' selector. ``X-Label:'' is not a standard
message header field, but it can easily be inserted by procmail and
other mail filtering agents.
dealing with large volume mailing lists easier because you can easily
delete uninteresting threads and quickly find topics of value.
- 4\b4.\b.9\b9.\b. D\bDe\bel\bli\biv\bve\ber\bry\by S\bSt\bta\bat\btu\bus\bs N\bNo\bot\bti\bif\bfi\bic\bca\bat\bti\bio\bon\bn (\b(D\bDS\bSN\bN)\b) S\bSu\bup\bpp\bpo\bor\brt\bt
+ \e[1m4.9. Delivery Status Notification (DSN) Support\e[0m
RFC1894 defines a set of MIME content types for relaying information
about the status of electronic mail messages. These can be thought of
message should be returned with the receipt (headers or full message).
Refer to the man page on sendmail for more details on DSN.
- 4\b4.\b.1\b10\b0.\b. P\bPO\bOP\bP3\b3 S\bSu\bup\bpp\bpo\bor\brt\bt (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ \e[1m4.10. POP3 Support (OPTIONAL)\e[0m
- If Mutt was compiled with POP3 support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be
- script with the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bp_\bo_\bp flag), it has the ability to work with
+ If Mutt was compiled with POP3 support (by running the \e[4mconfigure\e[0m
+ script with the \e[4m--enable-pop\e[24m flag), it has the ability to work with
mailboxes located on a remote POP3 server and fetch mail for local
browsing.
You can select an alternative port by specifying it with the server,
ie: pop://popserver:port/.
+
You can also specify different username for each folder, ie:
pop://username@popserver[:port]/.
can be controlled by the ``$pop_checkinterval'' variable, which
defaults to every 60 seconds.
- If Mutt was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script
- with the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl flag), connections to POP3 servers can be
+ If Mutt was compiled with SSL support (by running the \e[4mconfigure\e[24m script
+ with the \e[4m--with-ssl\e[24m flag), connections to POP3 servers can be
encrypted. This naturally requires that the server supports SSL
encrypted connections. To access a folder with POP3/SSL, you should
use pops: prefix, ie: pops://[username@]popserver[:port]/.
- Another way to access your POP3 mail is the _\bf_\be_\bt_\bc_\bh_\b-_\bm_\ba_\bi_\bl function
+ Another way to access your POP3 mail is the \e[4mfetch-mail\e[24m function
(default: G). It allows to connect to ``pop_host'', fetch all your
new mail and place it in the local ``spoolfile''. After this point,
Mutt runs exactly as if the mail had always been local.
- N\bNo\bot\bte\be:\b: If you only need to fetch all messages to local mailbox you
+ \e[1mNote: \e[22mIf you only need to fetch all messages to local mailbox you
should consider using a specialized program, such as fetchmail
- 4\b4.\b.1\b11\b1.\b. I\bIM\bMA\bAP\bP S\bSu\bup\bpp\bpo\bor\brt\bt (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ \e[1m4.11. IMAP Support (OPTIONAL)\e[0m
- If Mutt was compiled with IMAP support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be
- script with the _\b-_\b-_\be_\bn_\ba_\bb_\bl_\be_\b-_\bi_\bm_\ba_\bp flag), it has the ability to work with
+ If Mutt was compiled with IMAP support (by running the \e[4mconfigure\e[0m
+ script with the \e[4m--enable-imap\e[24m flag), it has the ability to work with
folders located on a remote IMAP server.
You can access the remote inbox by selecting the folder
You can also specify different username for each folder, ie:
imap://username@imapserver[:port]/INBOX.
- If Mutt was compiled with SSL support (by running the _\bc_\bo_\bn_\bf_\bi_\bg_\bu_\br_\be script
- with the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\bs_\bl flag), connections to IMAP servers can be
+ If Mutt was compiled with SSL support (by running the \e[4mconfigure\e[24m script
+ with the \e[4m--with-ssl\e[24m flag), connections to IMAP servers can be
encrypted. This naturally requires that the server supports SSL
encrypted connections. To access a folder with IMAP/SSL, you should
use imaps://[username@]imapserver[:port]/path/to/folder as your folder
When browsing folders on an IMAP server, you can toggle whether to
look at only the folders you are subscribed to, or all folders with
- the _\bt_\bo_\bg_\bg_\bl_\be_\b-_\bs_\bu_\bb_\bs_\bc_\br_\bi_\bb_\be_\bd command. See also the ``$imap_list_subscribed''
+ the \e[4mtoggle-subscribed\e[24m command. See also the ``$imap_list_subscribed''
variable.
Polling for new mail on an IMAP server can cause noticeable delays.
So, you'll want to carefully tune the ``$mail_check'' and ``$timeout''
variables. Personally I use
- set mail_check=90
- set timeout=15
+ set mail_check=90
+ set timeout=15
with relatively good results over my slow modem line.
to v12.250, the server has been reported to disconnect a client if
another client selects the same folder.
- 4\b4.\b.1\b11\b1.\b.1\b1.\b. T\bTh\bhe\be F\bFo\bol\bld\bde\ber\br B\bBr\bro\bow\bws\bse\ber\br
+ \e[1m4.11.1. The Folder Browser\e[0m
As of version 1.2, mutt supports browsing mailboxes on an IMAP server.
This is mostly the same as the local file browser, with the following
d by default. You may also subscribe and unsubscribe to mailboxes
(normally these are bound to s and u, respectively).
- 4\b4.\b.1\b11\b1.\b.2\b2.\b. A\bAu\but\bth\bhe\ben\bnt\bti\bic\bca\bat\bti\bio\bon\bn
+ \e[1m4.11.2. Authentication\e[0m
Mutt supports four authentication methods with IMAP servers: SASL,
GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add
entire session will be encrypted and invisible to those teeming
network snoops. It is the best option if you have it. To use it, you
must have the Cyrus SASL library installed on your system and compile
- mutt with the _\b-_\b-_\bw_\bi_\bt_\bh_\b-_\bs_\ba_\bs_\bl flag.
+ mutt with the \e[4m--with-sasl\e[24m flag.
Mutt will try whichever methods are compiled in and available on the
server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5,
authentication on the IMAP server, for all authenticators. This is
overridden by an explicit username in the mailbox path (ie by using
a mailbox name of the form {user@host}).
+
· ``$imap_pass'' - a password which you may preset, used by all
authentication methods where a password is needed.
If specified, this overrides mutt's default (attempt everything, in
the order listed above).
- 4\b4.\b.1\b12\b2.\b. M\bMa\ban\bna\bag\bgi\bin\bng\bg m\bmu\bul\blt\bti\bip\bpl\ble\be I\bIM\bMA\bAP\bP/\b/P\bPO\bOP\bP a\bac\bcc\bco\bou\bun\bnt\bts\bs (\b(O\bOP\bPT\bTI\bIO\bON\bNA\bAL\bL)\b)
+ \e[1m4.12. Managing multiple IMAP/POP accounts (OPTIONAL)\e[0m
If you happen to have accounts on multiple IMAP and/or POP servers,
you may find managing all the authentication settings inconvenient and
account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo'
account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"'
- 4\b4.\b.1\b13\b3.\b. S\bSt\bta\bar\brt\bt a\ba W\bWW\bWW\bW B\bBr\bro\bow\bws\bse\ber\br o\bon\bn U\bUR\bRL\bLs\bs (\b(E\bEX\bXT\bTE\bER\bRN\bNA\bAL\bL)\b)
+ \e[1m4.13. Start a WWW Browser on URLs (EXTERNAL)\e[0m
- If a message contains URLs (_\bu_\bn_\bi_\bf_\bi_\be_\bd _\br_\be_\bs_\bs_\bo_\bu_\br_\bc_\be _\bl_\bo_\bc_\ba_\bt_\bo_\br = address in the
- WWW space like _\bh_\bt_\bt_\bp_\b:_\b/_\b/_\bw_\bw_\bw_\b._\bm_\bu_\bt_\bt_\b._\bo_\br_\bg_\b/), it is efficient to get a menu
+ If a message contains URLs (\e[4munified\e[24m \e[4mresource\e[24m \e[4mlocator\e[24m = address in the
+ WWW space like \e[4mhttp://www.mutt.org/\e[24m), it is efficient to get a menu
with all the URLs and start a WWW browser on one of them. This
functionality is provided by the external urlview program which can be
retrieved at ftp://ftp.mutt.org/mutt/contrib/ and the configuration
macro index \cb |urlview\n
macro pager \cb |urlview\n
- 5\b5.\b. M\bMu\but\btt\bt'\b's\bs M\bMI\bIM\bME\bE S\bSu\bup\bpp\bpo\bor\brt\bt
+ \e[1m5. Mutt's MIME Support\e[0m
Quite a bit of effort has been made to make Mutt the premier text-mode
MIME MUA. Every effort has been made to provide the functionality
IANA MIME types. The other is the mailcap file, which specifies the
external commands to use for handling specific MIME types.
- 5\b5.\b.1\b1.\b. U\bUs\bsi\bin\bng\bg M\bMI\bIM\bME\bE i\bin\bn M\bMu\but\btt\bt
+ \e[1m5.1. Using MIME in Mutt\e[0m
There are three areas/menus in Mutt which deal with MIME, they are the
pager (while viewing a message), the attachment menu and the compose
menu.
- 5\b5.\b.1\b1.\b.1\b1.\b. V\bVi\bie\bew\bwi\bin\bng\bg M\bMI\bIM\bME\bE m\bme\bes\bss\bsa\bag\bge\bes\bs i\bin\bn t\bth\bhe\be p\bpa\bag\bge\ber\br
+ \e[1m5.1.1. Viewing MIME messages in the pager\e[0m
When you select a message from the index and view it in the pager,
Mutt decodes the message to a text representation. Mutt internally
[-- Type: text/plain, Encoding: 7bit, Size: 10000 --]
Where the Description is the description or filename given for the
- attachment, and the Encoding is one of 7bit/8bit/quoted-print
+ attachment, and the Encoding is one of 7bit/8bit/quoted-print-
able/base64/binary.
If Mutt cannot deal with a MIME type, it will display a message like:
[-- image/gif is unsupported (use 'v' to view this part) --]
- 5\b5.\b.1\b1.\b.2\b2.\b. T\bTh\bhe\be A\bAt\btt\bta\bac\bch\bhm\bme\ben\bnt\bt M\bMe\ben\bnu\bu
+ \e[1m5.1.2. The Attachment Menu\e[0m
The default binding for view-attachments is `v', which displays the
attachment menu for a message. The attachment menu displays a list of
See the help on the attachment menu for more information.
- 5\b5.\b.1\b1.\b.3\b3.\b. T\bTh\bhe\be C\bCo\bom\bmp\bpo\bos\bse\be M\bMe\ben\bnu\bu
+ \e[1m5.1.3. The Compose Menu\e[0m
The compose menu is the menu you see before you send a message. It
allows you to edit the recipient list, the subject, and other aspects
description of the attachment, and can be changed with the edit-
description command (default: d).
- 5\b5.\b.2\b2.\b. M\bMI\bIM\bME\bE T\bTy\byp\bpe\be c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn w\bwi\bit\bth\bh m\bmi\bim\bme\be.\b.t\bty\byp\bpe\bes\bs
+ \e[1m5.2. MIME Type configuration with mime.types\e[0m
When you add an attachment to your mail message, Mutt searches your
personal mime.types file at ${HOME}/.mime.types, and then the system
mime types should only be used if the recipient of the message is
likely to be expecting such attachments.
- 5\b5.\b.3\b3.\b. M\bMI\bIM\bME\bE V\bVi\bie\bew\bwe\ber\br c\bco\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn w\bwi\bit\bth\bh m\bma\bai\bil\blc\bca\bap\bp
+ \e[1m5.3. MIME Viewer configuration with mailcap\e[0m
Mutt supports RFC 1524 MIME Configuration, in particular the Unix
specific format specified in Appendix A of RFC 1524. This file format
usually as /usr/local/etc/mailcap, which contains some baseline
entries.
- 5\b5.\b.3\b3.\b.1\b1.\b. T\bTh\bhe\be B\bBa\bas\bsi\bic\bcs\bs o\bof\bf t\bth\bhe\be m\bma\bai\bil\blc\bca\bap\bp f\bfi\bil\ble\be
+ \e[1m5.3.1. The Basics of the mailcap file\e[0m
A mailcap file consists of a series of lines which are comments,
blank, or definitions.
text/html; lynx %s
In this case, lynx does not support viewing a file from stdin, so you
- must use the %s syntax. N\bNo\bot\bte\be:\b: _\bS_\bo_\bm_\be _\bo_\bl_\bd_\be_\br _\bv_\be_\br_\bs_\bi_\bo_\bn_\bs _\bo_\bf _\bl_\by_\bn_\bx _\bc_\bo_\bn_\bt_\ba_\bi_\bn _\ba
- _\bb_\bu_\bg _\bw_\bh_\be_\br_\be _\bt_\bh_\be_\by _\bw_\bi_\bl_\bl _\bc_\bh_\be_\bc_\bk _\bt_\bh_\be _\bm_\ba_\bi_\bl_\bc_\ba_\bp _\bf_\bi_\bl_\be _\bf_\bo_\br _\ba _\bv_\bi_\be_\bw_\be_\br _\bf_\bo_\br _\bt_\be_\bx_\bt_\b/_\bh_\bt_\bm_\bl_\b.
- _\bT_\bh_\be_\by _\bw_\bi_\bl_\bl _\bf_\bi_\bn_\bd _\bt_\bh_\be _\bl_\bi_\bn_\be _\bw_\bh_\bi_\bc_\bh _\bc_\ba_\bl_\bl_\bs _\bl_\by_\bn_\bx_\b, _\ba_\bn_\bd _\br_\bu_\bn _\bi_\bt_\b. _\bT_\bh_\bi_\bs _\bc_\ba_\bu_\bs_\be_\bs
- _\bl_\by_\bn_\bx _\bt_\bo _\bc_\bo_\bn_\bt_\bi_\bn_\bu_\bo_\bu_\bs_\bl_\by _\bs_\bp_\ba_\bw_\bn _\bi_\bt_\bs_\be_\bl_\bf _\bt_\bo _\bv_\bi_\be_\bw _\bt_\bh_\be _\bo_\bb_\bj_\be_\bc_\bt_\b.
+ must use the %s syntax. \e[1mNote: \e[4m\e[22mSome\e[24m \e[4molder\e[24m \e[4mversions\e[24m \e[4mof\e[24m \e[4mlynx\e[24m \e[4mcontain\e[24m \e[4ma\e[0m
+ \e[4mbug\e[24m \e[4mwhere\e[24m \e[4mthey\e[24m \e[4mwill\e[24m \e[4mcheck\e[24m \e[4mthe\e[24m \e[4mmailcap\e[24m \e[4mfile\e[24m \e[4mfor\e[24m \e[4ma\e[24m \e[4mviewer\e[24m \e[4mfor\e[24m \e[4mtext/html.\e[0m
+ \e[4mThey\e[24m \e[4mwill\e[24m \e[4mfind\e[24m \e[4mthe\e[24m \e[4mline\e[24m \e[4mwhich\e[24m \e[4mcalls\e[24m \e[4mlynx,\e[24m \e[4mand\e[24m \e[4mrun\e[24m \e[4mit.\e[24m \e[4mThis\e[24m \e[4mcauses\e[0m
+ \e[4mlynx\e[24m \e[4mto\e[24m \e[4mcontinuously\e[24m \e[4mspawn\e[24m \e[4mitself\e[24m \e[4mto\e[24m \e[4mview\e[24m \e[4mthe\e[24m \e[4mobject.\e[0m
On the other hand, maybe you don't want to use lynx interactively, you
just want to have it convert the text/html to text/plain, then you can
text/*; more
This is the simplest form of a mailcap file.
-
- 5\b5.\b.3\b3.\b.2\b2.\b. S\bSe\bec\bcu\bur\bre\be u\bus\bse\be o\bof\bf m\bma\bai\bil\blc\bca\bap\bp
+ \e[1m5.3.2. Secure use of mailcap\e[0m
The interpretion of shell meta-characters embedded in MIME parameters
can lead to security problems in general. Mutt tries to quote
care of it. Therefore you should pay attention to the following
rules:
- _\bK_\be_\be_\bp _\bt_\bh_\be _\b%_\b-_\be_\bx_\bp_\ba_\bn_\bd_\bo_\bs _\ba_\bw_\ba_\by _\bf_\br_\bo_\bm _\bs_\bh_\be_\bl_\bl _\bq_\bu_\bo_\bt_\bi_\bn_\bg_\b. Don't quote them with
+ \e[4mKeep\e[24m \e[4mthe\e[24m \e[4m%-expandos\e[24m \e[4maway\e[24m \e[4mfrom\e[24m \e[4mshell\e[24m \e[4mquoting.\e[24m Don't quote them with
single or double quotes. Mutt does this for you, the right way, as
should any other program which interprets mailcap. Don't put them
into backtick expansions. Be highly careful with eval statements, and
text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \
&& test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1
- 5\b5.\b.3\b3.\b.3\b3.\b. A\bAd\bdv\bva\ban\bnc\bce\bed\bd m\bma\bai\bil\blc\bca\bap\bp U\bUs\bsa\bag\bge\be
+ \e[1m5.3.3. Advanced mailcap Usage\e[0m
- 5\b5.\b.3\b3.\b.3\b3.\b.1\b1.\b. O\bOp\bpt\bti\bio\bon\bna\bal\bl F\bFi\bie\bel\bld\bds\bs
+ \e[1m5.3.3.1. Optional Fields\e[0m
In addition to the required content-type and view command fields, you
can add semi-colon ';' separated fields to set flags and other
options. Mutt recognizes the following optional fields:
- c\bco\bop\bpi\bio\bou\bus\bso\bou\but\btp\bpu\but\bt
+ \e[1mcopiousoutput\e[0m
This flag tells Mutt that the command passes possibly large
amounts of text on stdout. This causes Mutt to invoke a pager
(either the internal pager or the external pager defined by the
This will cause lynx to format the text/html output as text/plain
and Mutt will use your standard pager to display the results.
- n\bne\bee\bed\bds\bst\bte\ber\brm\bmi\bin\bna\bal\bl
+ \e[1mneedsterminal\e[0m
Mutt uses this flag when viewing attachments with ``autoview'',
in order to decide whether it should honor the setting of the
``$wait_key'' variable or not. When an attachment is viewed
using an interactive program, and the corresponding mailcap
- entry has a _\bn_\be_\be_\bd_\bs_\bt_\be_\br_\bm_\bi_\bn_\ba_\bl flag, Mutt will use ``$wait_key'' and
+ entry has a \e[4mneedsterminal\e[24m flag, Mutt will use ``$wait_key'' and
the exit status of the program to decide if it will ask you to
press a key after the external program has exited. In all other
situations it will not prompt you for a key.
- c\bco\bom\bmp\bpo\bos\bse\be=\b=<\b<c\bco\bom\bmm\bma\ban\bnd\bd>\b>
+ \e[1mcompose=<command>\e[0m
This flag specifies the command to use to create a new
attachment of a specific MIME type. Mutt supports this from the
compose menu.
- c\bco\bom\bmp\bpo\bos\bse\bet\bty\byp\bpe\bed\bd=\b=<\b<c\bco\bom\bmm\bma\ban\bnd\bd>\b>
+ \e[1mcomposetyped=<command>\e[0m
This flag specifies the command to use to create a new
attachment of a specific MIME type. This command differs from
the compose command in that mutt will expect standard MIME
filename, description, etc. for a new attachment. Mutt
supports this from the compose menu.
- p\bpr\bri\bin\bnt\bt=\b=<\b<c\bco\bom\bmm\bma\ban\bnd\bd>\b>
+ \e[1mprint=<command>\e[0m
This flag specifies the command to use to print a specific MIME
type. Mutt supports this from the attachment and compose menus.
- e\bed\bdi\bit\bt=\b=<\b<c\bco\bom\bmm\bma\ban\bnd\bd>\b>
+ \e[1medit=<command>\e[0m
This flag specifies the command to use to edit a specific MIME
type. Mutt supports this from the compose menu, and also uses
it to compose new attachments. Mutt will default to the defined
editor for text attachments.
- n\bna\bam\bme\bet\bte\bem\bmp\bpl\bla\bat\bte\be=\b=<\b<t\bte\bem\bmp\bpl\bla\bat\bte\be>\b>
+ \e[1mnametemplate=<template>\e[0m
This field specifies the format for the file denoted by %s in
the command fields. Certain programs will require a certain
file extension, for instance, to correctly view a file. For
text/html; lynx %s; nametemplate=%s.html
- t\bte\bes\bst\bt=\b=<\b<c\bco\bom\bmm\bma\ban\bnd\bd>\b>
+ \e[1mtest=<command>\e[0m
This field specifies a command to run to test whether this
mailcap entry should be used. The command is defined with the
command expansion rules defined in the next section. If the
command returns 0, then the test passed, and Mutt uses this
entry. If the command returns non-zero, then the test failed,
- and Mutt continues searching for the right entry. N\bNo\bot\bte\be:\b: _\bt_\bh_\be
- _\bc_\bo_\bn_\bt_\be_\bn_\bt_\b-_\bt_\by_\bp_\be _\bm_\bu_\bs_\bt _\bm_\ba_\bt_\bc_\bh _\bb_\be_\bf_\bo_\br_\be _\bM_\bu_\bt_\bt _\bp_\be_\br_\bf_\bo_\br_\bm_\bs _\bt_\bh_\be _\bt_\be_\bs_\bt_\b. For
+ and Mutt continues searching for the right entry. \e[1mNote: \e[4m\e[22mthe\e[0m
+ \e[4mcontent-type\e[24m \e[4mmust\e[24m \e[4mmatch\e[24m \e[4mbefore\e[24m \e[4mMutt\e[24m \e[4mperforms\e[24m \e[4mthe\e[24m \e[4mtest.\e[24m For
example:
text/html; netscape -remote 'openURL(%s)' ; test=RunningX
In this example, Mutt will run the program RunningX which will
return 0 if the X Window manager is running, and non-zero if it
- isn't. If RunningX returns 0, then Mutt will call netscape to dis
+ isn't. If RunningX returns 0, then Mutt will call netscape to dis-
play the text/html object. If RunningX doesn't return 0, then Mutt
will go on to the next entry and use lynx to display the text/html
object.
- 5\b5.\b.3\b3.\b.3\b3.\b.2\b2.\b. S\bSe\bea\bar\brc\bch\bh O\bOr\brd\bde\ber\br
+ \e[1m5.3.3.2. Search Order\e[0m
When searching for an entry in the mailcap file, Mutt will search for
the most useful entry for its purpose. For instance, if you are
can then use the test feature to determine which viewer to use
interactively depending on your environment.
- text/html; netscape -remote 'openURL(%s)' ; test=RunningX
- text/html; lynx %s; nametemplate=%s.html
- text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
+ text/html; netscape -remote 'openURL(%s)' ; test=RunningX
+ text/html; lynx %s; nametemplate=%s.html
+ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput
For ``Autoview'', Mutt will choose the third entry because of the
copiousoutput tag. For interactive viewing, Mutt will run the program
- RunningX to determine if it should use the first entry. If the pro
+ RunningX to determine if it should use the first entry. If the pro-
gram returns non-zero, Mutt will use the second entry for interactive
viewing.
- 5\b5.\b.3\b3.\b.3\b3.\b.3\b3.\b. C\bCo\bom\bmm\bma\ban\bnd\bd E\bEx\bxp\bpa\ban\bns\bsi\bio\bon\bn
+ \e[1m5.3.3.3. Command Expansion\e[0m
The various commands defined in the mailcap files are passed to the
/bin/sh shell using the system() function. Before the command is
passed to /bin/sh -c, it is parsed to expand various special
parameters with information from Mutt. The keywords Mutt expands are:
- %\b%s\bs As seen in the basic mailcap section, this variable is expanded
+ \e[1m%s \e[22mAs seen in the basic mailcap section, this variable is expanded
to a filename specified by the calling program. This file
contains the body of the message to view/print/edit or where the
composing program should place the results of composition. In
addition, the use of this keyword causes Mutt to not pass the
body of the message to the view/print/edit program on stdin.
- %\b%t\bt Mutt will expand %t to the text representation of the content
+ \e[1m%t \e[22mMutt will expand %t to the text representation of the content
type of the message in the same form as the first parameter of
the mailcap definition line, ie text/html or image/gif.
- %
\b%{
\b{<
\b<p
\bpa
\bar
\bra
\bam
\bme
\bet
\bte
\ber
\br>
\b>}
\b}
+
\e[1m%{<parameter>}
\e[0m
Mutt will expand this to the value of the specified parameter
from the Content-Type: line of the mail message. For instance,
if Your mail message contains:
-
Content-Type: text/plain; charset=iso-8859-1
- then Mutt will expand %{charset} to iso-8859-1. The default meta
+ then Mutt will expand %{charset} to iso-8859-1. The default meta-
mail mailcap file uses this feature to test the charset to spawn an
xterm using the right charset to view the message.
- \\b\%\b% This will be replaced by a %
+ \e[1m\% \e[22mThis will be replaced by a %
Mutt does not currently support the %F and %n keywords specified in
- RFC 1524. The main purpose of these parameters is for multipart mes
+ RFC 1524. The main purpose of these parameters is for multipart mes-
sages, which is handled internally by Mutt.
- 5\b5.\b.3\b3.\b.4\b4.\b. E\bEx\bxa\bam\bmp\bpl\ble\be m\bma\bai\bil\blc\bca\bap\bp f\bfi\bil\ble\bes\bs
+ \e[1m5.3.4. Example mailcap files\e[0m
This mailcap file is fairly simple and standard:
application/ms-excel; open.pl %s
______________________________________________________________________
- 5\b5.\b.4\b4.\b. M\bMI\bIM\bME\bE A\bAu\but\bto\bov\bvi\bie\bew\bw
+ \e[1m5.4. MIME Autoview\e[0m
In addition to explicitly telling Mutt to view an attachment with the
MIME viewer defined in the mailcap file, Mutt has support for
Mutt could use the following mailcap entries to automatically view
attachments of these types.
- text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
- image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
- application/x-gunzip; gzcat; copiousoutput
- application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
- application/postscript; ps2ascii %s; copiousoutput
+ text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html
+ image/*; anytopnm %s | pnmscale -xsize 80 -ysize 50 | ppmtopgm | pgmtopbm | pbmtoascii ; copiousoutput
+ application/x-gunzip; gzcat; copiousoutput
+ application/x-tar-gz; gunzip -c %s | tar -tf - ; copiousoutput
+ application/postscript; ps2ascii %s; copiousoutput
``unauto_view'' can be used to remove previous entries from the
autoview list. This can be used with message-hook to autoview
messages based on size, etc. ``unauto_view *'' will remove all
previous entries.
- 5\b5.\b.5\b5.\b. M\bMI\bIM\bME\bE M\bMu\bul\blt\bti\bip\bpa\bar\brt\bt/\b/A\bAl\blt\bte\ber\brn\bna\bat\bti\biv\bve\be
+ \e[1m5.5. MIME Multipart/Alternative\e[0m
Mutt has some heuristics for determining which attachment of a
multipart/alternative type to display. First, mutt will check the
To remove a MIME type from the alternative_order list, use the
unalternative_order command.
- 5\b5.\b.6\b6.\b. M\bMI\bIM\bME\bE L\bLo\boo\bok\bku\bup\bp
+ \e[1m5.6. MIME Lookup\e[0m
Mutt's mime_lookup list specifies a list of mime-types that should not
be treated according to their mailcap entry. This option is designed
mailcap file and according to any other configuration options (such as
auto_view) specified. Common usage would be:
- mime-lookup application/octet-stream application/X-Lotus-Manuscript
+ mime_lookup application/octet-stream application/X-Lotus-Manuscript
In addition, the unmime_lookup command may be used to disable this
feature for any particular mime-type if it had been set, for example,
in a global muttrc.
- 6\b6.\b. R\bRe\bef\bfe\ber\bre\ben\bnc\bce\be
+ \e[1m6. Reference\e[0m
- 6\b6.\b.1\b1.\b. C\bCo\bom\bmm\bma\ban\bnd\bd l\bli\bin\bne\be o\bop\bpt\bti\bio\bon\bns\bs
+ \e[1m6.1. Command line options\e[0m
Running mutt with no arguments will make Mutt attempt to read your
spool mailbox. However, it is possible to read other mailboxes and to
To read messages in a mailbox
- mutt [ -nz ] [ -F _\bm_\bu_\bt_\bt_\br_\bc ] [ -m _\bt_\by_\bp_\be ] [ -f _\bm_\ba_\bi_\bl_\bb_\bo_\bx ]
+ mutt [ -nz ] [ -F \e[4mmuttrc\e[24m ] [ -m \e[4mtype\e[24m ] [ -f \e[4mmailbox\e[24m ]
To compose a new message
- mutt [ -n ] [ -F _\bm_\bu_\bt_\bt_\br_\bc ] [ -a _\bf_\bi_\bl_\be ] [ -c _\ba_\bd_\bd_\br_\be_\bs_\bs ] [ -i _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ] [
- -s _\bs_\bu_\bb_\bj_\be_\bc_\bt ] _\ba_\bd_\bd_\br_\be_\bs_\bs [ _\ba_\bd_\bd_\br_\be_\bs_\bs ... ]
+ mutt [ -n ] [ -F \e[4mmuttrc\e[24m ] [ -a \e[4mfile\e[24m ] [ -c \e[4maddress\e[24m ] [ -i \e[4mfilename\e[24m ] [
+ -s \e[4msubject\e[24m ] \e[4maddress\e[24m [ \e[4maddress\e[24m ... ]
Mutt also supports a ``batch'' mode to send prepared messages. Simply
redirect input from the file you wish to send. For example,
subject of ``data set for run #2''. In the body of the message will
be the contents of the file ``~/run2.dat''.
- 6\b6.\b.2\b2.\b. C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn C\bCo\bom\bmm\bma\ban\bnd\bds\bs
+ \e[1m6.2. Configuration Commands\e[0m
The following are the commands understood by mutt.
- · ``account-hook'' _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ · ``account-hook'' \e[4mpattern\e[24m \e[4mcommand\e[0m
+
+ · ``alias'' \e[4mkey\e[24m \e[4maddress\e[24m [ , \e[4maddress\e[24m, ... ]
+
+ · ``unalias'' [ * | \e[4mkey\e[24m ... ]
+
+ · ``alternates'' \e[4mregexp\e[24m [ \e[4mregexp\e[24m ... ]
- · ``alias'' _\bk_\be_\by _\ba_\bd_\bd_\br_\be_\bs_\bs [ , _\ba_\bd_\bd_\br_\be_\bs_\bs, ... ]
+ · ``unalternates'' [ * | \e[4mregexp\e[24m ... ]
- · ``unalias'' [ * | _\bk_\be_\by ... ]
+ · ``alternative_order'' \e[4mmimetype\e[24m [ \e[4mmimetype\e[24m ... ]
- · ``alternates'' _\br_\be_\bg_\be_\bx_\bp [ _\br_\be_\bg_\be_\bx_\bp ... ]
+ · ``unalternative_order'' \e[4mmimetype\e[24m [ \e[4mmimetype\e[24m ... ]
- · ``unalternates'' [ * | _\br_\be_\bg_\be_\bx_\bp ... ]
+ · ``auto_view'' \e[4mmimetype\e[24m [ \e[4mmimetype\e[24m ... ]
- · ``alternative_order'' _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ · ``unauto_view'' \e[4mmimetype\e[24m [ \e[4mmimetype\e[24m ... ]
- · ``unalternative_order'' _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ · ``bind'' \e[4mmap\e[24m \e[4mkey\e[24m \e[4mfunction\e[0m
- · ``auto_view'' _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ · ``charset-hook'' \e[4malias\e[24m \e[4mcharset\e[0m
- · ``unauto_view'' _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ · ``color'' \e[4mobject\e[24m \e[4mforeground\e[24m \e[4mbackground\e[24m [ \e[4mregexp\e[24m ]
- · ``bind'' _\bm_\ba_\bp _\bk_\be_\by _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn
+ · ``uncolor'' \e[4mindex\e[24m \e[4mpattern\e[24m [ \e[4mpattern\e[24m ... ]
- · ``charset-hook'' _\ba_\bl_\bi_\ba_\bs _\bc_\bh_\ba_\br_\bs_\be_\bt
+ · ``exec'' \e[4mfunction\e[24m [ \e[4mfunction\e[24m ... ]
- · ``color'' _\bo_\bb_\bj_\be_\bc_\bt _\bf_\bo_\br_\be_\bg_\br_\bo_\bu_\bn_\bd _\bb_\ba_\bc_\bk_\bg_\br_\bo_\bu_\bn_\bd [ _\br_\be_\bg_\be_\bx_\bp ]
+ · ``fcc-hook'' \e[4mpattern\e[24m \e[4mmailbox\e[0m
- · ``uncolor'' _\bi_\bn_\bd_\be_\bx _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ · ``fcc-save-hook'' \e[4mpattern\e[24m \e[4mmailbox\e[0m
- · ``exec'' _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn [ _\bf_\bu_\bn_\bc_\bt_\bi_\bo_\bn ... ]
+ · ``folder-hook'' \e[4mpattern\e[24m \e[4mcommand\e[0m
- · ``fcc-hook'' _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ · ``hdr_order'' \e[4mheader\e[24m [ \e[4mheader\e[24m ... ]
- · ``fcc-save-hook'' _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ · ``unhdr_order'' \e[4mheader\e[24m [ \e[4mheader\e[24m ... ]
- · ``folder-hook'' _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ · ``iconv-hook'' \e[4mcharset\e[24m \e[4mlocal-charset\e[0m
- · ``hdr_order'' _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+ · ``ignore'' \e[4mpattern\e[24m [ \e[4mpattern\e[24m ... ]
- · ``unhdr_order'' _\bh_\be_\ba_\bd_\be_\br [ _\bh_\be_\ba_\bd_\be_\br ... ]
+ · ``unignore'' \e[4mpattern\e[24m [ \e[4mpattern\e[24m ... ]
- · ``iconv-hook'' _\bc_\bh_\ba_\br_\bs_\be_\bt _\bl_\bo_\bc_\ba_\bl_\b-_\bc_\bh_\ba_\br_\bs_\be_\bt
+ · ``lists'' \e[4mregexp\e[24m [ \e[4mregexp\e[24m ... ]
- · ``ignore'' _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ · ``unlists'' \e[4mregexp\e[24m [ \e[4mregexp\e[24m ... ]
- · ``unignore'' _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ · ``macro'' \e[4mmenu\e[24m \e[4mkey\e[24m \e[4msequence\e[24m [ \e[4mdescription\e[24m ]
- · ``lists'' _\ba_\bd_\bd_\br_\be_\bs_\bs [ _\ba_\bd_\bd_\br_\be_\bs_\bs ... ]
+ · ``mailboxes'' \e[4mfilename\e[24m [ \e[4mfilename\e[24m ... ]
- · ``unlists'' _\ba_\bd_\bd_\br_\be_\bs_\bs [ _\ba_\bd_\bd_\br_\be_\bs_\bs ... ]
+ · ``mbox-hook'' \e[4mpattern\e[24m \e[4mmailbox\e[0m
- · ``macro'' _\bm_\be_\bn_\bu _\bk_\be_\by _\bs_\be_\bq_\bu_\be_\bn_\bc_\be [ _\bd_\be_\bs_\bc_\br_\bi_\bp_\bt_\bi_\bo_\bn ]
+ · ``message-hook'' \e[4mpattern\e[24m \e[4mcommand\e[0m
- · ``mailboxes'' _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be [ _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be ... ]
+ · ``mime_lookup'' \e[4mmimetype\e[24m [ \e[4mmimetype\e[24m ... ]
- · ``mbox-hook'' _\bp_\ba_\bt_\bt_\be_\br_\bn _\bm_\ba_\bi_\bl_\bb_\bo_\bx
+ · ``unmime_lookup'' \e[4mmimetype\e[24m [ \e[4mmimetype\e[24m ... ]
- · ``message-hook'' _\bp_\ba_\bt_\bt_\be_\br_\bn _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ · ``mono'' \e[4mobject\e[24m \e[4mattribute\e[24m [ \e[4mregexp\e[24m ]
- · ``mime_lookup'' _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ · ``unmono'' \e[4mindex\e[24m \e[4mpattern\e[24m [ \e[4mpattern\e[24m ... ]
- · ``unmime_lookup'' _\bm_\bi_\bm_\be_\bt_\by_\bp_\be [ _\bm_\bi_\bm_\be_\bt_\by_\bp_\be ... ]
+ · ``my_hdr'' \e[4mstring\e[0m
- · ``mono'' _\bo_\bb_\bj_\be_\bc_\bt _\ba_\bt_\bt_\br_\bi_\bb_\bu_\bt_\be [ _\br_\be_\bg_\be_\bx_\bp ]
+ · ``unmy_hdr'' \e[4mfield\e[24m [ \e[4mfield\e[24m ... ]
- · ``unmono'' _\bi_\bn_\bd_\be_\bx _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ · ``crypt-hook'' \e[4mpattern\e[24m \e[4mkey-id\e[0m
- · ``my_hdr'' _\bs_\bt_\br_\bi_\bn_\bg
+ · ``push'' \e[4mstring\e[0m
- · ``unmy_hdr'' _\bf_\bi_\be_\bl_\bd [ _\bf_\bi_\be_\bl_\bd ... ]
+ · ``reset'' \e[4mvariable\e[24m [\e[4mvariable\e[24m ... ]
- · ``crypt-hook'' _\bp_\ba_\bt_\bt_\be_\br_\bn _\bk_\be_\by_\b-_\bi_\bd
+ · ``save-hook'' \e[4mregexp\e[24m \e[4mfilename\e[0m
- · ``push'' _\bs_\bt_\br_\bi_\bn_\bg
+ · ``score'' \e[4mpattern\e[24m \e[4mvalue\e[0m
- · ``reset'' _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ · ``unscore'' \e[4mpattern\e[24m [ \e[4mpattern\e[24m ... ]
- · ``save-hook'' _\br_\be_\bg_\be_\bx_\bp _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ · ``send-hook'' \e[4mregexp\e[24m \e[4mcommand\e[0m
- · ``score'' _\bp_\ba_\bt_\bt_\be_\br_\bn _\bv_\ba_\bl_\bu_\be
+ · ``reply-hook'' \e[4mregexp\e[24m \e[4mcommand\e[0m
- · ``unscore'' _\bp_\ba_\bt_\bt_\be_\br_\bn [ _\bp_\ba_\bt_\bt_\be_\br_\bn ... ]
+ · ``set'' [no|inv]\e[4mvariable\e[24m[=\e[4mvalue\e[24m] [ \e[4mvariable\e[24m ... ]
- · ``send-hook'' _\br_\be_\bg_\be_\bx_\bp _\bc_\bo_\bm_\bm_\ba_\bn_\bd
+ · ``unset'' \e[4mvariable\e[24m [\e[4mvariable\e[24m ... ]
- · ``set'' [no|inv]_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be[=_\bv_\ba_\bl_\bu_\be] [ _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ · ``source'' \e[4mfilename\e[0m
- · ``unset'' _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ · ``spam'' \e[4mpattern\e[24m \e[4mformat\e[0m
- · ``source'' _\bf_\bi_\bl_\be_\bn_\ba_\bm_\be
+ · ``nospam'' \e[4mpattern\e[0m
- · ``subscribe'' _\ba_\bd_\bd_\br_\be_\bs_\bs [ _\ba_\bd_\bd_\br_\be_\bs_\bs ... ]
+ · ``subscribe'' \e[4mregexp\e[24m [ \e[4mregexp\e[24m ... ]
- · ``unsubscribe'' _\ba_\bd_\bd_\br_\be_\bs_\bs [ _\ba_\bd_\bd_\br_\be_\bs_\bs ... ]
+ · ``unsubscribe'' \e[4mregexp\e[24m [ \e[4mregexp\e[24m ... ]
- · ``toggle'' _\bv_\ba_\br_\bi_\ba_\bb_\bl_\be [_\bv_\ba_\br_\bi_\ba_\bb_\bl_\be ... ]
+ · ``toggle'' \e[4mvariable\e[24m [\e[4mvariable\e[24m ... ]
- · ``unhook'' _\bh_\bo_\bo_\bk_\b-_\bt_\by_\bp_\be
+ · ``unhook'' \e[4mhook-type\e[0m
- 6\b6.\b.3\b3.\b. C\bCo\bon\bnf\bfi\big\bgu\bur\bra\bat\bti\bio\bon\bn v\bva\bar\bri\bia\bab\bbl\ble\bes\bs
+ \e[1m6.3. Configuration variables\e[0m
- 6\b6.\b.3\b3.\b.1\b1.\b. a\bab\bbo\bor\brt\bt_\b_n\bno\bos\bsu\bub\bbj\bje\bec\bct\bt
+ \e[1m6.3.1. abort_nosubject\e[0m
Type: quadoption
Default: ask-yes
- If set to _\by_\be_\bs, when composing messages and no subject is given at the
- subject prompt, composition will be aborted. If set to _\bn_\bo, composing
+ If set to \e[4myes\e[24m, when composing messages and no subject is given at the
+ subject prompt, composition will be aborted. If set to \e[4mno\e[24m, composing
messages with no subject given at the subject prompt will never be
aborted.
- 6\b6.\b.3\b3.\b.2\b2.\b. a\bab\bbo\bor\brt\bt_\b_u\bun\bnm\bmo\bod\bdi\bif\bfi\bie\bed\bd
+ \e[1m6.3.2. abort_unmodified\e[0m
Type: quadoption
Default: yes
- If set to _\by_\be_\bs, composition will automatically abort after editing the
+ If set to \e[4myes\e[24m, composition will automatically abort after editing the
message body if no changes are made to the file (this check only
- happens after the _\bf_\bi_\br_\bs_\bt edit of the file). When set to _\bn_\bo,
+ happens after the \e[4mfirst\e[24m edit of the file). When set to \e[4mno\e[24m,
composition will never be aborted.
- 6\b6.\b.3\b3.\b.3\b3.\b. a\bal\bli\bia\bas\bs_\b_f\bfi\bil\ble\be
+ \e[1m6.3.3. alias_file\e[0m
Type: path
Default: "~/.muttrc"
The default file in which to save aliases created by the ````create-
alias'''' function.
- N\bNo\bot\bte\be:\b: Mutt will not automatically source this file; you must
+ \e[1mNote: \e[22mMutt will not automatically source this file; you must
explicitly use the ````source'''' command for it to be executed.
- 6\b6.\b.3\b3.\b.4\b4.\b. a\bal\bli\bia\bas\bs_\b_f\bfo\bor\brm\bma\bat\bt
+ \e[1m6.3.4. alias_format\e[0m
Type: string
Default: "%4n %2f %t %-10a %r"
Specifies the format of the data displayed for the `alias' menu. The
following printf(3)-style sequences are available:
- %\b%a\ba alias name
+ \e[1m%a \e[22malias name
- %\b%f\bf flags - currently, a "d" for an alias marked for deletion
+ \e[1m%f \e[22mflags - currently, a "d" for an alias marked for deletion
- %\b%n\bn index number
+ \e[1m%n \e[22mindex number
- %\b%r\br address which alias expands to
+ \e[1m%r \e[22maddress which alias expands to
- %\b%t\bt character which indicates if the alias is tagged for inclusion
+ \e[1m%t \e[22mcharacter which indicates if the alias is tagged for inclusion
- 6\b6.\b.3\b3.\b.5\b5.\b. a\bal\bll\blo\bow\bw_\b_8\b8b\bbi\bit\bt
+ \e[1m6.3.5. allow_8bit\e[0m
Type: boolean
Default: yes
Controls whether 8-bit data is converted to 7-bit using either Quoted-
Printable or Base64 encoding when sending mail.
- 6\b6.\b.3\b3.\b.6\b6.\b. a\bal\bll\blo\bow\bw_\b_a\ban\bns\bsi\bi
+ \e[1m6.3.6. allow_ansi\e[0m
Type: boolean
Default: no
"[-- PGP output follows ..." and give it the same color as your
attachment color.
- 6\b6.\b.3\b3.\b.7\b7.\b. a\bar\brr\bro\bow\bw_\b_c\bcu\bur\brs\bso\bor\br
+ \e[1m6.3.7. arrow_cursor\e[0m
Type: boolean
Default: no
has to be redrawn on the screen when moving to the next or previous
entries in the menu.
- 6\b6.\b.3\b3.\b.8\b8.\b. a\bas\bsc\bci\bii\bi_\b_c\bch\bha\bar\brs\bs
+ \e[1m6.3.8. ascii_chars\e[0m
Type: boolean
Default: no
If set, Mutt will use plain ASCII characters when displaying thread
- and attachment trees, instead of the default _\bA_\bC_\bS characters.
+ and attachment trees, instead of the default \e[4mACS\e[24m characters.
- 6\b6.\b.3\b3.\b.9\b9.\b. a\bas\bsk\bkb\bbc\bcc\bc
+ \e[1m6.3.9. askbcc\e[0m
Type: boolean
Default: no
If set, Mutt will prompt you for blind-carbon-copy (Bcc) recipients
before editing an outgoing message.
- 6\b6.\b.3\b3.\b.1\b10\b0.\b. a\bas\bsk\bkc\bcc\bc
+ \e[1m6.3.10. askcc\e[0m
Type: boolean
Default: no
mailbox-order (unsorted)
score
size
+ spam
subject
threads
to
%?<sequence_char>?<optional_string>?
- where _\bs_\be_\bq_\bu_\be_\bn_\bc_\be_\b__\bc_\bh_\ba_\br is a character from the table above, and
- _\bo_\bp_\bt_\bi_\bo_\bn_\ba_\bl_\b__\bs_\bt_\br_\bi_\bn_\bg is the string you would like printed if _\bs_\bt_\ba_\bt_\bu_\bs_\b__\bc_\bh_\ba_\br is
- nonzero. _\bo_\bp_\bt_\bi_\bo_\bn_\ba_\bl_\b__\bs_\bt_\br_\bi_\bn_\bg m\bma\bay\by contain other sequence as well as normal
- text, but you may n\bno\bot\bt nest optional strings.
+ where \e[4msequence_char\e[24m is a character from the table above, and
+ \e[4moptional_string\e[24m is the string you would like printed if \e[4mstatus_char\e[24m is
+ nonzero. \e[4moptional_string\e[24m \e[1mmay \e[22mcontain other sequence as well as normal
+ text, but you may \e[1mnot \e[22mnest optional strings.
Here is an example illustrating how to optionally print the number of
new messages in a mailbox: %?n?%n new messages.?
If _\bs_\be_\bt, Mutt will add ``X-Comment-To:'' field (that contains full name
of original article author) to article that followuped to newsgroup.
- 6\b6.\b.4\b4.\b. F\bFu\bun\bnc\bct\bti\bio\bon\bns\bs
+ \e[1m6.4. Functions\e[0m
The following is the list of available functions listed by the mapping
in which they are available. The default key setting is given, and an
explanation of what the function does. The key bindings of these
functions can be changed with the ``bind'' command.
- 6\b6.\b.4\b4.\b.1\b1.\b. g\bge\ben\bne\ber\bri\bic\bc
+ \e[1m6.4.1. generic\e[0m
- The _\bg_\be_\bn_\be_\br_\bi_\bc menu is not a real menu, but specifies common functions
- (such as movement) available in all menus except for _\bp_\ba_\bg_\be_\br and _\be_\bd_\bi_\bt_\bo_\br.
+ The \e[4mgeneric\e[24m menu is not a real menu, but specifies common functions
+ (such as movement) available in all menus except for \e[4mpager\e[24m and \e[4meditor\e[24m.
Changing settings for this menu will affect the default bindings for
all menus (except as noted).
shell-escape ! run a program in a subshell
tag-entry t toggle the tag on the current entry
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
- 6\b6.\b.4\b4.\b.2\b2.\b. i\bin\bnd\bde\bex\bx
+ \e[1m6.4.2. index\e[0m
bounce-message b remail a message to another user
change-folder c open a different folder
untag-pattern ^T untag messages matching a pattern
view-attachments v show MIME attachments
- 6\b6.\b.4\b4.\b.3\b3.\b. p\bpa\bag\bge\ber\br
+ \e[1m6.4.3. pager\e[0m
bottom not bound jump to the bottom of the message
bounce-message b remail a message to another user
undelete-thread ^U undelete all messages in thread
view-attachments v show MIME attachments
- 6\b6.\b.4\b4.\b.4\b4.\b. a\bal\bli\bia\bas\bs
+ \e[1m6.4.4. alias\e[0m
search / search for a regular expression
search-next n search for next match
search-reverse ESC / search backwards for a regular expression
- 6\b6.\b.4\b4.\b.5\b5.\b. q\bqu\bue\ber\bry\by
+ \e[1m6.4.5. query\e[0m
create-alias a create an alias from a message sender
mail m compose a new mail message
search-opposite not bound search for next match in opposite direction
search-reverse ESC / search backwards for a regular expression
- 6\b6.\b.4\b4.\b.6\b6.\b. a\bat\btt\bta\bac\bch\bh
+ \e[1m6.4.6. attach\e[0m
bounce-message b remail a message to another user
collapse-parts v toggle display of subparts
view-mailcap m force viewing of attachment using mailcap
view-text T view attachment as text
- 6\b6.\b.4\b4.\b.7\b7.\b. c\bco\bom\bmp\bpo\bos\bse\be
+ \e[1m6.4.7. compose\e[0m
attach-file a attach a file(s) to this message
attach-message A attach message(s) to this message
view-attach RET view attachment using mailcap entry if necessary
write-fcc w write the message to a folder
- 6\b6.\b.4\b4.\b.8\b8.\b. p\bpo\bos\bst\btp\bpo\bon\bne\be
+ \e[1m6.4.8. postpone\e[0m
delete-entry d delete the current entry
undelete-entry u undelete the current entry
- 6\b6.\b.4\b4.\b.9\b9.\b. b\bbr\bro\bow\bws\bse\ber\br
+ \e[1m6.4.9. browser\e[0m
change-dir c change directories
check-new TAB check mailboxes for new mail
unsubscribe u unsubscribe to current mailbox (IMAP Only)
toggle-subscribed T toggle view all/subscribed mailboxes (IMAP Only)
- 6\b6.\b.4\b4.\b.1\b10\b0.\b. p\bpg\bgp\bp
+ \e[1m6.4.10. pgp\e[0m
view-name % view the key's user id
verify-key c verify a PGP public key
- 6\b6.\b.4\b4.\b.1\b11\b1.\b. e\bed\bdi\bit\bto\bor\br
+ \e[1m6.4.11. editor\e[0m
backspace BackSpace delete the char in front of the cursor
backward-char ^B move the cursor one character to the left
transpose-chars not bound transpose character under cursor with previous
upcase-word ESC u uppercase all characters in current word
- 7\b7.\b. M\bMi\bis\bsc\bce\bel\bll\bla\ban\bny\by
+ \e[1m7. Miscellany\e[0m
- 7\b7.\b.1\b1.\b. A\bAc\bck\bkn\bno\bow\bwl\ble\bed\bdg\bge\bem\bme\ben\bnt\bts\bs
+ \e[1m7.1. Acknowledgements\e[0m
Kari Hurtta <kari.hurtta@fmi.fi> co-developed the original MIME
parsing code back in the ELM-ME days.
Vsevolod Volkov <vvv@lucky.net>,
Ken Weinert <kenw@ihs.com>
- 7\b7.\b.2\b2.\b. A\bAb\bbo\bou\but\bt t\bth\bhi\bis\bs d\bdo\boc\bcu\bum\bme\ben\bnt\bt
+ \e[1m7.2. About this document\e[0m
This document was written in SGML, and then rendered using the sgml-
tools package.
projects / apps / madmutt.git / blobdiff