X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=doc%2Fmanual.txt;h=51caaf010f8d1ec738e070b31de492779e32b469;hp=bef333fb4fb48c381a1f05821208f21195d4829c;hb=afa60149c4d2bb71c8195091d3658b3bdc12d59d;hpb=9d2f1c9b6d2984bb6ee3e0a6c1709a678a801776 diff --git a/doc/manual.txt b/doc/manual.txt index bef333f..51caaf0 100644 --- a/doc/manual.txt +++ b/doc/manual.txt @@ -3,7 +3,7 @@ by Michael Elkins and others. - version 1.5.9 + version devel-r372 AAbbssttrraacctt @@ -94,7 +94,7 @@ _2_._1 _M_o_v_i_n_g _A_r_o_u_n_d _i_n _M_e_n_u_s Information is presented in menus, very similar to ELM. Here is a table show- - ing the common keys used to navigate menus in Mutt. + ing the common keys used to navigate menus in Mutt-ng. The Mutt-ng E-Mail Client 3 @@ -123,7 +123,7 @@ complete complete filename or alias ^T complete-query complete address with query ^K kill-eol delete to the end of the line - ESC d kill-eow delete to the end ot the word + ESC d kill-eow delete to the end of the word ^W kill-word kill the word in front of the cursor ^U kill-line delete entire line ^V quote-char quote the next typed key @@ -146,8 +146,8 @@ Similar to many other mail clients, there are two modes in which mail is read in Mutt-ng. The first is the index of messages in the mailbox, which is called - the ``index'' in Mutt. The second mode is the display of the message contents. - This is called the ``pager.'' + the ``index'' in Mutt-ng. The second mode is the display of the message con- + tents. This is called the ``pager.'' The Mutt-ng E-Mail Client 4 @@ -233,7 +233,7 @@ +o cclleeaarr--ffllaagg (default: W) Furthermore, the following flags reflect who the message is addressed to. They - can be customized with the _$_t_o___c_h_a_r_s (section 6.3.313 , page 141) variable. + can be customized with the _$_t_o___c_h_a_r_s (section 6.3.320 , page 143) variable. + message is to you and you only @@ -317,7 +317,7 @@ _2_._3_._3 _T_h_r_e_a_d_e_d _M_o_d_e - When the mailbox is _s_o_r_t_e_d (section 6.3.285 , page 133) by _t_h_r_e_a_d_s, there are + When the mailbox is _s_o_r_t_e_d (section 6.3.289 , page 134) by _t_h_r_e_a_d_s, there are a few additional functions available in the _i_n_d_e_x and _p_a_g_e_r modes. ^D delete-thread delete all messages in the current thread @@ -338,11 +338,11 @@ NNoottee:: Collapsing a thread displays only the first message in the thread and hides the others. This is useful when threads contain so many messages that you can only see a handful of threads on the screen. See %M in _$_i_n_d_e_x___f_o_r_m_a_t (sec- - tion 6.3.112 , page 91). For example, you could use "%?M?(#%03M)&(%4l)?" in - _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.112 , page 91) to optionally display the number of + tion 6.3.110 , page 90). For example, you could use "%?M?(#%03M)&(%4l)?" in + _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.110 , page 90) to optionally display the number of hidden messages if the thread is collapsed. - See also: _$_s_t_r_i_c_t___t_h_r_e_a_d_s (section 6.3.302 , page 139). + See also: _$_s_t_r_i_c_t___t_h_r_e_a_d_s (section 6.3.309 , page 141). _2_._3_._4 _M_i_s_c_e_l_l_a_n_e_o_u_s _F_u_n_c_t_i_o_n_s @@ -425,7 +425,7 @@ match the regular expressions given by the _l_i_s_t_s _o_r _s_u_b_s_c_r_i_b_e (section 3.10 , page 24) commands, but also honor any Mail-Followup-To header(s) if the - _$_h_o_n_o_r___f_o_l_l_o_w_u_p___t_o (section 6.3.91 , page 86) configuration variable is set. + _$_h_o_n_o_r___f_o_l_l_o_w_u_p___t_o (section 6.3.88 , page 85) configuration variable is set. Using this when replying to messages posted to mailing lists helps avoid dupli- cate copies being sent to the author of the message you are replying to. @@ -433,9 +433,9 @@ (default: |) Asks for an external Unix command and pipes the current or tagged message(s) to - it. The variables _$_p_i_p_e___d_e_c_o_d_e (section 6.3.192 , page 112), _$_p_i_p_e___s_p_l_i_t - (section 6.3.194 , page 112), _$_p_i_p_e___s_e_p (section 6.3.193 , page 112) and - _$_w_a_i_t___k_e_y (section 6.3.325 , page 144) control the exact behavior of this + it. The variables _$_p_i_p_e___d_e_c_o_d_e (section 6.3.200 , page 113), _$_p_i_p_e___s_p_l_i_t + (section 6.3.202 , page 114), _$_p_i_p_e___s_e_p (section 6.3.201 , page 114) and + _$_w_a_i_t___k_e_y (section 6.3.332 , page 145) control the exact behavior of this function. rreesseenndd--mmeessssaaggee @@ -445,7 +445,7 @@ message. This function is best described as "recall from arbitrary folders". It can conveniently be used to forward MIME messages while preserving the orig- inal mail structure. Note that the amount of headers included here depends on - the value of the _$_w_e_e_d (section 6.3.326 , page 144) variable. + the value of the _$_w_e_e_d (section 6.3.333 , page 146) variable. This function is also available from the attachment menu. You can use this to easily resend a message which was included with a bounce message as a mes- @@ -455,14 +455,14 @@ (default: !) Asks for an external Unix command and executes it. The _$_w_a_i_t___k_e_y (section - 6.3.325 , page 144) can be used to control whether Mutt-ng will wait for a key + 6.3.332 , page 145) can be used to control whether Mutt-ng will wait for a key to be pressed when the command returns (presumably to let the user read the output of the command), based on the return status of the named command. ttooggggllee--qquuootteedd (default: T) - The _p_a_g_e_r uses the _$_q_u_o_t_e___r_e_g_e_x_p (section 6.3.218 , page 118) variable to + The _p_a_g_e_r uses the _$_q_u_o_t_e___r_e_g_e_x_p (section 6.3.225 , page 119) variable to detect quoted text when displaying the body of the message. This function tog- gles the display of the quoted material in the message. It is particularly useful when are interested in just the response and there is a large amount of @@ -496,20 +496,20 @@ Mutt-ng will then enter the _c_o_m_p_o_s_e menu and prompt you for the recipients to place on the ``To:'' header field. Next, it will ask you for the ``Subject:'' field for the message, providing a default if you are replying to or forwarding - a message. See also _$_a_s_k_c_c (section 6.3.12 , page 67), _$_a_s_k_b_c_c (section - 6.3.11 , page 67), _$_a_u_t_o_e_d_i_t (section 6.3.19 , page 69), _$_b_o_u_n_c_e (section - 6.3.22 , page 70), and _$_f_a_s_t___r_e_p_l_y (section 6.3.61 , page 78) for changing - how Mutt asks these questions. - - Mutt will then automatically start your _$_e_d_i_t_o_r (section 6.3.57 , page 77) on - the message body. If the _$_e_d_i_t___h_e_a_d_e_r_s (section 6.3.56 , page 77) variable is - set, the headers will be at the top of the message in your editor. Any mes- + a message. See also _$_a_s_k_c_c (section 6.3.10 , page 67), _$_a_s_k_b_c_c (section + 6.3.9 , page 66), _$_a_u_t_o_e_d_i_t (section 6.3.17 , page 69), _$_b_o_u_n_c_e (section + 6.3.20 , page 69), and _$_f_a_s_t___r_e_p_l_y (section 6.3.60 , page 78) for changing + how Mutt-ng asks these questions. + + Mutt-ng will then automatically start your _$_e_d_i_t_o_r (section 6.3.55 , page 77) + on the message body. If the _$_e_d_i_t___h_e_a_d_e_r_s (section 6.3.54 , page 77) variable + is set, the headers will be at the top of the message in your editor. Any mes- sages you are replying to will be added in sort order to the message, with - appropriate _$_a_t_t_r_i_b_u_t_i_o_n (section 6.3.17 , page 69), _$_i_n_d_e_n_t___s_t_r_i_n_g (section - 6.3.111 , page 90) and _$_p_o_s_t___i_n_d_e_n_t___s_t_r_i_n_g (section 6.3.204 , page 115). - When forwarding a message, if the _$_m_i_m_e___f_o_r_w_a_r_d (section 6.3.139 , page 98) + appropriate _$_a_t_t_r_i_b_u_t_i_o_n (section 6.3.15 , page 68), _$_i_n_d_e_n_t___s_t_r_i_n_g (section + 6.3.109 , page 90) and _$_p_o_s_t___i_n_d_e_n_t___s_t_r_i_n_g (section 6.3.212 , page 116). + When forwarding a message, if the _$_m_i_m_e___f_o_r_w_a_r_d (section 6.3.136 , page 97) variable is unset, a copy of the forwarded message will be included. If you - have specified a _$_s_i_g_n_a_t_u_r_e (section 6.3.255 , page 126), it will be appended + have specified a _$_s_i_g_n_a_t_u_r_e (section 6.3.259 , page 127), it will be appended to the message. Once you have finished editing the body of your mail message, you are returned @@ -542,7 +542,7 @@ sages from. You can now tag messages in that folder and they will be attached to the message you are sending. Note that certain operations like composing a new mail, replying, forwarding, etc. are not permitted when you are in that - folder. The %r in _$_s_t_a_t_u_s___f_o_r_m_a_t (section 6.3.299 , page 137) will change to a + folder. The %r in _$_s_t_a_t_u_s___f_o_r_m_a_t (section 6.3.305 , page 138) will change to a 'A' to indicate that you are in attach-message mode. _2_._4_._1 _E_d_i_t_i_n_g _t_h_e _m_e_s_s_a_g_e _h_e_a_d_e_r @@ -554,8 +554,8 @@ Fcc: _f_i_l_e_n_a_m_e - Mutt will pick up _f_i_l_e_n_a_m_e just as if you had used the _e_d_i_t_-_f_c_c function in the - _c_o_m_p_o_s_e menu. + Mutt-ng will pick up _f_i_l_e_n_a_m_e just as if you had used the _e_d_i_t_-_f_c_c function in + the _c_o_m_p_o_s_e menu. You can also attach files to your message by specifying @@ -565,28 +565,28 @@ use as the description of the attached file. When replying to messages, if you remove the _I_n_-_R_e_p_l_y_-_T_o_: field from the header - field, Mutt will not generate a _R_e_f_e_r_e_n_c_e_s_: field, which allows you to create a - new message thread. + field, Mutt-ng will not generate a _R_e_f_e_r_e_n_c_e_s_: field, which allows you to cre- + ate a new message thread. - Also see _e_d_i_t___h_e_a_d_e_r_s (section 6.3.56 , page 77). + Also see _e_d_i_t___h_e_a_d_e_r_s (section 6.3.54 , page 77). The Mutt-ng E-Mail Client 12 - _2_._4_._2 _U_s_i_n_g _M_u_t_t _w_i_t_h _P_G_P + _2_._4_._2 _U_s_i_n_g _M_u_t_t_-_n_g _w_i_t_h _P_G_P If you want to use PGP, you can specify Pgp: [ E | S | S_<_i_d_> ] ``E'' encrypts, ``S'' signs and ``S'' signs with the given key, setting - _$_p_g_p___s_i_g_n___a_s (section 6.3.184 , page 110) permanently. + _$_p_g_p___s_i_g_n___a_s (section 6.3.192 , page 112) permanently. If you have told mutt to PGP encrypt a message, it will guide you through a key - selection process when you try to send the message. Mutt will not ask you any - questions about keys which have a certified user ID matching one of the message - recipients' mail addresses. However, there may be situations in which there - are several keys, weakly certified user ID fields, or where no matching keys - can be found. + selection process when you try to send the message. Mutt-ng will not ask you + any questions about keys which have a certified user ID matching one of the + message recipients' mail addresses. However, there may be situations in which + there are several keys, weakly certified user ID fields, or where no matching + keys can be found. In these cases, you are dropped into a menu with a list of keys from which you can select one. When you quit this menu, or mutt can't find any matching keys, @@ -597,7 +597,7 @@ encrypted using the selected public keys, and sent out. Most fields of the entries in the key selection menu (see also _$_p_g_p___e_n_t_r_y___f_o_r_- - _m_a_t (section 6.3.171 , page 107)) have obvious meanings. But some explana- + _m_a_t (section 6.3.179 , page 109)) have obvious meanings. But some explana- tions on the capabilities, flags, and validity fields are in order. The flags sequence (%f) will expand to one of the following flags: @@ -637,7 +637,7 @@ called 2.9b23. To use it, you'll have to obey certain restrictions. Most important, you can- - not use the Cc and Bcc headers. To tell Mutt to use mixmaster, you have to + not use the Cc and Bcc headers. To tell Mutt-ng to use mixmaster, you have to select a remailer chain, using the mix function on the compose menu. The chain selection screen is divided into two parts. In the (larger) upper @@ -653,8 +653,8 @@ leave the menu, or accept them pressing (by default) the Return key. Note that different remailers do have different capabilities, indicated in the - %c entry of the remailer menu lines (see _$_m_i_x___e_n_t_r_y___f_o_r_m_a_t (section 6.3.143 , - page 99)). Most important is the ``middleman'' capability, indicated by a cap- + %c entry of the remailer menu lines (see _$_m_i_x___e_n_t_r_y___f_o_r_m_a_t (section 6.3.139 , + page 98)). Most important is the ``middleman'' capability, indicated by a cap- ital ``M'': This means that the remailer in question cannot be used as the final element of a chain, but will only forward messages to other mixmaster remailers. For details on the other capabilities, please have a look at the @@ -663,7 +663,7 @@ _2_._5 _F_o_r_w_a_r_d_i_n_g _a_n_d _B_o_u_n_c_i_n_g _M_a_i_l Bouncing and forwarding let you send an existing message to recipients that you - specify. Bouncing a message uses the _s_e_n_d_m_a_i_l (section 6.3.241 , page 123) + specify. Bouncing a message uses the _s_e_n_d_m_a_i_l (section 6.3.247 , page 124) command to send a copy to alternative addresses as if they were the message's original recipients. Forwarding a message, on the other hand, allows you to modify the message before it is resent (for example, by adding your own com- @@ -676,19 +676,19 @@ Forwarding can be done by including the original message in the new message's body (surrounded by indicating lines) or including it as a MIME attachment, - depending on the value of the _$_m_i_m_e___f_o_r_w_a_r_d (section 6.3.139 , page 98) vari- + depending on the value of the _$_m_i_m_e___f_o_r_w_a_r_d (section 6.3.136 , page 97) vari- able. Decoding of attachments, like in the pager, can be controlled by the - _$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 6.3.71 , page 81) and _$_m_i_m_e___f_o_r_w_a_r_d___d_e_c_o_d_e (section + _$_f_o_r_w_a_r_d___d_e_c_o_d_e (section 6.3.69 , page 81) and _$_m_i_m_e___f_o_r_w_a_r_d___d_e_c_o_d_e (section The Mutt-ng E-Mail Client 14 - 6.3.140 , page 99) variables, respectively. The desired forwarding format may + 6.3.137 , page 98) variables, respectively. The desired forwarding format may depend on the content, therefore _$_m_i_m_e___f_o_r_w_a_r_d is a quadoption which, for exam- ple, can be set to ``ask-no''. The inclusion of headers is controlled by the current setting of the _$_w_e_e_d - (section 6.3.326 , page 144) variable, unless _m_i_m_e___f_o_r_w_a_r_d (section 6.3.139 , - page 98) is set. + (section 6.3.333 , page 146) variable, unless _m_i_m_e___f_o_r_w_a_r_d (section 6.3.136 , + page 97) is set. Editing the message to forward follows the same procedure as sending or reply- ing to a message does. @@ -698,8 +698,9 @@ At times it is desirable to delay sending a message that you have already begun to compose. When the _p_o_s_t_p_o_n_e_-_m_e_s_s_a_g_e function is used in the _c_o_m_p_o_s_e menu, the body of your message and attachments are stored in the mailbox specified by - the _$_p_o_s_t_p_o_n_e_d (section 6.3.207 , page 115) variable. This means that you can - recall the message even if you exit Mutt and then restart it at a later time. + the _$_p_o_s_t_p_o_n_e_d (section 6.3.214 , page 117) variable. This means that you can + recall the message even if you exit Mutt-ng and then restart it at a later + time. Once a message is postponed, there are several ways to resume it. From the command line you can use the ``-p'' option, or if you _c_o_m_p_o_s_e a new message @@ -712,41 +713,41 @@ be in the same folder with the message you replied to for the status of the message to be updated. - See also the _$_p_o_s_t_p_o_n_e (section 6.3.206 , page 115) quad-option. + See also the _$_p_o_s_t_p_o_n_e (section 6.3.213 , page 116) quad-option. _2_._7 _R_e_a_d_i_n_g _n_e_w_s _v_i_a _N_N_T_P - If compiled with ``--enable-nntp'' option, Mutt can read news from newsserver - via NNTP. You can open a newsgroup with function ``change-newsgroup'' - (default: i). Default newsserver can be obtained from _N_N_T_P_S_E_R_V_E_R environment - variable. Like other news readers, info about subscribed newsgroups is saved - in file by _$_n_e_w_s_r_c (section 6.3.150 , page 102) variable. Article headers are - cached and can be loaded from file when newsgroup entered instead loading from - newsserver. + If compiled with ``--enable-nntp'' option, Mutt-ng can read news from + newsserver via NNTP. You can open a newsgroup with function ``change-news- + group'' (default: i). Default newsserver can be obtained from _N_N_T_P_S_E_R_V_E_R envi- + ronment variable. Like other news readers, info about subscribed newsgroups is + saved in file by _$_n_n_t_p___n_e_w_s_r_c (section 6.3.156 , page 103) variable. Article + headers are cached and can be loaded from file when newsgroup entered instead + loading from newsserver. _3_. _C_o_n_f_i_g_u_r_a_t_i_o_n While the default configuration (or ``preferences'') make Mutt-ng usable right - out of the box, it is often desirable to tailor Mutt to suit your own tastes. - When Mutt-ng is first invoked, it will attempt to read the ``system'' configu- - ration file (defaults set by your local system administrator), unless the - ``-n'' _c_o_m_m_a_n_d _l_i_n_e (section 6.1 , page 62) option is specified. This file is - typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng users will - find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc. Mutt will - next look for a file named .muttrc in your home directory, Mutt-ng will look - for .muttngrc. If this file does not exist and your home directory has a + out of the box, it is often desirable to tailor Mutt-ng to suit your own + tastes. When Mutt-ng is first invoked, it will attempt to read the ``system'' + configuration file (defaults set by your local system administrator), unless + the ``-n'' _c_o_m_m_a_n_d _l_i_n_e (section 6.1 , page 62) option is specified. This + file is typically /usr/local/share/muttng/Muttngrc or /etc/Muttngrc, Mutt-ng + users will find this file in /usr/local/share/muttng/Muttrc or /etc/Muttngrc. + Mutt will next look for a file named .muttrc in your home directory, Mutt-ng The Mutt-ng E-Mail Client 15 - subdirectory named .mutt, mutt try to load a file named .muttng/muttngrc. + will look for .muttngrc. If this file does not exist and your home directory + has a subdirectory named .mutt, mutt try to load a file named .muttng/muttngrc. .muttrc (or .muttngrc for Mutt-ng) is the file where you will usually place - your _c_o_m_m_a_n_d_s (section 6.2 , page 62) to configure Mutt. + your _c_o_m_m_a_n_d_s (section 6.2 , page 62) to configure Mutt-ng. 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 configuration directory, and you are run- - ning version 0.88 of mutt, this file will be sourced instead of the Muttrc + ning version 0.88 of mutt, this file will be sourced instead of the Muttngrc file. The same is true of the user configuration file, if you have a file .muttrc-0.88.6 in your home directory, when you run mutt version 0.88.6, it will source this file instead of the default .muttrc file. The version number @@ -759,7 +760,7 @@ 62). Each line of the file may contain one or more commands. When multiple commands are used, they must be separated by a semicolon (;). - set realname='Mutt user' ; ignore x- + set realname='Mutt-ng user' ; ignore x- The hash mark, or pound sign (``#''), is used as a ``comment'' character. You can use it to annotate your initialization file. All text after the comment @@ -787,10 +788,9 @@ A \ at the end of a line can be used to split commands over multiple lines, provided that the split points don't appear in the middle of command names. - Please note that, unlike the various shells, mutt-ng interprets a ``\'' at the - The Mutt-ng E-Mail Client 16 + Please note that, unlike the various shells, mutt-ng interprets a ``\'' at the end of a line also in comments. This allows you to disable a command split over multiple lines with only one ``#''. @@ -838,11 +838,10 @@ Usage: alias _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ] - It's usually very cumbersome to remember or type out the address of someone you - The Mutt-ng E-Mail Client 17 - are communicating with. Mutt allows you to create ``aliases'' which map a + It's usually very cumbersome to remember or type out the address of someone you + are communicating with. Mutt-ng allows you to create ``aliases'' which map a short string to a full address. NNoottee:: if you want to create an alias for a group (by specifying more than one @@ -855,28 +854,28 @@ alias muttdude me@cs.hmc.edu (Michael Elkins) alias theguys manny, moe, jack - Unlike other mailers, Mutt doesn't require aliases to be defined in a special - file. The alias command can appear anywhere in a configuration file, as long - as this file is _s_o_u_r_c_e_d (section 3.26 , page 32). Consequently, you can have - multiple alias files, or you can have all aliases defined in your muttrc. + Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a spe- + cial file. The alias command can appear anywhere in a configuration file, as + long as this file is _s_o_u_r_c_e_d (section 3.26 , page 32). Consequently, you can + have multiple alias files, or you can have all aliases defined in your muttrc. On the other hand, the _c_r_e_a_t_e_-_a_l_i_a_s (section 2.3.4 , page 7) function can use only one file, the one pointed to by the _$_a_l_i_a_s___f_i_l_e (section 6.3.3 , page 65) variable (which is ~/.muttrc by default). This file is not special either, in - the sense that Mutt will happily append aliases to any file, but in order for - the new aliases to take effect you need to explicitly _s_o_u_r_c_e (section 3.26 , - page 32) this file too. + the sense that Mutt-ng will happily append aliases to any file, but in order + for the new aliases to take effect you need to explicitly _s_o_u_r_c_e (section + 3.26 , page 32) this file too. For example: - source /usr/local/share/Mutt.aliases + source /usr/local/share/Mutt-ng.aliases source ~/.mail_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 _T_o_: or _C_c_: prompt. You can also enter aliases in your editor at the appropriate headers if you have the _$_e_d_i_t___h_e_a_d_e_r_s - (section 6.3.56 , page 77) variable set. + (section 6.3.54 , page 77) variable set. In addition, at the various address prompts, you can use the tab character to expand a partial alias to the full alias. If there are multiple matches, mutt @@ -904,7 +903,7 @@ generic 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 use in + defined in another menu, Mutt-ng will look for a binding to use in this menu. This allows you to bind a key to a certain function in multiple menus instead of having multiple bind statements to accom- plish the same task. @@ -957,6 +956,7 @@ \t tab tab + backtab / shift-tab \r carriage return \n newline \e escape @@ -981,7 +981,7 @@ _k_e_y does not need to be enclosed in quotes unless it contains a space (`` ''). _f_u_n_c_t_i_o_n specifies which action to take when _k_e_y is pressed. For a complete - list of functions, see the _r_e_f_e_r_e_n_c_e (section 6.4 , page 146). The special + list of functions, see the _r_e_f_e_r_e_n_c_e (section 6.4 , page 147). The special function noop unbinds the specified key sequence. _3_._4 _D_e_f_i_n_i_n_g _a_l_i_a_s_e_s _f_o_r _c_h_a_r_a_c_t_e_r _s_e_t_s @@ -1000,18 +1000,18 @@ _3_._5 _S_e_t_t_i_n_g _v_a_r_i_a_b_l_e_s _b_a_s_e_d _u_p_o_n _m_a_i_l_b_o_x - Usage: folder-hook [!]_r_e_g_e_x_p _c_o_m_m_a_n_d - The Mutt-ng E-Mail Client 20 + Usage: folder-hook [!]_r_e_g_e_x_p _c_o_m_m_a_n_d + It is often desirable to change settings based on which mailbox you are read- ing. The folder-hook command provides a method by which you can execute any configuration command. _r_e_g_e_x_p is a regular expression specifying in which mailboxes to execute _c_o_m_m_a_n_d before loading. If a mailbox matches multiple folder-hook's, they are executed in the order given in the muttrc. - NNoottee:: if you use the ``!'' shortcut for _$_s_p_o_o_l_f_i_l_e (section 6.3.291 , page - 135) at the beginning of the pattern, you must place it inside of double or + NNoottee:: if you use the ``!'' shortcut for _$_s_p_o_o_l_f_i_l_e (section 6.3.295 , page + 136) at the beginning of the pattern, you must place it inside of double or single quotes in order to distinguish it from the logical _n_o_t operator for the expression. @@ -1031,9 +1031,9 @@ Usage: macro _m_e_n_u _k_e_y _s_e_q_u_e_n_c_e [ _d_e_s_c_r_i_p_t_i_o_n ] Macros are useful when you would like a single key to perform a series of - actions. When you press _k_e_y in menu _m_e_n_u, Mutt will behave as if you had typed - _s_e_q_u_e_n_c_e. So if you have a common sequence of commands you type, you can cre- - ate a macro to execute those commands with a single key. + actions. When you press _k_e_y in menu _m_e_n_u, Mutt-ng will behave as if you had + typed _s_e_q_u_e_n_c_e. So if you have a common sequence of commands you type, you can + create a macro to execute those commands with a single key. _m_e_n_u is the _m_a_p (section 3.3 , page 17) which the macro will be bound. Multi- ple maps may be specified by separating multiple menu arguments by commas. @@ -1047,16 +1047,17 @@ invoke a function directly, you can use the format _<_k_e_y _n_a_m_e_> and _<_f_u_n_c_t_i_o_n _n_a_m_e_>. For a listing of key names see the section on _k_e_y _b_i_n_d_i_n_g_s (section 3.3 , page 17). Functions are listed in the _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section - 6.4 , page 146). + 6.4 , page 147). The advantage with using function names directly is that the macros will work regardless of the current key bindings, so they are not dependent on the user having particular key definitions. This makes them more robust and portable, - and also facilitates defining of macros in files used by more than one user - (eg. the system Muttrc). The Mutt-ng E-Mail Client 21 + and also facilitates defining of macros in files used by more than one user + (eg. the system Muttngrc). + Optionally you can specify a descriptive text after _s_e_q_u_e_n_c_e, which is shown in the help screens. @@ -1071,7 +1072,7 @@ Usage: uncolor index _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] - If your terminal supports color, you can spice up Mutt by creating your own + If your terminal supports color, you can spice up Mutt-ng by creating your own color scheme. To define the color of an object (type of information), you must specify both a foreground color aanndd a background color (it is not possible to only specify one or the other). @@ -1084,7 +1085,7 @@ +o bold (highlighting bold patterns in the body of messages) - +o error (error messages printed by Mutt) + +o error (error messages printed by Mutt-ng) +o header (match _r_e_g_e_x_p in the message header) @@ -1100,19 +1101,19 @@ +o normal - +o quoted (text matching _$_q_u_o_t_e___r_e_g_e_x_p (section 6.3.218 , page 118) in the + +o quoted (text matching _$_q_u_o_t_e___r_e_g_e_x_p (section 6.3.225 , page 119) in the body of a message) +o quoted1, quoted2, ..., quotedNN (higher levels of quoting) +o search (highlighting of words in the pager) + The Mutt-ng E-Mail Client 22 + +o signature +o status (mode lines used to display info about the mailbox or message) - The Mutt-ng E-Mail Client 22 - +o tilde (the ``~'' used to pad blank lines in the pager) +o tree (thread tree drawn in the message index and attachment menu) @@ -1145,10 +1146,10 @@ ground color boldfaced (e.g., brightred). If your terminal supports it, the special keyword _d_e_f_a_u_l_t can be used as a - transparent color. The value _b_r_i_g_h_t_d_e_f_a_u_l_t is also valid. If Mutt is linked - against the _S_-_L_a_n_g library, you also need to set the _C_O_L_O_R_F_G_B_G environment - variable to the default colors of your terminal for this to work; for example - (for Bourne-like shells): + transparent color. The value _b_r_i_g_h_t_d_e_f_a_u_l_t is also valid. If Mutt-ng is + linked against the _S_-_L_a_n_g library, you also need to set the _C_O_L_O_R_F_G_B_G environ- + ment variable to the default colors of your terminal for this to work; for + example (for Bourne-like shells): set COLORFGBG="green;black" export COLORFGBG @@ -1161,13 +1162,13 @@ 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 _c_o_l_o_r_0, _c_o_l_o_r_1, ..., _c_o_l_o_rNN--11 (NN being the + The Mutt-ng E-Mail Client 23 + + Mutt-ng also recognizes the keywords _c_o_l_o_r_0, _c_o_l_o_r_1, ..., _c_o_l_o_rNN--11 (NN 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 _c_o_l_o_r_2 for your xterm), since color names may then lose their normal meaning. - The Mutt-ng E-Mail Client 23 - If your terminal does not support color, it is still possible change the video attributes through the use of the ``mono'' command: @@ -1202,8 +1203,9 @@ tent-''. ``ignore *'' will ignore all headers. To remove a previously added token from the list, use the ``unignore'' command. - The ``unignore'' command will make Mutt display headers with the given pattern. - For example, if you do ``ignore x-'' it is possible to ``unignore x-mailer''. + The ``unignore'' command will make Mutt-ng display headers with the given pat- + tern. For example, if you do ``ignore x-'' it is possible to ``unignore x- + mailer''. ``unignore *'' will remove all tokens from the ignore list. @@ -1215,19 +1217,18 @@ unignore organization organisation x-mailer: x-newsreader: x-mailing-list: unignore posted-to: + The Mutt-ng E-Mail Client 24 + _3_._9 _A_l_t_e_r_n_a_t_i_v_e _a_d_d_r_e_s_s_e_s Usage: [un]alternates _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] With various functions, mutt will treat messages differently, depending on whether you sent them or whether you received them from someone else. For - - The Mutt-ng E-Mail Client 24 - instance, when replying to a message that you sent to a different party, mutt will automatically suggest to send the response to the original message's recipients -- responding to yourself won't make much sense in many cases. (See - _$_r_e_p_l_y___t_o (section 6.3.226 , page 119).) + _$_r_e_p_l_y___t_o (section 6.3.233 , page 121).) Many users receive e-mail under a number of different addresses. To fully use mutt's features here, the program must be able to recognize what e-mail @@ -1252,7 +1253,7 @@ Usage: [un]subscribe _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] - Mutt has a few nice features for _h_a_n_d_l_i_n_g _m_a_i_l_i_n_g _l_i_s_t_s (section 4.9 , page + Mutt-ng has a few nice features for _h_a_n_d_l_i_n_g _m_a_i_l_i_n_g _l_i_s_t_s (section 4.9 , page 44). In order to take advantage of them, you must specify which addresses belong to mailing lists, and which mailing lists you are subscribed to. Once you have done this, the _l_i_s_t_-_r_e_p_l_y (section 2.3.4 , page 8) function will work @@ -1262,25 +1263,25 @@ Mail-Followup-To header is a non-standard extension which is not supported by all mail user agents. Adding it is not bullet-proof against receiving personal CCs of list messages. Also note that the generation of the Mail-Followup-To - header is controlled by the _$_f_o_l_l_o_w_u_p___t_o (section 6.3.67 , page 80) configura- + header is controlled by the _$_f_o_l_l_o_w_u_p___t_o (section 6.3.66 , page 80) configura- tion variable. - More precisely, Mutt maintains lists of patterns for the addresses of known and - subscribed mailing lists. Every subscribed mailing list is known. To mark a - mailing list as known, use the ``lists'' command. To mark it as subscribed, + More precisely, Mutt-ng maintains lists of patterns for the addresses of known + and subscribed mailing lists. Every subscribed mailing list is known. To mark + a mailing list as known, use the ``lists'' command. To mark it as subscribed, use ``subscribe''. You can use regular expressions with both commands. To mark all messages sent to a specific bug report's address on mutt's bug tracking system as list mail, + + The Mutt-ng E-Mail Client 25 + for instance, you could say ``subscribe [0-9]*@bugs.guug.de''. Often, it's sufficient to just give a portion of the list's e-mail address. Specify as much of the address as you need to to remove ambiguity. For exam- - ple, if you've subscribed to the Mutt mailing list, you will receive mail - addressed to _m_u_t_t_-_u_s_e_r_s_@_m_u_t_t_._o_r_g. So, to tell Mutt that this is a mailing - - The Mutt-ng E-Mail Client 25 - + ple, if you've subscribed to the Mutt-ng mailing list, you will receive mail + addressed to _m_u_t_t_-_u_s_e_r_s_@_m_u_t_t_._o_r_g. So, to tell Mutt-ng 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 ini- tialization file instead. If you also happen to get mail from someone whose @@ -1318,25 +1319,25 @@ Pressing TAB in the directory browser will bring up a menu showing the files specified by the mailboxes command, and indicate which contain new messages. - Mutt will automatically enter this mode when invoked from the command line with - the -y option. + Mutt-ng will automatically enter this mode when invoked from the command line + with the -y option. The ``unmailboxes'' command is used to remove a token from the list of folders which receive mail. Use ``unmailboxes *'' to remove all tokens. NNoottee:: new 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. + the mailbox might cause Mutt-ng 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. + + The Mutt-ng E-Mail Client 26 NNoottee:: the filenames in the mailboxes command are resolved when the command is executed, so if these names contain _s_h_o_r_t_c_u_t _c_h_a_r_a_c_t_e_r_s (section 4.8 , page 44) (such as ``='' and ``!''), any variable definition that affect these char- - acters (like _$_f_o_l_d_e_r (section 6.3.65 , page 79) and _$_s_p_o_o_l_f_i_l_e (section - 6.3.291 , page 135)) should be executed before the mailboxes command. - - The Mutt-ng E-Mail Client 26 + acters (like _$_f_o_l_d_e_r (section 6.3.64 , page 79) and _$_s_p_o_o_l_f_i_l_e (section + 6.3.295 , page 136)) should be executed before the mailboxes command. _3_._1_3 _U_s_e_r _d_e_f_i_n_e_d _h_e_a_d_e_r_s @@ -1358,10 +1359,10 @@ NNoottee:: space characters are _n_o_t allowed between the keyword and the colon (``:''). The standard for electronic mail (RFC822) says that space is illegal - there, so Mutt enforces the rule. + there, so Mutt-ng enforces the rule. If you would like to add a header field to a single message, you should either - set the _e_d_i_t___h_e_a_d_e_r_s (section 6.3.56 , page 77) variable, or use the _e_d_i_t_- + set the _e_d_i_t___h_e_a_d_e_r_s (section 6.3.54 , page 77) variable, or use the _e_d_i_t_- _h_e_a_d_e_r_s function (default: ``E'') in the send-menu so that you can edit the header of your message along with the body. @@ -1382,12 +1383,12 @@ ``unhdr_order *'' will clear all previous headers from the order list, thus removing the header order effects set by the system-wide startup file. + The Mutt-ng E-Mail Client 27 + hdr_order From Date: From: To: Cc: Subject: _3_._1_5 _S_p_e_c_i_f_y _d_e_f_a_u_l_t _s_a_v_e _f_i_l_e_n_a_m_e - The Mutt-ng E-Mail Client 27 - Usage: save-hook [!]_p_a_t_t_e_r_n _f_i_l_e_n_a_m_e This command is used to override the default filename used when saving mes- @@ -1410,10 +1411,10 @@ Usage: fcc-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x This command is used to save outgoing mail in a mailbox other than _$_r_e_c_o_r_d - (section 6.3.223 , page 119). Mutt searches the initial list of message + (section 6.3.230 , page 120). Mutt-ng searches the initial list of message recipients for the first matching _r_e_g_e_x_p and uses _m_a_i_l_b_o_x as the default Fcc: mailbox. If no match is found the message will be saved to _$_r_e_c_o_r_d (section - 6.3.223 , page 119) mailbox. + 6.3.230 , page 120) mailbox. See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.4.1 , page 41) for information on the exact format of _p_a_t_t_e_r_n. @@ -1435,14 +1436,13 @@ Usage: reply-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d + The Mutt-ng E-Mail Client 28 + Usage: send-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d Usage: send2-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d These commands can be used to execute arbitrary configuration commands based - - The Mutt-ng E-Mail Client 28 - upon recipients of the message. _p_a_t_t_e_r_n is a regular expression matching the desired address. _c_o_m_m_a_n_d is executed when _r_e_g_e_x_p matches recipients of the message. @@ -1455,7 +1455,7 @@ 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 - _$_s_e_n_d_m_a_i_l (section 6.3.241 , page 123) variable depending on the message's + _$_s_e_n_d_m_a_i_l (section 6.3.247 , page 124) variable depending on the message's sender address. For each type of send-hook or reply-hook, when multiple matches occur, commands @@ -1468,8 +1468,8 @@ Example: send-hook mutt 'set mime_forward signature=''' Another typical use for this command is to change the values of the _$_a_t_t_r_i_b_u_- - _t_i_o_n (section 6.3.17 , page 69), _$_s_i_g_n_a_t_u_r_e (section 6.3.255 , page 126) and - _$_l_o_c_a_l_e (section 6.3.117 , page 94) variables in order to change the language + _t_i_o_n (section 6.3.15 , page 68), _$_s_i_g_n_a_t_u_r_e (section 6.3.259 , page 127) and + _$_l_o_c_a_l_e (section 6.3.114 , page 93) variables in order to change the language of the attributions and signatures based upon the recipients. NNoottee:: the send-hook's are only executed ONCE after getting the initial list of @@ -1493,11 +1493,11 @@ Example: + The Mutt-ng E-Mail Client 29 + message-hook ~A 'set pager=builtin' message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""' - The Mutt-ng E-Mail Client 29 - _3_._2_0 _C_h_o_o_s_i_n_g _t_h_e _c_r_y_p_t_o_g_r_a_p_h_i_c _k_e_y _o_f _t_h_e _r_e_c_i_p_i_e_n_t Usage: crypt-hook _p_a_t_t_e_r_n _k_e_y_i_d @@ -1505,9 +1505,9 @@ When encrypting messages with PGP or OpenSSL, you may want to associate a cer- tain key with a given e-mail address automatically, either because the recipi- ent's public key can't be deduced from the destination address, or because, for - some reasons, you need to override the key Mutt would normally use. The crypt- - hook command provides a method by which you can specify the ID of the public - key to be used when encrypting messages to a certain recipient. + some reasons, you need to override the key Mutt-ng would normally use. The + crypt-hook command provides a method by which you can specify the ID of the + public key to be used when encrypting messages to a certain recipient. The meaning of "key id" is to be taken broadly in this context: You can either put a numerical key ID here, an e-mail address, or even just a real name. @@ -1526,7 +1526,7 @@ Usage: exec _f_u_n_c_t_i_o_n [ _f_u_n_c_t_i_o_n ... ] This command can be used to execute any function. Functions are listed in the - _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section 6.4 , page 146). ``exec function'' is equivalent + _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section 6.4 , page 147). ``exec function'' is equivalent to ``push ''. _3_._2_3 _M_e_s_s_a_g_e _S_c_o_r_i_n_g @@ -1548,19 +1548,19 @@ 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. + The Mutt-ng E-Mail Client 30 + _3_._2_4 _S_p_a_m _d_e_t_e_c_t_i_o_n Usage: spam _p_a_t_t_e_r_n _f_o_r_m_a_t - The Mutt-ng E-Mail Client 30 - Usage: nospam _p_a_t_t_e_r_n - Mutt has generalized support for external spam-scoring filters. By defining + Mutt-ng has generalized support for external spam-scoring filters. By defining your spam patterns with the spam and nospam commands, you can _l_i_m_i_t, _s_e_a_r_c_h, and _s_o_r_t 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 _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.112 , page 91) variable. + the %H selector in the _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.110 , page 90) variable. (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a given message.) @@ -1604,12 +1604,12 @@ expression matches against for _s_e_a_r_c_h and _l_i_m_i_t functions. And it's what sort- ing by spam attribute will use as a sort key. + The Mutt-ng E-Mail Client 31 + 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. - The Mutt-ng E-Mail Client 31 - Generally, when you sort by spam tag, mutt will sort _l_e_x_i_c_a_l_l_y -- 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 @@ -1651,7 +1651,7 @@ Usage: reset _v_a_r_i_a_b_l_e [_v_a_r_i_a_b_l_e ... ] This command is used to set (and unset) _c_o_n_f_i_g_u_r_a_t_i_o_n _v_a_r_i_a_b_l_e_s (section 6.3 , - page 64). There are four basic types of variables: boolean, number, string and + page 65). There are four basic types of variables: boolean, number, string and quadoption. _b_o_o_l_e_a_n variables can be _s_e_t (true) or _u_n_s_e_t (false). _n_u_m_b_e_r variables can be assigned a positive integer value. @@ -1659,14 +1659,13 @@ be enclosed in quotes if they contain spaces or tabs. You may also use the ``C'' escape sequences \\nn and \\tt for newline and tab, respectively. - _q_u_a_d_o_p_t_i_o_n variables are used to control whether or not to be prompted for cer- - tain actions, or to specify a default action. A value of _y_e_s will cause the - action to be carried out automatically as if you had answered yes to the - The Mutt-ng E-Mail Client 32 - question. Similarly, a value of _n_o will cause the the action to be carried out - as if you had answered ``no.'' A value of _a_s_k_-_y_e_s will cause a prompt with a + _q_u_a_d_o_p_t_i_o_n variables are used to control whether or not to be prompted for cer- + tain actions, or to specify a default action. A value of _y_e_s will cause the + action to be carried out automatically as if you had answered yes to the ques- + tion. Similarly, a value of _n_o will cause the the action to be carried out as + if you had answered ``no.'' A value of _a_s_k_-_y_e_s will cause a prompt with a default answer of ``yes'' and _a_s_k_-_n_o will provide a default answer of ``no.'' Prefixing a variable with ``no'' will unset it. Example: set noaskbcc. @@ -1712,26 +1711,29 @@ _3_._2_7 _C_o_n_f_i_g_u_r_i_n_g _f_e_a_t_u_r_e_s _c_o_n_d_i_t_i_o_n_a_l_l_y - Usage: ifdef _i_t_e_m _c_o_m_m_a_n_d Usage: ifndef _i_t_e_m _c_o_m_m_a_n_d - - These command allows to test if a variable, function or certain feature is - available or not respectively, before actually executing the command. ifdef - (short for ``if defined) handles commands if upon availability while ifndef + Usage: ifdef _i_t_e_m _c_o_m_m_a_n_d The Mutt-ng E-Mail Client 33 - (short for ``if not defined'') does if not. The _c_o_m_m_a_n_d may be any valid frac- - tion of a configuration file. + Usage: ifndef _i_t_e_m _c_o_m_m_a_n_d + + These commands allow testing for a variable, function or certain feature being + available or not respectively, before actually executing the command given. - All names of variables and functions may be tested. Additionally, the following - compile-features may be tested when prefixed with 'feature_': ncurses, slang, - iconv, idn, dotlock, standalone, pop, nntp, imap, ssl, gnutls, sasl, sasl2, - libesmtp, compressed, color, classic_pgp, classic_smime, gpgme, header_cache. + ifdef (short for ``if defined'') only executes the command upon availability + while ifndef (short for ``if not defined'') does if not. The _c_o_m_m_a_n_d may be any + valid fraction of a configuration file. + + All names of variables, functions and menus may be tested. Additionally, the + following compile-features may be tested when prefixed with 'feature_': + ncurses, slang, iconv, idn, dotlock, standalone, pop, nntp, imap, ssl, gnutls, + sasl, sasl2, libesmtp, compressed, color, classic_pgp, classic_smime, gpgme, + header_cache, gdbm, qdbm and db4. Examples follow. - To only source a file with IMAP related settings only if IMAP support is com- - piled in, use: + To only source a file with IMAP related settings if IMAP support is compiled + in, use: ifdef feature_imap 'source ~/.mutt-ng/imap_setup' # or @@ -1747,10 +1749,10 @@ # or # ... - To only set the _<_$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 6.3.101 , page 88) when the sys- - tem's SVN is recent enough to have it: + To only set the _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 6.3.99 , page 88) variable if the + system's mutt-ng is aware of it, use: - ifdef imap_mail_check 'set imap_mail_check=300' + ifdef imap_mail_check 'set imap_mail_check=500' _3_._2_8 _R_e_m_o_v_i_n_g _h_o_o_k_s @@ -1763,15 +1765,15 @@ _4_. _A_d_v_a_n_c_e_d _U_s_a_g_e - _4_._1 _R_e_g_u_l_a_r _E_x_p_r_e_s_s_i_o_n_s + The Mutt-ng E-Mail Client 34 - All string patterns in Mutt including those in more complex _p_a_t_t_e_r_n_s (section - 4.2 , page 36) must be specified using regular expressions (regexp) in the - ``POSIX extended'' syntax (which is more or less the syntax used by egrep and - GNU awk). For your convenience, we have included below a brief description of - this syntax. + _4_._1 _R_e_g_u_l_a_r _E_x_p_r_e_s_s_i_o_n_s - The Mutt-ng E-Mail Client 34 + All string patterns in Mutt-ng including those in more complex _p_a_t_t_e_r_n_s (sec- + tion 4.2 , page 36) must be specified using regular expressions (regexp) in + the ``POSIX extended'' syntax (which is more or less the syntax used by egrep + and GNU awk). For your convenience, we have included below a brief description + of this syntax. The search is case sensitive if the pattern contains at least one upper case letter, and case insensitive otherwise. Note that ``\'' must be quoted if used @@ -1819,6 +1821,8 @@ [:blank:] Space or tab characters. + The Mutt-ng E-Mail Client 35 + [:cntrl:] Control characters. @@ -1826,11 +1830,8 @@ Numeric characters. [:graph:] - Characters that are both printable and visible. (A space is - - The Mutt-ng E-Mail Client 35 - - printable, but not visible, while an ``a'' is both.) + Characters that are both printable and visible. (A space is print- + able, but not visible, while an ``a'' is both.) [:lower:] Lower-case alphabetic characters. @@ -1877,14 +1878,14 @@ A regular expression matching a single character may be followed by one of sev- eral repetition operators: + The Mutt-ng E-Mail Client 36 + ? The preceding item is optional and matched at most once. * The preceding item will be matched zero or more times. - The Mutt-ng E-Mail Client 36 - + The preceding item will be matched one or more times. @@ -1912,8 +1913,8 @@ over alternation. A whole subexpression may be enclosed in parentheses to override these precedence rules. - NNoottee:: If you compile Mutt with the GNU _r_x package, the following operators may - also be used in regular expressions: + NNoottee:: If you compile Mutt-ng with the GNU _r_x package, the following operators + may also be used in regular expressions: \\y Matches the empty string at either the beginning or the end of a @@ -1932,14 +1933,14 @@ Matches any word-constituent character (letter, digit, or under- score). + The Mutt-ng E-Mail Client 37 + \\W Matches any character that is not word-constituent. \\` Matches the empty string at the beginning of a buffer (string). - The Mutt-ng E-Mail Client 37 - \\' Matches the empty string at the end of a buffer. @@ -1948,9 +1949,11 @@ _4_._2 _P_a_t_t_e_r_n_s - Many of Mutt's commands allow you to specify a pattern to match (limit, tag- + Many of Mutt-ng's commands allow you to specify a pattern to match (limit, tag- pattern, delete-pattern, etc.). There are several ways to select messages: + The Mutt-ng E-Mail Client 38 + ~A all messages ~b EXPR messages which contain EXPR in the message body ~B EXPR messages which contain EXPR in the whole message @@ -1966,7 +1969,7 @@ ~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 + ~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 @@ -1984,26 +1987,27 @@ ~T tagged messages ~t USER messages addressed to USER ~U unread messages - ~v message is part of a collapsed thread. - ~V cryptographically verified messages + ~v message is part of a collapsed thread. + ~V cryptographically verified messages + ~w EXPR messages which contain EXPR in the `Newsgroups' field + (if compiled with NNTP support) ~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) - ~* ``From'' contains realname and (syntactically) valid - address (excluded are addresses matching against - - The Mutt-ng E-Mail Client 38 - - alternates or any alias) + ~= duplicated messages (see $duplicate_threads) + ~$ unreferenced messages (requires threaded view) + ~* ``From'' contains realname and (syntactically) valid + address (excluded are addresses matching against + alternates or any alias) Where EXPR, USER, ID, and SUBJECT are _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n_s (section 4.1 , page 33). Special attention has to be made when using regular expressions inside of - patterns. Specifically, Mutt's parser for these patterns will strip one level - of backslash (\), which is normally used for quoting. If it is your intention - to use a backslash in the regular expression, you will need to use two back- - slashes instead (\\). + patterns. Specifically, Mutt-ng's parser for these patterns will strip one + level of backslash (\), which is normally used for quoting. If it is your + intention to use a backslash in the regular expression, you will need to use + two backslashes instead (\\). + + The Mutt-ng E-Mail Client 39 *) The forms <[MAX], >[MIN], [MIN]- and -[MAX] are allowed, too. @@ -2025,8 +2029,8 @@ would select messages which contain the word ``mutt'' in the list of recipients aanndd that have the word ``elkins'' in the ``From'' header field. - Mutt also recognizes the following operators to create more complex search pat- - terns: + Mutt-ng also recognizes the following operators to create more complex search + patterns: +o ! -- logical NOT operator @@ -2042,19 +2046,18 @@ Here is an example using white space in the regular expression (note the ' and ' delimiters). For this to match, the mail's subject must match the ``^Junk - +From +Me$'' and it must be from either ``Jim +Somebody'' or ``Ed - - The Mutt-ng E-Mail Client 39 - - +SomeoneElse'': + +From +Me$'' and it must be from either ``Jim +Somebody'' or ``Ed +Some- + oneElse'': '~s "^Junk +From +Me$" ~f ("Jim +Somebody"|"Ed +SomeoneElse")' - Note that if a regular expression contains parenthesis, or a veritical bar + Note that if a regular expression contains parenthesis, or a vertical bar ("|"), you mmuusstt enclose the expression in double or single quotes since those - characters are also used to separate different parts of Mutt's pattern lan- + characters are also used to separate different parts of Mutt-ng's pattern lan- guage. For example, + The Mutt-ng E-Mail Client 40 + ~f "me@(mutt\.org|cs\.hmc\.edu)" Without the quotes, the parenthesis wouldn't end. This would be separated to @@ -2063,7 +2066,7 @@ _4_._2_._3 _S_e_a_r_c_h_i_n_g _b_y _D_a_t_e - Mutt supports two types of dates, _a_b_s_o_l_u_t_e and _r_e_l_a_t_i_v_e. + Mutt-ng supports two types of dates, _a_b_s_o_l_u_t_e and _r_e_l_a_t_i_v_e. AAbbssoolluuttee. Dates mmuusstt be in DD/MM/YY format (month and year are optional, defaulting to the current month and year). An example of a valid range of @@ -2092,8 +2095,6 @@ Example: To select any messages two weeks around January 15, 2001, you'd use the following pattern: - The Mutt-ng E-Mail Client 40 - Limit to messages matching: ~d 15/1/2001*2w RReellaattiivvee. This type of date is relative to the current date, and may be speci- @@ -2105,6 +2106,8 @@ +o =_o_f_f_s_e_t (messages exactly _o_f_f_s_e_t units old) + The Mutt-ng E-Mail Client 41 + _o_f_f_s_e_t is specified as a positive number with one of the following units: y years @@ -2117,8 +2120,8 @@ Limit to messages matching: ~d <1m NNoottee:: all dates used when searching are relative to the llooccaall time zone, so - unless you change the setting of your _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.112 , page - 91) to include a %[...] format, these are nnoott the dates shown in the main + unless you change the setting of your _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.110 , page + 90) to include a %[...] format, these are nnoott the dates shown in the main index. _4_._3 _U_s_i_n_g _T_a_g_s @@ -2129,35 +2132,35 @@ ject. To tag all messages matching a pattern, use the tag-pattern function, which is bound to ``shift-T'' by default. Or you can select individual mes- sages by hand using the ``tag-message'' function, which is bound to ``t'' by - default. See _p_a_t_t_e_r_n_s (section 4.2 , page 36) for Mutt's pattern matching + default. See _p_a_t_t_e_r_n_s (section 4.2 , page 36) for Mutt-ng's pattern matching syntax. Once you have tagged the desired messages, you can use the ``tag-prefix'' oper- ator, which is the ``;'' (semicolon) key by default. When the ``tag-prefix'' operator is used, the nneexxtt operation will be applied to all tagged messages if - that operation can be used in that manner. If the _$_a_u_t_o___t_a_g (section 6.3.18 , + that operation can be used in that manner. If the _$_a_u_t_o___t_a_g (section 6.3.16 , page 69) variable is set, the next operation applies to the tagged messages automatically, without requiring the ``tag-prefix''. In _m_a_c_r_o_s (section 3.6 , page 20) or _p_u_s_h (section 3.21 , page 29) 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. - - The Mutt-ng E-Mail Client 41 + mutt will "eat" the rest of the macro to abort it's execution. Mutt-ng 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. _4_._4 _U_s_i_n_g _H_o_o_k_s A _h_o_o_k 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 _h_o_o_k consists of a _r_e_g_u_l_a_r + whom you are sending mail. In the Mutt-ng world, a _h_o_o_k consists of a _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n (section 4.1 , page 33) or _p_a_t_t_e_r_n (section 4.2 , page 36) along with a configuration option/command. See +o _f_o_l_d_e_r_-_h_o_o_k (section 3.5 , page 19) + The Mutt-ng E-Mail Client 42 + +o _s_e_n_d_-_h_o_o_k (section 3.18 , page 27) +o _m_e_s_s_a_g_e_-_h_o_o_k (section 3.19 , page 28) @@ -2188,28 +2191,28 @@ messages a finer grain of control is needed for matching since for different purposes you want to match different criteria. - Mutt allows the use of the _s_e_a_r_c_h _p_a_t_t_e_r_n (section 4.2 , page 36) language for - matching messages in hook commands. This works in exactly the same way as it - would when _l_i_m_i_t_i_n_g or _s_e_a_r_c_h_i_n_g the mailbox, except that you are restricted to - those operators which match information mutt extracts from the header of the + Mutt-ng allows the use of the _s_e_a_r_c_h _p_a_t_t_e_r_n (section 4.2 , page 36) language + for matching messages in hook commands. This works in exactly the same way as + it would when _l_i_m_i_t_i_n_g or _s_e_a_r_c_h_i_n_g 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.). For example, if you wanted to set your return address based upon sending mail to a specific address, you could do something like: - send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User ' - - The Mutt-ng E-Mail Client 42 + send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User ' which would execute the given command when sending mail to _m_e_@_c_s_._h_m_c_._e_d_u. However, it is not required that you write the pattern to match using the full searching language. You can still specify a simple _r_e_g_u_l_a_r _e_x_p_r_e_s_s_i_o_n like the - other hooks, in which case Mutt will translate your pattern into the full lan- - guage, using the translation specified by the _$_d_e_f_a_u_l_t___h_o_o_k (section 6.3.47 , - page 75) variable. The pattern is translated at the time the hook is declared, - so the value of _$_d_e_f_a_u_l_t___h_o_o_k (section 6.3.47 , page 75) that is in effect at - that time will be used. + other hooks, in which case Mutt-ng will translate your pattern into the full + language, using the translation specified by the _$_d_e_f_a_u_l_t___h_o_o_k (section + 6.3.45 , page 75) variable. The pattern is translated at the time the hook is + declared, so the value of _$_d_e_f_a_u_l_t___h_o_o_k (section 6.3.45 , page 75) that is in + effect at that time will be used. + + The Mutt-ng E-Mail Client 43 _4_._5 _U_s_i_n_g _t_h_e _s_i_d_e_b_a_r @@ -2245,8 +2248,6 @@ Reasonable key bindings look e.g. like this: - The Mutt-ng E-Mail Client 43 - bind index \Cp sidebar-prev bind index \Cn sidebar-next bind index \Cb sidebar-open @@ -2262,10 +2263,12 @@ _4_._6 _E_x_t_e_r_n_a_l _A_d_d_r_e_s_s _Q_u_e_r_i_e_s - Mutt supports connecting to external directory databases such as LDAP, ph/qi, - bbdb, or NIS through a wrapper script which connects to mutt using a simple - interface. Using the _$_q_u_e_r_y___c_o_m_m_a_n_d (section 6.3.214 , page 117) variable, - you specify the wrapper command to use. For example: + The Mutt-ng E-Mail Client 44 + + Mutt-ng supports connecting to external directory databases such as LDAP, + ph/qi, bbdb, or NIS through a wrapper script which connects to mutt using a + simple interface. Using the _$_q_u_e_r_y___c_o_m_m_a_n_d (section 6.3.221 , page 118) vari- + able, you specify the wrapper command to use. For example: set query_command = "mutt_ldap_query.pl '%s'" @@ -2298,21 +2301,21 @@ will activate the query menu. At the query menu, you can select one or more addresses to be added to the prompt. - The Mutt-ng E-Mail Client 44 - _4_._7 _M_a_i_l_b_o_x _F_o_r_m_a_t_s - Mutt supports reading and writing of four different mailbox formats: mbox, + Mutt-ng supports reading and writing of four different mailbox formats: mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to - use a flag for different mailbox types. When creating new mailboxes, Mutt uses - the default specified with the _$_m_b_o_x___t_y_p_e (section 6.3.128 , page 96) vari- - able. + use a flag for different mailbox types. When creating new mailboxes, Mutt-ng + uses the default specified with the _$_m_b_o_x___t_y_p_e (section 6.3.125 , page 95) + variable. mmbbooxx. 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: From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST + The Mutt-ng E-Mail Client 45 + to denote the start of a new message (this is often referred to as the ``From_'' line). @@ -2321,7 +2324,7 @@ MMHH. A radical departure from _m_b_o_x and _M_M_D_F, a mailbox consists of a directory and each message is stored in a separate file. The filename indicates the mes- - sage number (however, this is may not correspond to the message number Mutt + sage number (however, this is may not correspond to the message number Mutt-ng displays). Deleted messages are renamed with a comma (,) prepended to the file- name. NNoottee:: Mutt detects this type of mailbox by looking for either .mh_sequences or .xmhcache (needed to distinguish normal directories from MH @@ -2339,12 +2342,12 @@ These shortcuts can be used anywhere you are prompted for a file or mailbox path. - +o ! -- refers to your _$_s_p_o_o_l_f_i_l_e (section 6.3.291 , page 135) (incoming) + +o ! -- refers to your _$_s_p_o_o_l_f_i_l_e (section 6.3.295 , page 136) (incoming) mailbox - +o > -- refers to your _$_m_b_o_x (section 6.3.127 , page 96) file + +o > -- refers to your _$_m_b_o_x (section 6.3.124 , page 95) file - +o < -- refers to your _$_r_e_c_o_r_d (section 6.3.223 , page 119) file + +o < -- refers to your _$_r_e_c_o_r_d (section 6.3.230 , page 120) file +o ^ -- refers to the current mailbox @@ -2352,27 +2355,28 @@ +o ~ -- refers to your home directory - The Mutt-ng E-Mail Client 45 - - +o = or + -- refers to your _$_f_o_l_d_e_r (section 6.3.65 , page 79) directory + +o = or + -- refers to your _$_f_o_l_d_e_r (section 6.3.64 , page 79) directory +o @_a_l_i_a_s -- refers to the _d_e_f_a_u_l_t _s_a_v_e _f_o_l_d_e_r (section 3.15 , page 26) as determined by the address of the alias _4_._9 _H_a_n_d_l_i_n_g _M_a_i_l_i_n_g _L_i_s_t_s - Mutt has a few configuration options that make dealing with large amounts of + Mutt-ng has a few configuration options that make dealing with large amounts of mail easier. The first thing you must do is to let Mutt know what addresses you consider to be mailing lists (technically this does not have to be a mail- ing list, but that is what it is most often used for), and what lists you are subscribed to. This is accomplished through the use of the _l_i_s_t_s _a_n_d _s_u_b_s_c_r_i_b_e (section 3.10 , page 24) commands in your muttrc. - 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 + Now that Mutt-ng knows what your mailing lists are, it can do several things, + + The Mutt-ng E-Mail Client 46 + + 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 _i_n_d_e_x menu display. This is useful to distinguish between personal and list mail in the same mail- - box. In the _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.112 , page 91) variable, the escape + box. In the _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.110 , page 90) variable, the escape ``%L'' will return the string ``To '' when ``list'' appears in the ``To'' field, and ``Cc '' when it appears in the ``Cc'' field (otherwise it returns the name of the author). @@ -2385,34 +2389,32 @@ mailing list addresses instead of all recipients (except as specified by Mail- Followup-To, see below). - Mutt also supports the Mail-Followup-To header. When you send a message to a - list of recipients which includes one or several subscribed mailing lists, and - if the _$_f_o_l_l_o_w_u_p___t_o (section 6.3.67 , page 80) option is set, mutt will gener- - ate a Mail-Followup-To header which contains all the recipients to whom you - send this message, but not your address. This indicates that group-replies or - list-replies (also known as ``followups'') to this message should only be sent - to the original recipients of the message, and not separately to you - you'll - receive your copy through one of the mailing lists you are subscribed to. + Mutt-ng also supports the Mail-Followup-To header. When you send a message to + a list of recipients which includes one or several subscribed mailing lists, + and if the _$_f_o_l_l_o_w_u_p___t_o (section 6.3.66 , page 80) option is set, mutt will + generate a Mail-Followup-To header which contains all the recipients to whom + you send this message, but not your address. This indicates that group-replies + or list-replies (also known as ``followups'') to this message should only be + sent to the original recipients of the message, and not separately to you - + you'll receive your copy through one of the mailing lists you are subscribed + to. Conversely, when group-replying or list-replying to a message which has a Mail- Followup-To header, mutt will respect this header if the _$_h_o_n_o_r___f_o_l_l_o_w_u_p___t_o - (section 6.3.91 , page 86) configuration variable is set. Using list-reply + (section 6.3.88 , page 85) configuration variable is set. Using list-reply will in this case also make sure that the reply goes to the mailing list, even if it's not specified in the list of recipients in the Mail-Followup-To. Note that, when header editing is enabled, you can create a Mail-Followup-To - header manually. Mutt will only auto-generate this header if it doesn't exist - when you send the message. + header manually. Mutt-ng will only auto-generate this header if it doesn't + exist when you send the message. The other method some mailing list admins use is to generate a ``Reply-To'' field which points back to the mailing list address rather than the author of the message. This can create problems when trying to reply directly to the author in private, since most mail clients will automatically reply to the - - The Mutt-ng E-Mail Client 46 - - address given in the ``Reply-To'' field. Mutt uses the _$_r_e_p_l_y___t_o (section - 6.3.226 , page 119) variable to help decide which address to use. If set to + address given in the ``Reply-To'' field. Mutt-ng uses the _$_r_e_p_l_y___t_o (section + 6.3.233 , page 121) variable to help decide which address to use. If set to _a_s_k_-_y_e_s or _a_s_k_-_n_o, you will be prompted as to whether or not you would like to use the address given in the ``Reply-To'' field, or reply directly to the address given in the ``From'' field. When set to _y_e_s, the ``Reply-To'' field @@ -2420,32 +2422,34 @@ The ``X-Label:'' header field can be used to further identify mailing lists or list subject matter (or just to annotate messages individually). The - _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.112 , page 91) variable's ``%y'' and ``%Y'' escapes - can be used to expand ``X-Label:'' fields in the index, and Mutt's pattern- + _$_i_n_d_e_x___f_o_r_m_a_t (section 6.3.110 , page 90) variable's ``%y'' and ``%Y'' escapes + can be used to expand ``X-Label:'' fields in the index, and Mutt-ng's pattern- matcher can match regular expressions to ``X-Label:'' fields with the `` y'' selector. ``X-Label:'' is not a standard message header field, but it can eas- ily be inserted by procmail and other mail filtering agents. - Lastly, Mutt has the ability to _s_o_r_t (section 6.3.285 , page 133) the mailbox - into _t_h_r_e_a_d_s (section 2.3.3 , page 7). A thread is a group of messages which - all relate to the same subject. This is usually organized into a tree-like - structure where a message and all of its replies are represented graphically. - If you've ever used a threaded news client, this is the same concept. It makes - dealing with large volume mailing lists easier because you can easily delete - uninteresting threads and quickly find topics of value. + The Mutt-ng E-Mail Client 47 + + Lastly, Mutt-ng has the ability to _s_o_r_t (section 6.3.289 , page 134) the mail- + box into _t_h_r_e_a_d_s (section 2.3.3 , page 7). A thread is a group of messages + which all relate to the same subject. This is usually organized into a tree- + like structure where a message and all of its replies are represented graphi- + cally. If you've ever used a threaded news client, this is the same concept. + It makes dealing with large volume mailing lists easier because you can easily + delete uninteresting threads and quickly find topics of value. _4_._1_0 _E_d_i_t_i_n_g _t_h_r_e_a_d_s - Mutt has the ability to dynamically restructure threads that are broken either - by misconfigured software or bad behavior from some correspondents. This allows - to clean your mailboxes formats) from these annoyances which make it hard to - follow a discussion. + Mutt-ng has the ability to dynamically restructure threads that are broken + either by misconfigured software or bad behavior from some correspondents. This + allows to clean your mailboxes formats) from these annoyances which make it + hard to follow a discussion. _4_._1_0_._1 _L_i_n_k_i_n_g _t_h_r_e_a_d_s Some mailers tend to "forget" to correctly set the "In-Reply-To:" and "Refer- ences:" headers when replying to a message. This results in broken discussions - because Mutt has not enough information to guess the correct threading. You + because Mutt-ng has not enough information to guess the correct threading. You can fix this by tagging the reply, then moving to the parent message and using the ``link-threads'' function (bound to & by default). The reply will then be connected to this "parent" message. @@ -2465,25 +2469,24 @@ RFC1894 defines a set of MIME content types for relaying information about the status of electronic mail messages. These can be thought of as ``return - - The Mutt-ng E-Mail Client 47 - receipts.'' Berkeley sendmail 8.8.x currently has some command line options in which the mail client can make requests as to what type of status messages should be returned. - To support this, there are two variables. _$_d_s_n___n_o_t_i_f_y (section 6.3.53 , page + To support this, there are two variables. _$_d_s_n___n_o_t_i_f_y (section 6.3.51 , page 76) is used to request receipts for different results (such as failed message, - message delivered, etc.). _$_d_s_n___r_e_t_u_r_n (section 6.3.54 , page 77) requests how + message delivered, etc.). _$_d_s_n___r_e_t_u_r_n (section 6.3.52 , page 76) requests how much of your message should be returned with the receipt (headers or full mes- sage). Refer to the man page on sendmail for more details on DSN. _4_._1_2 _P_O_P_3 _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) - If Mutt was compiled with POP3 support (by running the _c_o_n_f_i_g_u_r_e script with + If Mutt-ng was compiled with POP3 support (by running the _c_o_n_f_i_g_u_r_e script with the _-_-_e_n_a_b_l_e_-_p_o_p flag), it has the ability to work with mailboxes located on a remote POP3 server and fetch mail for local browsing. + The Mutt-ng E-Mail Client 48 + You can access the remote POP3 mailbox by selecting the folder pop://popserver/. @@ -2494,27 +2497,27 @@ name@popserver[:port]/. Polling for new mail is more expensive over POP3 than locally. For this reason - the frequency at which Mutt will check for mail remotely can be controlled by - the _$_p_o_p___c_h_e_c_k_i_n_t_e_r_v_a_l (section 6.3.197 , page 113) variable, which defaults + the frequency at which Mutt-ng will check for mail remotely can be controlled + by the _$_p_o_p___m_a_i_l___c_h_e_c_k (section 6.3.208 , page 115) variable, which defaults to every 60 seconds. - If Mutt was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script with the - _-_-_w_i_t_h_-_s_s_l 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://[user- + If Mutt-ng was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script with + the _-_-_w_i_t_h_-_s_s_l flag), connections to POP3 servers can be encrypted. This natu- + rally requires that the server supports SSL encrypted connections. To access a + folder with POP3/SSL, you should use pops: prefix, ie: pops://[user- name@]popserver[:port]/. Another way to access your POP3 mail is the _f_e_t_c_h_-_m_a_i_l function (default: G). - It allows to connect to _p_o_p___h_o_s_t (section 6.3.199 , page 113), fetch all your - new mail and place it in the local _s_p_o_o_l_f_i_l_e (section 6.3.291 , page 135). - After this point, Mutt runs exactly as if the mail had always been local. + It allows to connect to _p_o_p___h_o_s_t (section 6.3.206 , page 115), fetch all your + new mail and place it in the local _s_p_o_o_l_f_i_l_e (section 6.3.295 , page 136). + After this point, Mutt-ng runs exactly as if the mail had always been local. NNoottee:: If you only need to fetch all messages to local mailbox you should con- sider using a specialized program, such as fetchmail _4_._1_3 _I_M_A_P _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) - If Mutt was compiled with IMAP support (by running the _c_o_n_f_i_g_u_r_e script with + If Mutt-ng was compiled with IMAP support (by running the _c_o_n_f_i_g_u_r_e script with the _-_-_e_n_a_b_l_e_-_i_m_a_p flag), it has the ability to work with folders located on a remote IMAP server. @@ -2522,9 +2525,6 @@ imap://imapserver/INBOX, where imapserver is the name of the IMAP server and INBOX is the special name for your spool mailbox on the IMAP server. If you want to access another mail folder at the IMAP server, you should use - - The Mutt-ng E-Mail Client 48 - imap://imapserver/path/to/folder where path/to/folder is the path of the folder you want to access. @@ -2534,27 +2534,30 @@ You can also specify different username for each folder, i.e.: imap://user- name@imapserver[:port]/INBOX. - If Mutt was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script with the - _-_-_w_i_t_h_-_s_s_l 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://[user- + If Mutt-ng was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script with + the _-_-_w_i_t_h_-_s_s_l flag), connections to IMAP servers can be encrypted. This natu- + rally requires that the server supports SSL encrypted connections. To access a + folder with IMAP/SSL, you should use imaps://[user- name@]imapserver[:port]/path/to/folder as your folder path. - Pine-compatible notation is also supported, i.e. {[user- - name@]imapserver[:port][/ssl]}path/to/folder + Pine-compatible notation is also supported, i.e. + + The Mutt-ng E-Mail Client 49 + + {[username@]imapserver[:port][/ssl]}path/to/folder - Note that not all servers use / as the hierarchy separator. Mutt should cor- - rectly notice which separator is being used by the server and convert paths + Note that not all servers use / as the hierarchy separator. Mutt-ng should + correctly notice which separator is being used by the server and convert paths accordingly. 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 _t_o_g_g_l_e_-_s_u_b_s_c_r_i_b_e_d - command. See also the _$_i_m_a_p___l_i_s_t___s_u_b_s_c_r_i_b_e_d (section 6.3.100 , page 88) vari- + command. See also the _$_i_m_a_p___l_i_s_t___s_u_b_s_c_r_i_b_e_d (section 6.3.97 , page 87) vari- able. Polling for new mail on an IMAP server can cause noticeable delays. So, you'll - want to carefully tune the _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 6.3.101 , page 88) and - _$_t_i_m_e_o_u_t (section 6.3.311 , page 141) variables. + want to carefully tune the _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 6.3.99 , page 88) and + _$_t_i_m_e_o_u_t (section 6.3.318 , page 142) variables. Note that if you are using mbox as the mail store on UW servers prior to v12.250, the server has been reported to disconnect a client if another client @@ -2580,11 +2583,9 @@ respectively). You may also subscribe and unsubscribe to mailboxes (nor- mally these are bound to s and u, respectively). - The Mutt-ng E-Mail Client 49 - _4_._1_3_._2 _A_u_t_h_e_n_t_i_c_a_t_i_o_n - Mutt supports four authentication methods with IMAP servers: SASL, GSSAPI, + Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM authentica- tion for you poor exchange users out there, but it has yet to be integrated into the main tree). There is also support for the pseudo-protocol ANONYMOUS, @@ -2597,22 +2598,25 @@ DIGEST-MD5 and possibly GSSAPI), your 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 + + The Mutt-ng E-Mail Client 50 + and compile mutt with the _-_-_w_i_t_h_-_s_a_s_l flag. - Mutt will try whichever methods are compiled in and available on the server, in - the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN. + Mutt-ng will try whichever methods are compiled in and available on the server, + in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN. There are a few variables which control authentication: - +o _$_i_m_a_p___u_s_e_r (section 6.3.107 , page 90) - controls the username under + +o _$_i_m_a_p___u_s_e_r (section 6.3.105 , page 89) - controls the username under which you request authentication on the IMAP server, for all authentica- tors. This is overridden by an explicit username in the mailbox path (i.e. by using a mailbox name of the form {user@host}). - +o _$_i_m_a_p___p_a_s_s (section 6.3.102 , page 88) - a password which you may preset, + +o _$_i_m_a_p___p_a_s_s (section 6.3.100 , page 88) - a password which you may preset, used by all authentication methods where a password is needed. - +o _$_i_m_a_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s (section 6.3.94 , page 86) - a colon-delimited list + +o _$_i_m_a_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s (section 6.3.91 , page 85) - a colon-delimited list of IMAP authentication methods to try, in the order you wish to try them. If specified, this overrides mutt's default (attempt everything, in the order listed above). @@ -2634,9 +2638,6 @@ _4_._1_5 _S_t_a_r_t _a _W_W_W _B_r_o_w_s_e_r _o_n _U_R_L_s _(_E_X_T_E_R_N_A_L_) If a message contains URLs (_u_n_i_f_i_e_d _r_e_s_o_u_r_c_e _l_o_c_a_t_o_r = address in the WWW space - - The Mutt-ng E-Mail Client 50 - like _h_t_t_p_:_/_/_w_w_w_._m_u_t_t_._o_r_g_/), 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/con- @@ -2647,10 +2648,12 @@ _4_._1_6 _C_o_m_p_r_e_s_s_e_d _f_o_l_d_e_r_s _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) - If Mutt was compiled with compressed folders support (by running the _c_o_n_f_i_g_u_r_e - script with the _-_-_e_n_a_b_l_e_-_c_o_m_p_r_e_s_s_e_d flag), Mutt can open folders stored in an - arbitrary format, provided that the user has a script to convert from/to this - format to one of the accepted. + If Mutt-ng was compiled with compressed folders support (by running the _c_o_n_f_i_g_- + _u_r_e script with the _-_-_e_n_a_b_l_e_-_c_o_m_p_r_e_s_s_e_d flag), Mutt can open folders stored in + an arbitrary format, provided that the user has a script to convert from/to + this format to one of the accepted. + + The Mutt-ng E-Mail Client 51 The most common use is to open compressed archived folders e.g. with gzip. @@ -2676,20 +2679,18 @@ empty command) , the folder will be open in the mode. If you specify _a_p_p_e_n_d_- _h_o_o_k (section 4.16.3 , page 51) though you'll be able to append to the folder. - Note that Mutt will only try to use hooks if the file is not in one of the + Note that Mutt-ng will only try to use hooks if the file is not in one of the accepted formats. In particular, if the file is empty, mutt supposes it is not compressed. This is important because it allows the use of programs that do not have well defined extensions. Just use '.' as a regexp. But this may be sur- prising if your compressing script produces empty files. In this situation, - unset _$_s_a_v_e___e_m_p_t_y (section 6.3.233 , page 121), so that the compressed file + unset _$_s_a_v_e___e_m_p_t_y (section 6.3.240 , page 123), so that the compressed file will be removed if you delete all of the messages. _4_._1_6_._1 _O_p_e_n _a _c_o_m_p_r_e_s_s_e_d _m_a_i_l_b_o_x _f_o_r _r_e_a_d_i_n_g Usage: open-hook _r_e_g_e_x_p '_c_o_m_m_a_n_d' - The Mutt-ng E-Mail Client 51 - The _c_o_m_m_a_n_d is the command that can be used for opening the folders whose names match _r_e_g_e_x_p. @@ -2706,6 +2707,8 @@ Example: + The Mutt-ng E-Mail Client 52 + open-hook \\.gz$ "gzip -cd %f > %t" If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type. @@ -2740,9 +2743,6 @@ Usage: append-hook _r_e_g_e_x_p '_c_o_m_m_a_n_d' This command is used for saving to an existing compressed folder. The _c_o_m_m_a_n_d - - The Mutt-ng E-Mail Client 52 - is the command that can be used for appending to the folders whose names match _r_e_g_e_x_p. It has the same format as in the _o_p_e_n_-_h_o_o_k (section 4.16.1 , page 50) command. The temporary folder in this case contains the messages that are @@ -2757,7 +2757,10 @@ When _a_p_p_e_n_d_-_h_o_o_k (section 4.16.3 , page 51) is used, the folder is not opened, which saves time, but this means that we can not find out what the folder type - is. Thus the default (_$_m_b_o_x___t_y_p_e (section 6.3.128 , page 96)) type is always + is. Thus the default (_$_m_b_o_x___t_y_p_e (section 6.3.125 , page 95)) type is always + + The Mutt-ng E-Mail Client 53 + supposed (i.e. this is the format used for the temporary folder). If the file does not exist when you save to it, _c_l_o_s_e_-_h_o_o_k (section 4.16.2 , @@ -2784,34 +2787,33 @@ can be read by your system administrator. So think about the security aspects of this. - _5_. _M_u_t_t_'_s _M_I_M_E _S_u_p_p_o_r_t + _5_. _M_u_t_t_-_n_g_'_s _M_I_M_E _S_u_p_p_o_r_t - Quite a bit of effort has been made to make Mutt the premier text-mode MIME + Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME MUA. Every effort has been made to provide the functionality that the discern- ing MIME user requires, and the conformance to the standards wherever possible. - When configuring Mutt for MIME, there are two extra types of configuration - files which Mutt uses. One is the mime.types file, which contains the mapping - of file extensions to IANA MIME types. The other is the mailcap file, which - - The Mutt-ng E-Mail Client 53 - - specifies the external commands to use for handling specific MIME types. + When configuring Mutt-ng for MIME, there are two extra types of configuration + files which Mutt-ng uses. One is the mime.types file, which contains the map- + ping of file extensions to IANA MIME types. The other is the mailcap file, + which specifies the external commands to use for handling specific MIME types. _5_._1 _U_s_i_n_g _M_I_M_E _i_n _M_u_t_t - There are three areas/menus in Mutt which deal with MIME, they are the pager + There are three areas/menus in Mutt-ng which deal with MIME, they are the pager (while viewing a message), the attachment menu and the compose menu. _5_._1_._1 _V_i_e_w_i_n_g _M_I_M_E _m_e_s_s_a_g_e_s _i_n _t_h_e _p_a_g_e_r When you select a message from the index and view it in the pager, Mutt decodes - the message to a text representation. Mutt internally supports a number of + the message to a text representation. Mutt-ng internally supports a number of MIME types, including text/plain, text/enriched, message/rfc822, and mes- - sage/news. In addition, the export controlled version of Mutt recognizes a + sage/news. In addition, the export controlled version of Mutt-ng recognizes a variety of PGP MIME types, including PGP/MIME and application/pgp. - Mutt will denote attachments with a couple lines describing them. These lines - are of the form: + Mutt-ng will denote attachments with a couple lines describing them. These + lines are of the form: + + The Mutt-ng E-Mail Client 54 [-- Attachment #1: Description --] [-- Type: text/plain, Encoding: 7bit, Size: 10000 --] @@ -2819,7 +2821,7 @@ Where the Description is the description or filename given for the attachment, and the Encoding is one of 7bit/8bit/quoted-printable/base64/binary. - If Mutt cannot deal with a MIME type, it will display a message like: + If Mutt-ng cannot deal with a MIME type, it will display a message like: [-- image/gif is unsupported (use 'v' to view this part) --] @@ -2847,9 +2849,6 @@ also contains a list of the attachments of your message, including the main body. From this menu, you can print, copy, filter, pipe, edit, compose, review, and rename an attachment or a list of tagged attachments. You can also - - The Mutt-ng E-Mail Client 54 - modifying the attachment information, notably the type, encoding and descrip- tion. @@ -2858,8 +2857,8 @@ - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz - The '-' denotes that Mutt will delete the file after sending (or postponing, or - canceling) the message. It can be toggled with the toggle-unlink command + The '-' denotes that Mutt-ng will delete the file after sending (or postponing, + or canceling) the message. It can be toggled with the toggle-unlink command (default: u). The next field is the MIME content-type, and can be changed with the edit-type command (default: ^T). The next field is the encoding for the attachment, which allows a binary message to be encoded for transmission on @@ -2867,11 +2866,14 @@ The next field is the size of the attachment, rounded to kilobytes or megabytes. The next field is the filename, which can be changed with the rename-file command (default: R). The final field is the description of the + + The Mutt-ng E-Mail Client 55 + attachment, and can be changed with the edit-description command (default: d). _5_._2 _M_I_M_E _T_y_p_e _c_o_n_f_i_g_u_r_a_t_i_o_n _w_i_t_h _m_i_m_e_._t_y_p_e_s - When you add an attachment to your mail message, Mutt searches your personal + When you add an attachment to your mail message, Mutt-ng searches your personal mime.types file at ${HOME}/.mime.types, and then the system mime.types file at /usr/local/share/mutt/mime.types or /etc/mime.types @@ -2882,44 +2884,46 @@ application/pgp pgp audio/x-aiff aif aifc aiff - A sample mime.types file comes with the Mutt distribution, and should contain - most of the MIME types you are likely to use. + A sample mime.types file comes with the Mutt-ng distribution, and should con- + tain most of the MIME types you are likely to use. - If Mutt can not determine the mime type by the extension of the file you + If Mutt-ng can not determine the mime type by the extension of the file you attach, it will look at the file. If the file is free of binary information, - Mutt will assume that the file is plain text, and mark it as text/plain. If - the file contains binary information, then Mutt will mark it as applica- - tion/octet-stream. You can change the MIME type that Mutt assigns to an + Mutt-ng will assume that the file is plain text, and mark it as text/plain. If + the file contains binary information, then Mutt-ng will mark it as applica- + tion/octet-stream. You can change the MIME type that Mutt-ng assigns to an attachment by using the edit-type command from the compose menu (default: ^T). The MIME type is actually a major mime type followed by the sub-type, separated by a '/'. 6 major types: application, text, image, video, audio, and model have - been approved after various internet discussions. Mutt recognises all of these - if the appropriate entry is found in the mime.types file. It also recognises - other major mime types, such as the chemical type that is widely used in the - molecular modelling community to pass molecular data in various forms to vari- - ous molecular viewers. Non-recognised mime types should only be used if the + been approved after various internet discussions. Mutt-ng recognises all of + these if the appropriate entry is found in the mime.types file. It also recog- + nises other major mime types, such as the chemical type that is widely used in + the molecular modelling community to pass molecular data in various forms to + various molecular viewers. Non-recognised mime types should only be used if the recipient of the message is likely to be expecting such attachments. _5_._3 _M_I_M_E _V_i_e_w_e_r _c_o_n_f_i_g_u_r_a_t_i_o_n _w_i_t_h _m_a_i_l_c_a_p - The Mutt-ng E-Mail Client 55 - - Mutt supports RFC 1524 MIME Configuration, in particular the Unix specific for- - mat specified in Appendix A of RFC 1524. This file format is commonly referred - to as the mailcap format. Many MIME compliant programs utilize the mailcap - format, allowing you to specify handling for all MIME types in one place for - all programs. Programs known to use this format include Netscape, XMosaic, - lynx and metamail. + Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix specific + format specified in Appendix A of RFC 1524. This file format is commonly + referred to as the mailcap format. Many MIME compliant programs utilize the + mailcap format, allowing you to specify handling for all MIME types in one + place for all programs. Programs known to use this format include Netscape, + XMosaic, lynx and metamail. - In order to handle various MIME types that Mutt can not handle internally, Mutt - parses a series of external configuration files to find an external handler. - The default search string for these files is a colon delimited list set to + In order to handle various MIME types that Mutt-ng can not handle internally, + Mutt-ng parses a series of external configuration files to find an external + handler. The default search string for these files is a colon delimited list + set to ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap where $HOME is your home directory. In particular, the metamail distribution will install a mailcap file, usually + + The Mutt-ng E-Mail Client 56 + as /usr/local/etc/mailcap, which contains some baseline entries. _5_._3_._1 _T_h_e _B_a_s_i_c_s _o_f _t_h_e _m_a_i_l_c_a_p _f_i_l_e @@ -2945,19 +2949,17 @@ The view command is a Unix command for viewing the type specified. There are two different types of commands supported. The default is to send the body of the MIME message to the command on stdin. You can change this behavior by using - %s as a parameter to your view command. This will cause Mutt to save the body - of the MIME message to a temporary file, and then call the view command with - the %s replaced by the name of the temporary file. In both cases, Mutt will - turn over the terminal to the view program until the program quits, at which - time Mutt will remove the temporary file if it exists. + %s as a parameter to your view command. This will cause Mutt-ng to save the + body of the MIME message to a temporary file, and then call the view command + with the %s replaced by the name of the temporary file. In both cases, Mutt-ng + will turn over the terminal to the view program until the program quits, at + which time Mutt will remove the temporary file if it exists. So, in the simplest form, you can send a text/plain message to the external pager more on stdin: text/plain; more - The Mutt-ng E-Mail Client 56 - Or, you could send the message as a file: text/plain; more %s @@ -2973,6 +2975,9 @@ _v_i_e_w _t_h_e _o_b_j_e_c_t_. On the other hand, maybe you don't want to use lynx interactively, you just + + The Mutt-ng E-Mail Client 57 + want to have it convert the text/html to text/plain, then you can use: text/html; lynx -dump %s | more @@ -2988,17 +2993,17 @@ _5_._3_._2 _S_e_c_u_r_e _u_s_e _o_f _m_a_i_l_c_a_p The interpretation of shell meta-characters embedded in MIME parameters can - lead to security problems in general. Mutt tries to quote parameters in expan- - sion of %s syntaxes properly, and avoids risky characters by substituting them, - see the _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e (section 6.3.120 , page 95) variable. + lead to security problems in general. Mutt-ng tries to quote parameters in + expansion of %s syntaxes properly, and avoids risky characters by substituting + them, see the _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e (section 6.3.117 , page 94) variable. Although mutt's procedures to invoke programs with mailcap seem to be safe, there are other applications parsing mailcap, maybe taking less care of it. Therefore you should pay attention to the following rules: _K_e_e_p _t_h_e _%_-_e_x_p_a_n_d_o_s _a_w_a_y _f_r_o_m _s_h_e_l_l _q_u_o_t_i_n_g_. Don't quote them with single or - double quotes. Mutt does this for you, the right way, as should any other pro- - gram which interprets mailcap. Don't put them into backtick expansions. Be + double quotes. Mutt-ng 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 avoid them if possible at all. Trying to fix broken behaviour with quotes introduces new leaks - there is no alterna- tive to correct quoting in the first place. @@ -3009,8 +3014,6 @@ inside the backtick expansion is safe, since it is not itself subject to any further expansion): - The Mutt-ng E-Mail Client 57 - text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1 @@ -3019,56 +3022,59 @@ _5_._3_._3_._1 _O_p_t_i_o_n_a_l _F_i_e_l_d_s 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 recog- + semi-colon ';' separated fields to set flags and other options. Mutt-ng recog- nizes the following optional fields: copiousoutput - 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 pager variable) - on the output of the view command. Without this flag, Mutt assumes - that the command is interactive. One could use this to replace the - pipe to more in the lynx -dump example in the Basic section: + This flag tells Mutt-ng that the command passes possibly large + amounts of text on stdout. This causes Mutt-ng to invoke a pager + + The Mutt-ng E-Mail Client 58 + + (either the internal pager or the external pager defined by the + pager variable) on the output of the view command. Without this + flag, Mutt-ng assumes that the command is interactive. One could + use this to replace the pipe to more in the lynx -dump example in + the Basic section: text/html; lynx -dump %s ; copiousoutput This will cause lynx to format the text/html output as text/plain - and Mutt will use your standard pager to display the results. + and Mutt-ng will use your standard pager to display the results. needsterminal - Mutt uses this flag when viewing attachments with _a_u_t_o_v_i_e_w (section - 5.4 , page 60), in order to decide whether it should honor the - setting of the _$_w_a_i_t___k_e_y (section 6.3.325 , page 144) variable or - not. When an attachment is viewed using an interactive program, - and the corresponding mailcap entry has a _n_e_e_d_s_t_e_r_m_i_n_a_l flag, Mutt - will use _$_w_a_i_t___k_e_y (section 6.3.325 , page 144) and the exit sta- - tus of the program to decide if it will ask you to press a key + Mutt-ng uses this flag when viewing attachments with _a_u_t_o_v_i_e_w (sec- + tion 5.4 , page 60), in order to decide whether it should honor + the setting of the _$_w_a_i_t___k_e_y (section 6.3.332 , page 145) variable + or not. When an attachment is viewed using an interactive program, + and the corresponding mailcap entry has a _n_e_e_d_s_t_e_r_m_i_n_a_l flag, Mutt- + ng will use _$_w_a_i_t___k_e_y (section 6.3.332 , page 145) 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. compose= This flag specifies the command to use to create a new attachment - of a specific MIME type. Mutt supports this from the compose menu. + of a specific MIME type. Mutt-ng supports this from the compose + menu. composetyped= 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 headers on the data. This can be used to specify parameters, filename, description, etc. - for a new attachment. Mutt supports this from the compose menu. + for a new attachment. Mutt-ng supports this from the compose + menu. print= This flag specifies the command to use to print a specific MIME - type. Mutt supports this from the attachment and compose menus. + type. Mutt-ng supports this from the attachment and compose menus. edit= This flag specifies the command to use to edit a specific MIME - - The Mutt-ng E-Mail Client 58 - - type. Mutt supports this from the compose menu, and also uses it - to compose new attachments. Mutt will default to the defined edi- - tor for text attachments. + type. Mutt-ng supports this from the compose menu, and also uses + it to compose new attachments. Mutt-ng will default to the defined + editor for text attachments. nametemplate=