X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=doc%2Fmanual.txt;h=ec54e0b8f96697d0c8dd59e28ab87383fcec7990;hp=457beac60ee047a5f71d2116b6a4cfb6ba72bfea;hb=452ffdd4bbcd8f2dd9e4811c115824b556814ebb;hpb=f7a7cee0f8bce7ddc378197a9394c6fceb6988ec diff --git a/doc/manual.txt b/doc/manual.txt index 457beac..ec54e0b 100644 --- a/doc/manual.txt +++ b/doc/manual.txt @@ -4,7 +4,7 @@ by Andreas Krennmair and others originally based on _m_u_t_t by Michael Elkins and others - version devel-r392 + version devel-r462 AAbbssttrraacctt @@ -316,7 +316,7 @@ ^G n/a abort n/a finish editing - You can remap the _e_d_i_t_o_r functions using the _b_i_n_d (section 3.4 , page 24) com- + You can remap the _e_d_i_t_o_r functions using the _b_i_n_d (section 3.5 , page 27) com- mand. For example, to make the _D_e_l_e_t_e key delete the character in front of the cursor rather than under, you could use @@ -413,7 +413,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.4.323 , page 160) variable. + can be customized with the _$_t_o___c_h_a_r_s (section 7.4.336 , page 171) variable. + message is to you and you only @@ -461,7 +461,7 @@ letter again for bold or the letter, backspace, ``_'' for denoting underline. Mutt-ng will attempt to display these in bold and underline respectively if your terminal supports them. If not, you can use the bold and underline _c_o_l_o_r - (section 3.8 , page 27) objects to specify a color or mono attribute for them. + (section 3.9 , page 30) objects to specify a color or mono attribute for them. Additionally, the internal pager supports the ANSI escape sequences for charac- ter attributes. Mutt-ng translates them into the correct color and character @@ -490,14 +490,14 @@ The Mutt Next Generation E-Mail Client 11 Mutt-ng uses these attributes for handling text/enriched messages, and they can - also be used by an external _a_u_t_o_v_i_e_w (section 5.4 , page 74) script for high- + also be used by an external _a_u_t_o_v_i_e_w (section 5.4 , page 78) script for high- lighting purposes. NNoottee:: If you change the colors for your display, for exam- ple by changing the color associated with color2 for your xterm, then that color will be used instead of green. _2_._5_._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.4.291 , page 150) by _t_h_r_e_a_d_s, there are + When the mailbox is _s_o_r_t_e_d (section 7.4.304 , page 161) 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 @@ -518,11 +518,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.4.110 , page 106). For example, you could use "%?M?(#%03M)&(%4l)?" in - _$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page 106) to optionally display the number of + tion 7.4.116 , page 115). For example, you could use "%?M?(#%03M)&(%4l)?" in + _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115) 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.4.312 , page 158). + See also: _$_s_t_r_i_c_t___t_h_r_e_a_d_s (section 7.4.325 , page 168). _2_._5_._4 _M_i_s_c_e_l_l_a_n_e_o_u_s _F_u_n_c_t_i_o_n_s @@ -530,11 +530,11 @@ (default: a) Creates a new alias based upon the current message (or prompts for a new one). - Once editing is complete, an _a_l_i_a_s (section 3.3 , page 23) command is added to - the file specified by the _$_a_l_i_a_s___f_i_l_e (section 6.4.3 , page 81) variable for - future use. NNoottee:: Specifying an _$_a_l_i_a_s___f_i_l_e (section 6.4.3 , page 81) does not - add the aliases specified there-in, you must also _s_o_u_r_c_e (section 3.28 , page - 42) the file. + Once editing is complete, an _a_l_i_a_s (section 3.4 , page 26) command is added to + the file specified by the _$_a_l_i_a_s___f_i_l_e (section 7.4.5 , page 89) variable for + future use. NNoottee:: Specifying an _$_a_l_i_a_s___f_i_l_e (section 7.4.5 , page 89) does not + add the aliases specified there-in, you must also _s_o_u_r_c_e (section 3.29 , page + 45) the file. cchheecckk--ttrraaddiittiioonnaall--ppggpp (default: ESC P) @@ -552,7 +552,7 @@ (default: h) Toggles the weeding of message header fields specified by _i_g_n_o_r_e (section - 3.9 , page 30) commands. + 3.10 , page 32) commands. eeddiitt (default: e) @@ -570,12 +570,12 @@ This command is used to temporarily edit an attachment's content type to fix, for instance, bogus character set parameters. When invoked from the index or from the pager, you'll have the opportunity to edit the top-level attachment's - content type. On the _a_t_t_a_c_h_m_e_n_t _m_e_n_u (section 5.1.2 , page 67), you can + content type. On the _a_t_t_a_c_h_m_e_n_t _m_e_n_u (section 5.1.2 , page 71), you can change any attachment's content type. These changes are not persistent, and get lost upon changing folders. Note that this command is also available on the _c_o_m_p_o_s_e _m_e_n_u (section 5.1.3 , - page 67). There, it's used to fine-tune the properties of attachments you are + page 71). There, it's used to fine-tune the properties of attachments you are going to send. eenntteerr--ccoommmmaanndd @@ -583,7 +583,7 @@ This command is used to execute any command you would normally put in a config- uration file. A common use is to check the settings of variables, or in con- - junction with _m_a_c_r_o_s (section 3.7 , page 27) to change settings on the fly. + junction with _m_a_c_r_o_s (section 3.8 , page 29) to change settings on the fly. eexxttrraacctt--kkeeyyss (default: ^K) @@ -603,9 +603,9 @@ (default: L) Reply to the current or tagged message(s) by extracting any addresses which - 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.12 , - page 32) 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.4.88 , page 101) configuration variable is set. + 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.13 , + page 36) 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 7.4.94 , page 110) 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. @@ -613,9 +613,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.4.200 , page 130), _$_p_i_p_e___s_p_l_i_t - (section 6.4.202 , page 130), _$_p_i_p_e___s_e_p (section 6.4.201 , page 130) and - _$_w_a_i_t___k_e_y (section 6.4.335 , page 162) control the exact behavior of this + it. The variables _$_p_i_p_e___d_e_c_o_d_e (section 7.4.213 , page 140), _$_p_i_p_e___s_p_l_i_t + (section 7.4.215 , page 141), _$_p_i_p_e___s_e_p (section 7.4.214 , page 140) and + _$_w_a_i_t___k_e_y (section 7.4.347 , page 173) control the exact behavior of this function. rreesseenndd--mmeessssaaggee @@ -625,7 +625,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.4.336 , page 163) variable. + the value of the _$_w_e_e_d (section 7.4.348 , page 173) 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- @@ -635,14 +635,14 @@ (default: !) Asks for an external Unix command and executes it. The _$_w_a_i_t___k_e_y (section - 6.4.335 , page 162) can be used to control whether Mutt-ng will wait for a key + 7.4.347 , page 173) 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.4.225 , page 135) variable to + The _p_a_g_e_r uses the _$_q_u_o_t_e___r_e_g_e_x_p (section 7.4.238 , page 146) 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 @@ -755,7 +755,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.4.308 , page 155) will change to a + folder. The %r in _$_s_t_a_t_u_s___f_o_r_m_a_t (section 7.4.321 , page 165) will change to a 'A' to indicate that you are in attach-message mode. The Mutt Next Generation E-Mail Client 16 @@ -863,7 +863,7 @@ 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.4.54 , page 93). + Also see _e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 102). _2_._6_._4 _U_s_i_n_g _M_u_t_t_-_n_g _w_i_t_h _P_G_P @@ -872,7 +872,7 @@ 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.4.192 , page 128) permanently. + _$_p_g_p___s_i_g_n___a_s (section 7.4.205 , page 139) 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-ng will not ask you @@ -890,7 +890,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.4.179 , page 125)) have obvious meanings. But some explana- + _m_a_t (section 7.4.192 , page 135)) 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: @@ -947,8 +947,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.4.139 , - page 114)). Most important is the ``middleman'' capability, indicated by a + %c entry of the remailer menu lines (see _$_m_i_x___e_n_t_r_y___f_o_r_m_a_t (section 7.4.146 , + page 124)). Most important is the ``middleman'' capability, indicated by a capital ``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 @@ -1001,7 +1001,7 @@ 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.4.214 , page 133) variable. This means that you can + the _$_p_o_s_t_p_o_n_e_d (section 7.4.227 , page 143) variable. This means that you can recall the message even if you exit Mutt-ng and then restart it at a later time. @@ -1019,7 +1019,7 @@ 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.4.213 , page 133) quad-option. + See also the _$_p_o_s_t_p_o_n_e (section 7.4.226 , page 143) quad-option. _3_. _C_o_n_f_i_g_u_r_a_t_i_o_n @@ -1029,7 +1029,7 @@ 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 76) option is specified. This + the ``-n'' _c_o_m_m_a_n_d _l_i_n_e (section 7.1 , page 82) 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 @@ -1037,12 +1037,12 @@ 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.3 , page 79) to configure Mutt-ng. + your _c_o_m_m_a_n_d_s (section 7.3 , page 85) to configure Mutt-ng. - _3_._2 _S_y_n_t_a_x _o_f _I_n_i_t_i_a_l_i_z_a_t_i_o_n _F_i_l_e_s + _3_._2 _B_a_s_i_c _S_y_n_t_a_x _o_f _I_n_i_t_i_a_l_i_z_a_t_i_o_n _F_i_l_e_s - An initialization file consists of a series of _c_o_m_m_a_n_d_s (section 6.3 , page - 79). Each line of the file may contain one or more commands. When multiple + An initialization file consists of a series of _c_o_m_m_a_n_d_s (section 7.3 , page + 85). 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-ng user' ; ignore x- @@ -1102,27 +1102,161 @@ which includes line3 and line4. line5 is a new line of its own and thus is interpreted again. - It is also possible to substitute the output of a Unix command in an initial- - ization file. This is accomplished by enclosing the command in backquotes - (``). For example, + The commands understood by mutt are explained in the next paragraphs. For a + complete list, see the _c_o_m_m_a_n_d _r_e_f_e_r_e_n_c_e (section 7.3 , page 85). The Mutt Next Generation E-Mail Client 23 + _3_._3 _E_x_p_a_n_s_i_o_n _w_i_t_h_i_n _v_a_r_i_a_b_l_e_s + + Besides just assign static content to variables, there's plenty of ways of + adding external and more or less dynamic content. + + _3_._3_._1 _C_o_m_m_a_n_d_s_' _O_u_t_p_u_t + + It is possible to substitute the output of a Unix command in an initialization + file. This is accomplished by enclosing the command in backquotes (``) as in, + for example: + my_hdr X-Operating-System: `uname -a` The output of the Unix command ``uname -a'' will be substituted before the line - is parsed. Note that since initialization files are line oriented, only the + is parsed. Note that since initialization files are line oriented, only the first line of output from the Unix command will be substituted. + _3_._3_._2 _E_n_v_i_r_o_n_m_e_n_t _V_a_r_i_a_b_l_e_s + UNIX environments can be accessed like the way it is done in shells like sh and - bash: Prepend the name of the environment by a ``$''. For example, + bash: Prepend the name of the environment by a ``$'' sign. For example, set record=+sent_on_$HOSTNAME - The commands understood by mutt are explained in the next paragraphs. For a - complete list, see the _c_o_m_m_a_n_d _r_e_f_e_r_e_n_c_e (section 6.3 , page 79). + sets the _$_r_e_c_o_r_d (section 7.4.243 , page 147) variable to the string _+_s_e_n_t___o_n__ + and appends the value of the evironment variable $HOSTNAME. + + NNoottee:: There will be no warning if an environment variable is not defined. The + result will of the expansion will then be empty. + + _3_._3_._3 _C_o_n_f_i_g_u_r_a_t_i_o_n _V_a_r_i_a_b_l_e_s + + As for environment variables, the values of all configuration variables as + string can be used in the same way, too. For example, + + set imap_home_namespace = $folder + + would set the value of _$_i_m_a_p___h_o_m_e___n_a_m_e_s_p_a_c_e (section 7.4.101 , page 112) to + the value to which _$_f_o_l_d_e_r (section 7.4.70 , page 104) is _c_u_r_r_e_n_t_l_y set to. + + NNoottee:: There're no logical links established in such cases so that the the value + for _$_i_m_a_p___h_o_m_e___n_a_m_e_s_p_a_c_e (section 7.4.101 , page 112) won't change even if + _$_f_o_l_d_e_r (section 7.4.70 , page 104) gets changed. + + NNoottee:: There will be no warning if a configuration variable is not defined or is + empty. The result will of the expansion will then be empty. + + The Mutt Next Generation E-Mail Client 24 + + _3_._3_._4 _S_e_l_f_-_D_e_f_i_n_e_d _V_a_r_i_a_b_l_e_s + + Mutt-ng flexibly allows users to define their own variables. To avoid conflicts + with the standard set and to prevent misleading error messages, there's a + reserved namespace for them: all user-defined variables must be prefixed with + user_ and can be used just like any ordinary configuration or environment vari- + able. + + For example, to view the manual, users can either define two macros like the + following + + macro generic "!less -r /path/to/manual" "Show manual" + macro pager "!less -r /path/to/manual" "Show manual" + + for generic, pager and index. The alternative is to define a custom variable + like so: + + set user_manualcmd = "!less -r /path/to_manual" + macro generic "$user_manualcmd" "Show manual" + macro pager "$user_manualcmd" "Show manual" + macro index "$user_manualcmd" "Show manual" + + to re-use the command sequence as in: + + macro index "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns" + + Using this feature, arbitrary sequences can be defined once and recalled and + reused where necessary. More advanced scenarios could include to save a vari- + able's value at the beginning of macro sequence and restore it at end. + + When the variable is first defined, the first value it gets assigned is also + the initial value to which it can be reset using the reset command. + + The complete removal is done via the unset keyword. + + After the following sequence: + + set user_foo = 42 + set user_foo = 666 + + the variable $user_foo has a current value of 666 and an initial of 42. The + query + + set ?user_foo - _3_._3 _D_e_f_i_n_i_n_g_/_U_s_i_n_g _a_l_i_a_s_e_s + The Mutt Next Generation E-Mail Client 25 + + will show 666. After doing the reset via + + reset user_foo + + a following query will give 42 as the result. After unsetting it via + + unset user_foo + + any query or operation (except the noted expansion within other statements) + will lead to an error message. + + _3_._3_._5 _P_r_e_-_D_e_f_i_n_e_d _V_a_r_i_a_b_l_e_s + + In order to allow users to share one setup over a number of different machines + without having to change its contents, there's a number of pre-defined vari- + ables. These are prefixed with muttng_ and are read-only, i.e. they cannot be + set, unset or reset. The reference chapter lists all available variables. + + _P_l_e_a_s_e _c_o_n_s_u_l_t _t_h_e _l_o_c_a_l _c_o_p_y _o_f _y_o_u_r _m_a_n_u_a_l _f_o_r _t_h_e_i_r _v_a_l_u_e_s _a_s _t_h_e_y _m_a_y _d_i_f_- + _f_e_r _f_r_o_m _d_i_f_f_e_r_e_n_t _m_a_n_u_a_l _s_o_u_r_c_e_s_. Where the manual is installed in can be + queried (already using such a variable) by running: + + muttng -Q muttng_docdir + + To extend the example for viewing the manual via self-defined variables, it can + be made more readable and more portable by changing the real path in: + + set user_manualcmd = '!less -r /path/to_manual' + + to: + + set user_manualcmd = "!less -r $muttng_docdir/manual.txt" + + which works everywhere if a manual is installed. + + _N_o_t_e_: _t_h_i_s _i_s _a _d_r_a_f_t _f_e_a_t_u_r_e _a_n_d _m_a_y_b_e _s_u_b_j_e_c_t _t_o _c_h_a_n_g_e _i_n _t_h_e _n_e_a_r _f_u_t_u_r_e_. + + _3_._3_._6 _T_y_p_e _C_o_n_v_e_r_s_i_o_n_s + + A note about variable's types during conversion: internally values are stored + in internal types but for any dump/query or set operation they're converted to + and from string. That means that there's no need to worry about types when ref- + erencing any variable. As an example, the following can be used without harm + (besides makeing muttng very likely behave strange): + + The Mutt Next Generation E-Mail Client 26 + + set read_inc = 100 + set folder = $read_inc + set read_inc = $folder + set user_magic_number = 42 + set folder = $user_magic_number + + _3_._4 _D_e_f_i_n_i_n_g_/_U_s_i_n_g _a_l_i_a_s_e_s Usage: alias _k_e_y _a_d_d_r_e_s_s [ , _a_d_d_r_e_s_s, ... ] @@ -1142,20 +1276,18 @@ 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.28 , page 42). Consequently, you can + long as this file is _s_o_u_r_c_e_d (section 3.29 , page 45). 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.5.4 , page 11) function can use - only one file, the one pointed to by the _$_a_l_i_a_s___f_i_l_e (section 6.4.3 , page 81) + only one file, the one pointed to by the _$_a_l_i_a_s___f_i_l_e (section 7.4.5 , page 89) variable (which is ~/.muttrc by default). This file is not special either, in 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.28 , page 42) this file too. + 3.29 , page 45) this file too. For example: - The Mutt Next Generation E-Mail Client 24 - source /usr/local/share/Mutt-ng.aliases source ~/.mail_aliases set alias_file=~/.mail_aliases @@ -1163,10 +1295,13 @@ 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.4.54 , page 93) variable set. + (section 7.4.59 , page 102) 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 + + The Mutt Next Generation E-Mail Client 27 + will bring up a menu with the matching aliases. In order to be presented with the full list of aliases, you must hit tab with out a partial alias, such as at the beginning of the prompt or after a comma denoting multiple addresses. @@ -1175,7 +1310,7 @@ _e_n_t_r_y key (default: RET), and use the _e_x_i_t key (default: q) to return to the address prompt. - _3_._4 _C_h_a_n_g_i_n_g _t_h_e _d_e_f_a_u_l_t _k_e_y _b_i_n_d_i_n_g_s + _3_._5 _C_h_a_n_g_i_n_g _t_h_e _d_e_f_a_u_l_t _k_e_y _b_i_n_d_i_n_g_s Usage: bind _m_a_p _k_e_y _f_u_n_c_t_i_o_n @@ -1204,11 +1339,8 @@ messages. browser - The browser is used for both browsing the local directory - - The Mutt Next Generation E-Mail Client 25 - - structure, and for listing all of your incoming mailboxes. + The browser is used for both browsing the local directory struc- + ture, and for listing all of your incoming mailboxes. editor The editor is the line-based editor the user enters text data. @@ -1219,6 +1351,8 @@ compose The compose menu is the screen used when sending a new message. + The Mutt Next Generation E-Mail Client 28 + pager The pager is the mode used to display message/attachment data, and help listings. @@ -1240,8 +1374,6 @@ In addition, _k_e_y may consist of: - The Mutt Next Generation E-Mail Client 26 - \t tab tab backtab / shift-tab @@ -1269,10 +1401,12 @@ _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.5 , page 165). The special + list of functions, see the _r_e_f_e_r_e_n_c_e (section 7.5 , page 175). The special function noop unbinds the specified key sequence. - _3_._5 _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 + The Mutt Next Generation E-Mail Client 29 + + _3_._6 _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 Usage: charset-hook _a_l_i_a_s _c_h_a_r_s_e_t @@ -1286,21 +1420,18 @@ This is helpful when your systems character conversion library insists on using strange, system-specific names for character sets. - _3_._6 _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 + _3_._7 _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 - It is often desirable to change settings based on which mailbox you are - - The Mutt Next Generation E-Mail Client 27 - - reading. 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 + 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.4.297 , page - 152) 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 7.4.310 , page + 163) 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. @@ -1315,36 +1446,36 @@ folder-hook . set sort=date-sent - _3_._7 _K_e_y_b_o_a_r_d _m_a_c_r_o_s + _3_._8 _K_e_y_b_o_a_r_d _m_a_c_r_o_s 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-ng will behave as if you had + + The Mutt Next Generation E-Mail Client 30 + 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.4 , page 24) which the macro will be bound. Multi- + _m_e_n_u is the _m_a_p (section 3.5 , page 27) which the macro will be bound. Multi- ple maps may be specified by separating multiple menu arguments by commas. Whitespace may not be used in between the menu arguments and the commas sepa- rating them. _k_e_y and _s_e_q_u_e_n_c_e are expanded by the same rules as the _k_e_y _b_i_n_d_i_n_g_s (section - 3.4 , page 24). There are some additions however. The first is that control + 3.5 , page 27). There are some additions however. The first is that control characters in _s_e_q_u_e_n_c_e can also be specified as _^_x. In order to get a caret (`^'') you need to use _^_^. Secondly, to specify a certain key such as _u_p or to 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.4 , page 24). Functions are listed in the _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section - 6.5 , page 165). + 3.5 , page 27). Functions are listed in the _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section + 7.5 , page 175). 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 - - The Mutt Next Generation E-Mail Client 28 - (eg. the system Muttngrc). Optionally you can specify a descriptive text after _s_e_q_u_e_n_c_e, which is shown in @@ -1353,7 +1484,7 @@ NNoottee:: Macro definitions (if any) listed in the help screen(s), are silently truncated at the screen width, and are not wrapped. - _3_._8 _U_s_i_n_g _c_o_l_o_r _a_n_d _m_o_n_o _v_i_d_e_o _a_t_t_r_i_b_u_t_e_s + _3_._9 _U_s_i_n_g _c_o_l_o_r _a_n_d _m_o_n_o _v_i_d_e_o _a_t_t_r_i_b_u_t_e_s Usage: color _o_b_j_e_c_t _f_o_r_e_g_r_o_u_n_d _b_a_c_k_g_r_o_u_n_d [ _r_e_g_e_x_p ] @@ -1376,6 +1507,8 @@ +o error (error messages printed by Mutt-ng) + The Mutt Next Generation E-Mail Client 31 + +o header (match _r_e_g_e_x_p in the message header) +o hdrdefault (default color of the message header in the pager) @@ -1390,15 +1523,13 @@ +o normal - +o quoted (text matching _$_q_u_o_t_e___r_e_g_e_x_p (section 6.4.225 , page 135) in the + +o quoted (text matching _$_q_u_o_t_e___r_e_g_e_x_p (section 7.4.238 , page 146) in the body of a message) +o quoted1, quoted2, ..., quotedNN (higher levels of quoting) +o search (highlighting of words in the pager) - The Mutt Next Generation E-Mail Client 29 - +o signature +o status (mode lines used to display info about the mailbox or message) @@ -1431,8 +1562,11 @@ +o color_x - _f_o_r_e_g_r_o_u_n_d can optionally be prefixed with the keyword bright to make the fore- - ground color boldfaced (e.g., brightred). + _f_o_r_e_g_r_o_u_n_d can optionally be prefixed with the keyword bright to make the + + The Mutt Next Generation E-Mail Client 32 + + foreground 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-ng is @@ -1451,8 +1585,6 @@ command for it to be removed. The pattern ``*'' is a special token which means to clear the color index list of all entries. - The Mutt Next Generation E-Mail Client 30 - 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 @@ -1479,11 +1611,14 @@ +o standout - _3_._9 _I_g_n_o_r_i_n_g _(_w_e_e_d_i_n_g_) _u_n_w_a_n_t_e_d _m_e_s_s_a_g_e _h_e_a_d_e_r_s + _3_._1_0 _I_g_n_o_r_i_n_g _(_w_e_e_d_i_n_g_) _u_n_w_a_n_t_e_d _m_e_s_s_a_g_e _h_e_a_d_e_r_s Usage: [un]ignore _p_a_t_t_e_r_n [ _p_a_t_t_e_r_n ... ] Messages often have many header fields added by automatic processing systems, + + The Mutt Next Generation E-Mail Client 33 + or which may not seem useful to display on the screen. This command allows you to specify header fields which you don't normally want to see. @@ -1506,9 +1641,7 @@ unignore organization organisation x-mailer: x-newsreader: x-mailing-list: unignore posted-to: - The Mutt Next Generation E-Mail Client 31 - - _3_._1_0 _A_l_t_e_r_n_a_t_i_v_e _a_d_d_r_e_s_s_e_s + _3_._1_1 _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 ... ] @@ -1517,7 +1650,7 @@ 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.4.233 , page 137).) + _$_r_e_p_l_y___t_o (section 7.4.246 , page 148).) 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 @@ -1536,7 +1669,11 @@ be removed. If the _r_e_g_e_x_p for unalternates is ``*'', _a_l_l _e_n_t_r_i_e_s on alternates will be removed. - _3_._1_1 _F_o_r_m_a_t _= _F_l_o_w_e_d + The Mutt Next Generation E-Mail Client 34 + + _3_._1_2 _F_o_r_m_a_t _= _F_l_o_w_e_d + + _3_._1_2_._1 _I_n_t_r_o_d_u_c_t_i_o_n Mutt-ng contains support for so-called format=flowed messages. In the begin- ning of email, each message had a fixed line width, and it was enough for dis- @@ -1551,14 +1688,14 @@ For introductory information on format=flowed messages, see . + _3_._1_2_._2 _R_e_c_e_i_v_i_n_g_: _D_i_s_p_l_a_y _S_e_t_u_p + When you receive emails that are marked as format=flowed messages, and is for- matted correctly, mutt-ng will try to reformat the message to optimally fit on your terminal. If you want a fixed margin on the right side of your terminal, you can set the following: - set wrapmargin = 10 - - The Mutt Next Generation E-Mail Client 32 + set wrapmargin = 10 The code above makes the line break 10 columns before the right side of the terminal. @@ -1566,50 +1703,86 @@ If your terminal is so wide that the lines are embarrassingly long, you can also set a maximum line length: - set max_line_length = 120 + set max_line_length = 120 The example above will give you lines not longer than 120 characters. When you view at format=flowed messages, you will often see the quoting hierar- chy like in the following example: - >Bill, can you please send last month's progress report to Mr. - >Morgan? We also urgently need the cost estimation for the new - >production server that we want to set up before our customer's - >project will go live. + >Bill, can you please send last month's progress report to Mr. + >Morgan? We also urgently need the cost estimation for the new + >production server that we want to set up before our customer's + >project will go live. + + This obviously doesn't look very nice, and it makes it very hard to + + The Mutt Next Generation E-Mail Client 35 - This obviously doesn't look very nice, and it makes it very hard to differenti- - ate between text and quoting character. The solution is to configure mutt-ng to - "stuff" the quoting: + differentiate between text and quoting character. The solution is to configure + mutt-ng to "stuff" the quoting: - set stuff_quoted + set stuff_quoted This will lead to a nicer result that is easier to read: - > Bill, can you please send last month's progress report to Mr. - > Morgan? We also urgently need the cost estimation for the new - > production server that we want to set up before our customer's - > project will go live. + > Bill, can you please send last month's progress report to Mr. + > Morgan? We also urgently need the cost estimation for the new + > production server that we want to set up before our customer's + > project will go live. + + _3_._1_2_._3 _S_e_n_d_i_n_g If you want mutt-ng to send emails with format=flowed set, you need to explic- itly set it: - set text_flowed + set text_flowed Additionally, you have to use an editor which supports writing format=flowed- conforming emails. For vim, this is done by adding w to the formatoptions (see :h formatoptions and :h fo-table) when writing emails. - _3_._1_2 _M_a_i_l_i_n_g _l_i_s_t_s + Also note that _f_o_r_m_a_t_=_f_l_o_w_e_d knows about ``space-stuffing'', that is, when + sending messages, some kinds of lines have to be indented with a single space + on the sending side. On the receiving side, the first space (if any) is + removed. As a consequence and in addition to the above simple setting, please + keep this in mind when making manual formattings within the editor. Also note + that mutt-ng currently violates the standard (RfC 3676) as it does not space- + stuff lines starting with: - The Mutt Next Generation E-Mail Client 33 + +o > This is _n_o_t the quote character but a right angle used for other reasons + + +o From with a trailing space. + + +o just a space for formatting reasons + + Please make sure that you manually prepend a space to each of them. + + _3_._1_2_._4 _A_d_d_i_t_i_o_n_a_l _N_o_t_e_s + + " + + For completeness, the _$_d_e_l_e_t_e___s_p_a_c_e (section 7.4.51 , page 100) variable pro- + vides the mechanism to generate a DelSp=yes parameter on _o_u_t_g_o_i_n_g messages. + + The Mutt Next Generation E-Mail Client 36 + + According to the standard, clients receiving a format=flowed messages should + delete the last space of a flowed line but still interpret the line as flowed. + Because flowed lines usually contain only one space at the end, this parameter + would make the receiving client concatenate the last word of the previous with + the first of the current line _w_i_t_h_o_u_t a space. This makes ordinary text unread- + able and is intended for languages rarely using spaces. So please use this set- + ting only if you're sure what you're doing. + + _3_._1_3 _M_a_i_l_i_n_g _l_i_s_t_s Usage: [un]lists _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] Usage: [un]subscribe _r_e_g_e_x_p [ _r_e_g_e_x_p ... ] 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.10 , - page 57). In order to take advantage of them, you must specify which addresses + page 60). 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.5.4 , page 12) function will work for all known lists. Additionally, when you send a message to a sub- @@ -1618,7 +1791,7 @@ the 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 per- sonal CCs of list messages. Also note that the generation of the Mail-Fol- - lowup-To header is controlled by the _$_f_o_l_l_o_w_u_p___t_o (section 6.4.66 , page 96) + lowup-To header is controlled by the _$_f_o_l_l_o_w_u_p___t_o (section 7.4.72 , page 105) configuration variable. More precisely, Mutt-ng maintains lists of patterns for the addresses of known @@ -1647,7 +1820,9 @@ To remove a mailing list from the list of subscribed mailing lists, but keep it on the list of known mailing lists, use ``unsubscribe''. - _3_._1_3 _U_s_i_n_g _M_u_l_t_i_p_l_e _s_p_o_o_l _m_a_i_l_b_o_x_e_s + The Mutt Next Generation E-Mail Client 37 + + _3_._1_4 _U_s_i_n_g _M_u_l_t_i_p_l_e _s_p_o_o_l _m_a_i_l_b_o_x_e_s Usage: mbox-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x @@ -1656,12 +1831,10 @@ regular expression specifying the mailbox to treat as a ``spool'' mailbox and _m_a_i_l_b_o_x specifies where mail should be saved when read. - The Mutt Next Generation E-Mail Client 34 - Unlike some of the other _h_o_o_k commands, only the _f_i_r_s_t matching pattern is used (it is not possible to save read mail in more than a single mailbox). - _3_._1_4 _D_e_f_i_n_i_n_g _m_a_i_l_b_o_x_e_s _w_h_i_c_h _r_e_c_e_i_v_e _m_a_i_l + _3_._1_5 _D_e_f_i_n_i_n_g _m_a_i_l_b_o_x_e_s _w_h_i_c_h _r_e_c_e_i_v_e _m_a_i_l Usage: [un]mailboxes [!]_f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] @@ -1687,11 +1860,11 @@ 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.9 , page - 56) (such as ``='' and ``!''), any variable definition that affect these char- - acters (like _$_f_o_l_d_e_r (section 6.4.64 , page 95) and _$_s_p_o_o_l_f_i_l_e (section - 6.4.297 , page 152)) should be executed before the mailboxes command. + 60) (such as ``='' and ``!''), any variable definition that affect these char- + acters (like _$_f_o_l_d_e_r (section 7.4.70 , page 104) and _$_s_p_o_o_l_f_i_l_e (section + 7.4.310 , page 163)) should be executed before the mailboxes command. - _3_._1_5 _U_s_e_r _d_e_f_i_n_e_d _h_e_a_d_e_r_s + _3_._1_6 _U_s_e_r _d_e_f_i_n_e_d _h_e_a_d_e_r_s Usage: @@ -1699,6 +1872,8 @@ unmy_hdr _f_i_e_l_d [ _f_i_e_l_d ... ] + The Mutt Next Generation E-Mail Client 38 + The ``my_hdr'' command allows you to create your own header fields which will be added to every message you send. @@ -1707,8 +1882,6 @@ my_hdr Organization: A Really Big Company, Anytown, USA - The Mutt Next Generation E-Mail Client 35 - in your .muttrc. NNoottee:: space characters are _n_o_t allowed between the keyword and the colon @@ -1716,7 +1889,7 @@ 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.4.54 , page 93) variable, or use the _e_d_i_t_- + set the _e_d_i_t___h_e_a_d_e_r_s (section 7.4.59 , page 102) 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. @@ -1727,7 +1900,7 @@ unmy_hdr to cc - _3_._1_6 _D_e_f_i_n_i_n_g _t_h_e _o_r_d_e_r _o_f _h_e_a_d_e_r_s _w_h_e_n _v_i_e_w_i_n_g _m_e_s_s_a_g_e_s + _3_._1_7 _D_e_f_i_n_i_n_g _t_h_e _o_r_d_e_r _o_f _h_e_a_d_e_r_s _w_h_e_n _v_i_e_w_i_n_g _m_e_s_s_a_g_e_s Usage: hdr_order _h_e_a_d_e_r_1 _h_e_a_d_e_r_2 _h_e_a_d_e_r_3 @@ -1739,55 +1912,55 @@ hdr_order From Date: From: To: Cc: Subject: - _3_._1_7 _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 + _3_._1_8 _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 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- sages. _f_i_l_e_n_a_m_e will be used as the default filename if the message is _F_r_o_m_: + + The Mutt Next Generation E-Mail Client 39 + an address matching _r_e_g_e_x_p or if you are the author and the message is addressed _t_o_: something matching _r_e_g_e_x_p. - 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.5.1 , page 53) for information on the + 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.5.1 , page 57) for information on the exact format of _p_a_t_t_e_r_n. Examples: save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins - - The Mutt Next Generation E-Mail Client 36 - save-hook aol\\.com$ +spam - Also see the _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.19 , page 36) command. + Also see the _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.20 , page 39) command. - _3_._1_8 _S_p_e_c_i_f_y _d_e_f_a_u_l_t _F_c_c_: _m_a_i_l_b_o_x _w_h_e_n _c_o_m_p_o_s_i_n_g + _3_._1_9 _S_p_e_c_i_f_y _d_e_f_a_u_l_t _F_c_c_: _m_a_i_l_b_o_x _w_h_e_n _c_o_m_p_o_s_i_n_g 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.4.230 , page 136). Mutt-ng searches the initial list of message + (section 7.4.243 , page 147). 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.4.230 , page 136) mailbox. + 7.4.243 , page 147) 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.5.1 , page 53) for information on the + 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.5.1 , page 57) for information on the exact format of _p_a_t_t_e_r_n. Example: fcc-hook [@.]aol\\.com$ +spammers The above will save a copy of all messages going to the aol.com domain to the - `+spammers' mailbox by default. Also see the _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.19 , - page 36) command. + `+spammers' mailbox by default. Also see the _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.20 , + page 39) command. - _3_._1_9 _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 _a_n_d _d_e_f_a_u_l_t _F_c_c_: _m_a_i_l_b_o_x _a_t _o_n_c_e + _3_._2_0 _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 _a_n_d _d_e_f_a_u_l_t _F_c_c_: _m_a_i_l_b_o_x _a_t _o_n_c_e Usage: fcc-save-hook [!]_p_a_t_t_e_r_n _m_a_i_l_b_o_x This command is a shortcut, equivalent to doing both a _f_c_c_-_h_o_o_k (section - 3.18 , page 35) and a _s_a_v_e_-_h_o_o_k (section 3.17 , page 35) with its arguments. + 3.19 , page 39) and a _s_a_v_e_-_h_o_o_k (section 3.18 , page 38) with its arguments. - _3_._2_0 _C_h_a_n_g_e _s_e_t_t_i_n_g_s _b_a_s_e_d _u_p_o_n _m_e_s_s_a_g_e _r_e_c_i_p_i_e_n_t_s + _3_._2_1 _C_h_a_n_g_e _s_e_t_t_i_n_g_s _b_a_s_e_d _u_p_o_n _m_e_s_s_a_g_e _r_e_c_i_p_i_e_n_t_s Usage: reply-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d @@ -1795,6 +1968,8 @@ Usage: send2-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d + The Mutt Next Generation E-Mail Client 40 + These commands can be used to execute arbitrary configuration commands based 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 @@ -1805,26 +1980,24 @@ and _r_e_p_l_i_e_s. NNoottee:: reply-hooks are matched bbeeffoorree the send-hook, rreeggaarrddlleessss of the order specified in the users's configuration file. - The Mutt Next Generation E-Mail Client 37 - 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.4.247 , page 140) variable depending on the message's + _$_s_e_n_d_m_a_i_l (section 7.4.260 , page 151) variable depending on the message's sender address. For each type of send-hook or reply-hook, when multiple matches occur, commands are executed in the order they are specified in the muttrc (for that type of hook). - See _M_e_s_s_a_g_e _M_a_t_c_h_i_n_g _i_n _H_o_o_k_s (section 4.5.1 , page 53) for information on the + 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.5.1 , page 57) for information on the exact format of _p_a_t_t_e_r_n. 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.4.15 , page 85), _$_s_i_g_n_a_t_u_r_e (section 6.4.259 , page 143) and - _$_l_o_c_a_l_e (section 6.4.114 , page 109) variables in order to change the language + _t_i_o_n (section 7.4.18 , page 93), _$_s_i_g_n_a_t_u_r_e (section 7.4.272 , page 154) and + _$_l_o_c_a_l_e (section 7.4.120 , page 119) 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 @@ -1833,7 +2006,7 @@ ify recipient headers, or the message's subject, don't have any effect on the current message when executed from a send-hook. - _3_._2_1 _C_h_a_n_g_e _s_e_t_t_i_n_g_s _b_e_f_o_r_e _f_o_r_m_a_t_t_i_n_g _a _m_e_s_s_a_g_e + _3_._2_2 _C_h_a_n_g_e _s_e_t_t_i_n_g_s _b_e_f_o_r_e _f_o_r_m_a_t_t_i_n_g _a _m_e_s_s_a_g_e Usage: message-hook [!]_p_a_t_t_e_r_n _c_o_m_m_a_n_d @@ -1843,49 +2016,49 @@ tiple matches occur, commands are executed in the order they are specified in the muttrc. - 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.5.1 , page 53) for information on the + 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.5.1 , page 57) for information on the exact format of _p_a_t_t_e_r_n. Example: message-hook ~A 'set pager=builtin' - message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""' - _3_._2_2 _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 + The Mutt Next Generation E-Mail Client 41 - Usage: crypt-hook _p_a_t_t_e_r_n _k_e_y_i_d + message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject: .*\""' - When encrypting messages with PGP or OpenSSL, you may want to associate a + _3_._2_3 _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 - The Mutt Next Generation E-Mail Client 38 + Usage: crypt-hook _p_a_t_t_e_r_n _k_e_y_i_d - certain key with a given e-mail address automatically, either because the - recipient's public key can't be deduced from the destination address, or - because, for 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. + 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-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. - _3_._2_3 _A_d_d_i_n_g _k_e_y _s_e_q_u_e_n_c_e_s _t_o _t_h_e _k_e_y_b_o_a_r_d _b_u_f_f_e_r + _3_._2_4 _A_d_d_i_n_g _k_e_y _s_e_q_u_e_n_c_e_s _t_o _t_h_e _k_e_y_b_o_a_r_d _b_u_f_f_e_r Usage: push _s_t_r_i_n_g This command adds the named string to the keyboard buffer. The string may con- tain control characters, key names and function names like the sequence string - in the _m_a_c_r_o (section 3.7 , page 27) command. You may use it to automatically + in the _m_a_c_r_o (section 3.8 , page 29) command. You may use it to automatically run a sequence of commands at startup, or when entering certain folders. - _3_._2_4 _E_x_e_c_u_t_i_n_g _f_u_n_c_t_i_o_n_s + _3_._2_5 _E_x_e_c_u_t_i_n_g _f_u_n_c_t_i_o_n_s 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.5 , page 165). ``exec function'' is equivalent + _f_u_n_c_t_i_o_n _r_e_f_e_r_e_n_c_e (section 7.5 , page 175). ``exec function'' is equivalent to ``push ''. - _3_._2_5 _M_e_s_s_a_g_e _S_c_o_r_i_n_g + _3_._2_6 _M_e_s_s_a_g_e _S_c_o_r_i_n_g Usage: score _p_a_t_t_e_r_n _v_a_l_u_e @@ -1897,6 +2070,8 @@ that you aren't interested in deleted. For this purpose, mutt-ng features a mechanism called ``scoring''. + The Mutt Next Generation E-Mail Client 42 + When you use scoring, every message has a base score of 0. You can then use the score command to define patterns and a positive or negative value associated with it. When a pattern matches a message, the message's score will be raised @@ -1905,8 +2080,6 @@ score "~f nion@muttng\.org" 50 score "~f @sco\.com" -100 - The Mutt Next Generation E-Mail Client 39 - If the pattern matches, it is also possible to set the score value of the cur- rent message to a certain value and then stop evaluation: @@ -1928,24 +2101,26 @@ delete threshold, it will be marked as deleted. These three thresholds can be set via the variables _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___f_l_a_g (sec- - tion 6.4.244 , page 140), _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 6.4.245 , page 140), - _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e (section 6.4.243 , page 140) and. By default, - _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 6.4.245 , page 140) and _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e - (section 6.4.243 , page 140) are set to -1, which means that in the default + tion 7.4.257 , page 150), _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 7.4.258 , page 151), + _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e (section 7.4.256 , page 150) and. By default, + _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___r_e_a_d (section 7.4.258 , page 151) and _$_s_c_o_r_e___t_h_r_e_s_h_o_l_d___d_e_l_e_t_e + (section 7.4.256 , page 150) are set to -1, which means that in the default threshold configuration no message will ever get marked as read or deleted. Scoring gets especially interesting when combined with the color command and the ~n pattern: - color black yellow "~n 10-" - color red yellow "~n 100-" + color index black yellow "~n 10-" + color index red yellow "~n 100-" The rules above mark all messages with a score between 10 and 99 with black and yellow, and messages with a score greater or equal 100 with red and yellow. This might be unusual to you if you're used to e.g. slrn's scoring mechanism, but it is more flexible, as it visually marks different scores. - _3_._2_6 _S_p_a_m _d_e_t_e_c_t_i_o_n + The Mutt Next Generation E-Mail Client 43 + + _3_._2_7 _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 @@ -1955,10 +2130,7 @@ 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 Mutt Next Generation E-Mail Client 40 - - the %H selector in the _$_i_n_d_e_x___f_o_r_m_a_t (section 6.4.110 , page 106) variable. + the %H selector in the _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115) variable. (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a given message.) @@ -2002,6 +2174,8 @@ 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 Next Generation E-Mail Client 44 + 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. @@ -2011,9 +2185,6 @@ mutt will sort numerically first, and lexically only when two numbers are equal in value. (This is like UNIX's sort -n.) A message with no spam attributes at all -- that is, one that didn't match _a_n_y of your spam patterns -- is sorted at - - The Mutt Next Generation E-Mail Client 41 - lowest priority. Numbers are sorted next, beginning with 0 and ranging upward. Finally, non-numeric strings are sorted, with ``a'' taking lower priority than ``z''. Clearly, in general, sorting by spam tags is most effective when you can @@ -2039,7 +2210,7 @@ spam "^From: .*MAILER-DAEMON" "999" - _3_._2_7 _S_e_t_t_i_n_g _v_a_r_i_a_b_l_e_s + _3_._2_8 _S_e_t_t_i_n_g _v_a_r_i_a_b_l_e_s Usage: set [no|inv]_v_a_r_i_a_b_l_e[=_v_a_l_u_e] [ _v_a_r_i_a_b_l_e ... ] @@ -2049,12 +2220,15 @@ 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.4 , - page 81). There are four basic types of variables: boolean, number, string and + 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 7.4 , + page 87). 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. _s_t_r_i_n_g variables consist of any number of printable characters. _s_t_r_i_n_g_s must + + The Mutt Next Generation E-Mail Client 45 + 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. @@ -2065,8 +2239,6 @@ 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.'' - The Mutt Next Generation E-Mail Client 42 - Prefixing a variable with ``no'' will unset it. Example: set noaskbcc. For _b_o_o_l_e_a_n variables, you may optionally prefix the variable name with inv to @@ -2094,7 +2266,7 @@ With the reset command there exists the special variable ``all'', which allows you to reset all variables to their system defaults. - _3_._2_8 _R_e_a_d_i_n_g _i_n_i_t_i_a_l_i_z_a_t_i_o_n _c_o_m_m_a_n_d_s _f_r_o_m _a_n_o_t_h_e_r _f_i_l_e + _3_._2_9 _R_e_a_d_i_n_g _i_n_i_t_i_a_l_i_z_a_t_i_o_n _c_o_m_m_a_n_d_s _f_r_o_m _a_n_o_t_h_e_r _f_i_l_e Usage: source _f_i_l_e_n_a_m_e [ _f_i_l_e_n_a_m_e ... ] @@ -2108,21 +2280,20 @@ If the filename ends with a vertical bar (|), then _f_i_l_e_n_a_m_e is considered to be an executable program from which to read input (eg. source ~/bin/myscript|). - _3_._2_9 _R_e_m_o_v_i_n_g _h_o_o_k_s + The Mutt Next Generation E-Mail Client 46 + + _3_._3_0 _R_e_m_o_v_i_n_g _h_o_o_k_s Usage: unhook [ * | _h_o_o_k_-_t_y_p_e ] This command permits you to flush hooks you have previously defined. You can either remove all hooks by giving the ``*'' character as an argument, or you can remove all hooks of a specific type by saying something like unhook send- - - The Mutt Next Generation E-Mail Client 43 - hook. - _3_._3_0 _S_h_a_r_i_n_g _S_e_t_u_p_s + _3_._3_1 _S_h_a_r_i_n_g _S_e_t_u_p_s - _3_._3_0_._1 _C_h_a_r_a_c_t_e_r _S_e_t_s + _3_._3_1_._1 _C_h_a_r_a_c_t_e_r _S_e_t_s As users may run mutt-ng on different systems, the configuration must be main- tained because it's likely that people want to use the setup everywhere they @@ -2144,7 +2315,7 @@ while, again, replacing the dots with the appropriate name. This tells vim as which character set to read and save the file. - _3_._3_0_._2 _M_o_d_u_l_a_r_i_z_a_t_i_o_n + _3_._3_1_._2 _M_o_d_u_l_a_r_i_z_a_t_i_o_n ``Modularization'' means to divide the setup into several files while sorting the options or commands by topic. Especially for longer setups (e.g. with many @@ -2153,7 +2324,9 @@ When using separation, setups may be, as a whole or in fractions, shared over different systems. - _3_._3_0_._3 _C_o_n_d_i_t_i_o_n_a_l _p_a_r_t_s + _3_._3_1_._3 _C_o_n_d_i_t_i_o_n_a_l _p_a_r_t_s + + The Mutt Next Generation E-Mail Client 47 When using a configuration on different systems, the user may not always have influence on how mutt-ng is installed and which features it includes. @@ -2161,8 +2334,6 @@ To solve this, mutt-ng contain a feature based on the ``ifdef'' patch written for mutt. Its basic syntax is: - The Mutt Next Generation E-Mail Client 44 - ifdef ifndef @@ -2196,21 +2367,20 @@ An example for testing for variable names can be used if users use different revisions of mutt-ng whereby the older one may not have a certain variable. To - test for the availability of _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 6.4.99 , page 104), + test for the availability of _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 7.4.105 , page 113), use: ifdef imap_mail_check 'set imap_mail_check = 300' Provided for completeness is the test for menu names. To set _$_p_a_g_e_r___i_n_d_e_x___l_i_n_e_s - (section 6.4.169 , page 122) only if the pager menu is available, use: + (section 7.4.182 , page 133) only if the pager menu is available, use: + + The Mutt Next Generation E-Mail Client 48 ifdef pager 'set pager_index_lines = 10' For completeness, too, the opposite of ifdef is provided: ifndef which only executes the command if the test fails. For example, the following two examples - - The Mutt Next Generation E-Mail Client 45 - are equivalent: ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses' @@ -2221,12 +2391,18 @@ ifdef feature_slang 'source ~/.mutt-ng/setup-slang' ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' + _3_._3_2 _O_b_s_o_l_e_t_e _V_a_r_i_a_b_l_e_s + + In the process of ensuring and creating more consistency, many variables have + been renamed and some of the old names were already removed. Please see _O_b_s_o_- + _l_e_t_e _V_a_r_i_a_b_l_e_s (section 7.4 , page 87) for a complete list. + _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 All string patterns in Mutt-ng including those in more complex _p_a_t_t_e_r_n_s (sec- - tion 6.2 , page 77) must be specified using regular expressions (regexp) in + tion 7.2 , page 83) 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. @@ -2241,6 +2417,9 @@ Note that the regular expression can be enclosed/delimited by either ' or ' which is useful if the regular expression includes a white-space character. + + The Mutt Next Generation E-Mail Client 49 + See _S_y_n_t_a_x _o_f _I_n_i_t_i_a_l_i_z_a_t_i_o_n _F_i_l_e_s (section 3.2 , page 21) for more informa- tion on ' and ' delimiter processing. To match a literal ' or ' you must pref- ace it with \ (backslash). @@ -2254,8 +2433,6 @@ sign ``$'' are metacharacters that respectively match the empty string at the beginning and end of a line. - The Mutt Next Generation E-Mail Client 46 - A list of characters enclosed by ``['' and ``]'' matches any single character in that list; if the first character of the list is a caret ``^'' then it matches any character nnoott in the list. For example, the regular expression @@ -2297,6 +2474,9 @@ [:punct:] Punctuation characters (characters that are not letter, digits, + + The Mutt Next Generation E-Mail Client 50 + control characters, or space characters). [:space:] @@ -2310,9 +2490,6 @@ A character class is only valid in a regular expression inside the brackets of a character list. Note that the brackets in these class names are part of the - - The Mutt Next Generation E-Mail Client 47 - symbolic names, and must be included in addition to the brackets delimiting the bracket list. For example, [[[[::ddiiggiitt::]]]] is equivalent to [[00--99]]. @@ -2355,6 +2532,8 @@ {,m} The preceding item is matched at most _m times. + The Mutt Next Generation E-Mail Client 51 + {n,m} The preceding item is matched at least _n times, but no more than _m times. @@ -2367,9 +2546,6 @@ ing regular expression matches any string matching either subexpression. Repetition takes precedence over concatenation, which in turn takes precedence - - The Mutt Next Generation E-Mail Client 48 - over alternation. A whole subexpression may be enclosed in parentheses to override these precedence rules. @@ -2410,8 +2586,11 @@ Mutt-ng's pattern language provides a simple yet effective way to set up rules to match messages, e.g. for operations like tagging and scoring. A pattern con- sists of one or more sub-pattern, which can be logically grouped, ORed, and + + The Mutt Next Generation E-Mail Client 52 + negated. For a complete listing of these patterns, please refer to table _P_a_t_- - _t_e_r_n_s (section 6.2 , page 77) in the Reference chapter. + _t_e_r_n_s (section 7.2 , page 83) in the Reference chapter. It must be noted that in this table, EXPR, USER, ID and SUBJECT are regular expressions. For ranges, the forms <[MAX], >>[MIN], [MIN]- and -[MAX] are also @@ -2423,8 +2602,6 @@ most simple possibility is to logically AND several patterns by stringing them together: - The Mutt Next Generation E-Mail Client 49 - ~s 'SPAM' ~U The pattern above matches all messages that contain ``SPAM'' in the subject and @@ -2461,6 +2638,9 @@ ~d 01/01/2005+1y ~d 18/10/2004-2w + + The Mutt Next Generation E-Mail Client 53 + ~d 28/12/2004*1d The first pattern matches all dates between January 1st, 2005 and January 1st @@ -2472,8 +2652,6 @@ date ranges between a fixed number of units and the current date. How this works can be seen in the following example: - The Mutt Next Generation E-Mail Client 50 - ~d >2w # messages older than two weeks ~d <3d # messages newer than 3 days ~d =1m # messages that are exactly one month old @@ -2498,7 +2676,7 @@ +o the current mutt-ng version number The setting for the status bar of the index is controlled via the _$_s_t_a_t_u_s___f_o_r_- - _m_a_t (section 6.4.308 , page 155) variable. For the hostname and version + _m_a_t (section 7.4.321 , page 165) variable. For the hostname and version string, there's an expando for $status_format: %h expands to the hostname and %v to the version string. When just configuring: @@ -2510,6 +2688,8 @@ Mutt-ng 1.5.9i on mailhost: ... + The Mutt Next Generation E-Mail Client 54 + In the index, there're more useful information one could want to see: +o which mailbox is open @@ -2520,8 +2700,6 @@ To include the mailbox' name is as easy as: - The Mutt Next Generation E-Mail Client 51 - set status_format = "%v on %h: %B: ... When the currently opened mailbox is Inbox, this will be expanded to: @@ -2556,6 +2734,8 @@ This is achieved by the following syntax for those expandos which may be printed nonzero: + The Mutt Next Generation E-Mail Client 55 + %??&? Using this we can make mutt-ng to do the following: @@ -2565,8 +2745,6 @@ +o and make it print ``no new messages'' if there aren't any - The Mutt Next Generation E-Mail Client 52 - The corresponding configuration is: set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ... @@ -2603,6 +2781,9 @@ %>X Since the previous expando stops at the end of line, there must be + + The Mutt Next Generation E-Mail Client 56 + a way to fill the gap between two items via the %>X expando: it puts as many characters X in between two items so that the rest of the line will be right-justified. For example, to not put the ver- @@ -2612,8 +2793,6 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" - The Mutt Next Generation E-Mail Client 53 - _4_._4 _U_s_i_n_g _T_a_g_s Sometimes it is desirable to perform an operation on a group of messages all at @@ -2622,17 +2801,17 @@ 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 6.2 , page 77) for Mutt-ng's pattern matching + default. See _p_a_t_t_e_r_n_s (section 7.2 , page 83) 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.4.16 , - page 85) variable is set, the next operation applies to the tagged messages + that operation can be used in that manner. If the _$_a_u_t_o___t_a_g (section 7.4.19 , + page 93) 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.7 , page 27) or _p_u_s_h (section 3.23 , page 37) commands, + In _m_a_c_r_o_s (section 3.8 , page 29) or _p_u_s_h (section 3.24 , page 41) 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-ng will stop "eating" the macro when it encounters the ``end-cond'' operator; after @@ -2644,31 +2823,30 @@ 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-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 44) or _p_a_t_t_e_r_n (section 6.2 , page 77) along + _e_x_p_r_e_s_s_i_o_n (section 4.1 , page 48) or _p_a_t_t_e_r_n (section 7.2 , page 83) along with a configuration option/command. See - +o _f_o_l_d_e_r_-_h_o_o_k (section 3.6 , page 26) + +o _f_o_l_d_e_r_-_h_o_o_k (section 3.7 , page 29) - +o _s_e_n_d_-_h_o_o_k (section 3.20 , page 36) + +o _s_e_n_d_-_h_o_o_k (section 3.21 , page 39) + + The Mutt Next Generation E-Mail Client 57 - +o _m_e_s_s_a_g_e_-_h_o_o_k (section 3.21 , page 37) + +o _m_e_s_s_a_g_e_-_h_o_o_k (section 3.22 , page 40) - +o _s_a_v_e_-_h_o_o_k (section 3.17 , page 35) + +o _s_a_v_e_-_h_o_o_k (section 3.18 , page 38) - +o _m_b_o_x_-_h_o_o_k (section 3.13 , page 33) + +o _m_b_o_x_-_h_o_o_k (section 3.14 , page 37) - +o _f_c_c_-_h_o_o_k (section 3.18 , page 35) + +o _f_c_c_-_h_o_o_k (section 3.19 , page 39) - +o _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.19 , page 36) + +o _f_c_c_-_s_a_v_e_-_h_o_o_k (section 3.20 , page 39) for specific details on each type of _h_o_o_k available. NNoottee:: if a hook changes configuration settings, these changes remain effective until the end of the current mutt session. As this is generally not desired, a default hook needs to be added before all other hooks to restore configuration - - The Mutt Next Generation E-Mail Client 54 - defaults. Here is an example with send-hook and the my_hdr directive: send-hook . 'unmy_hdr From:' @@ -2678,11 +2856,11 @@ Hooks that act upon messages (send-hook, save-hook, fcc-hook, message-hook) are evaluated in a slightly different manner. For the other types of hooks, a _r_e_g_- - _u_l_a_r _e_x_p_r_e_s_s_i_o_n (section 4.1 , page 44) is sufficient. But in dealing with + _u_l_a_r _e_x_p_r_e_s_s_i_o_n (section 4.1 , page 48) is sufficient. But in dealing with messages a finer grain of control is needed for matching since for different purposes you want to match different criteria. - Mutt-ng allows the use of the _s_e_a_r_c_h _p_a_t_t_e_r_n (section 6.2 , page 77) language + Mutt-ng allows the use of the _s_e_a_r_c_h _p_a_t_t_e_r_n (section 7.2 , page 83) 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 @@ -2699,9 +2877,11 @@ 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-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.4.45 , page 91) 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.4.45 , page 91) that is in - effect at that time will be used. + 7.4.49 , page 100) 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 7.4.49 , page 100) that is + in effect at that time will be used. + + The Mutt Next Generation E-Mail Client 58 _4_._6 _U_s_i_n_g _t_h_e _s_i_d_e_b_a_r @@ -2715,8 +2895,6 @@ If you want to specify the mailboxes you can do so with: - The Mutt Next Generation E-Mail Client 55 - set mbox='=INBOX' mailboxes INBOX \ MBOX1 \ @@ -2752,20 +2930,19 @@ You can then go up and down by pressing Ctrl-P and Ctrl-N, and switch on and off the sidebar simply by pressing 'B'. + The Mutt Next Generation E-Mail Client 59 + _4_._7 _E_x_t_e_r_n_a_l _A_d_d_r_e_s_s _Q_u_e_r_i_e_s 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.4.221 , page 134) vari- + simple interface. Using the _$_q_u_e_r_y___c_o_m_m_a_n_d (section 7.4.234 , page 145) vari- able, you specify the wrapper command to use. For example: set query_command = "mutt_ldap_query.pl '%s'" The wrapper script should accept the query on the command-line. It should return a one line message, then each matching response on a single line, each - - The Mutt Next Generation E-Mail Client 56 - line containing a tab separated address then name then some other optional information. On error, or if there are no matching addresses, return a non- zero exit code and a one line error message. @@ -2798,12 +2975,14 @@ 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-ng - uses the default specified with the _$_m_b_o_x___t_y_p_e (section 6.4.125 , page 112) + uses the default specified with the _$_m_b_o_x___t_y_p_e (section 7.4.132 , page 121) 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: + The Mutt Next Generation E-Mail Client 60 + From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST to denote the start of a new message (this is often referred to as the @@ -2815,9 +2994,6 @@ 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-ng - - The Mutt Next Generation E-Mail Client 57 - 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 @@ -2835,12 +3011,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.4.297 , page 152) (incoming) + +o ! -- refers to your _$_s_p_o_o_l_f_i_l_e (section 7.4.310 , page 163) (incoming) mailbox - +o > -- refers to your _$_m_b_o_x (section 6.4.124 , page 111) file + +o > -- refers to your _$_m_b_o_x (section 7.4.131 , page 121) file - +o < -- refers to your _$_r_e_c_o_r_d (section 6.4.230 , page 136) file + +o < -- refers to your _$_r_e_c_o_r_d (section 7.4.243 , page 147) file +o ^ -- refers to the current mailbox @@ -2848,29 +3024,29 @@ +o ~ -- refers to your home directory - +o = or + -- refers to your _$_f_o_l_d_e_r (section 6.4.64 , page 95) directory + +o = or + -- refers to your _$_f_o_l_d_e_r (section 7.4.70 , page 104) 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.17 , page 35) as + +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.18 , page 38) as determined by the address of the alias _4_._1_0 _H_a_n_d_l_i_n_g _M_a_i_l_i_n_g _L_i_s_t_s Mutt-ng has a few configuration options that make dealing with large amounts of + + The Mutt Next Generation E-Mail Client 61 + 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.12 , page 32) commands in your muttrc. + (section 3.13 , page 36) commands in your muttrc. Now that Mutt-ng knows what your mailing lists are, it can do several things, the first of which is the ability to show the name of a list through which you received a message (i.e., of a subscribed list) in the _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.4.110 , page 106) variable, the escape + box. In the _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115) variable, the escape ``%L'' will return the string ``To '' when ``list'' appears in the ``To'' - - The Mutt Next Generation E-Mail Client 58 - field, and ``Cc '' when it appears in the ``Cc'' field (otherwise it returns the name of the author). @@ -2884,7 +3060,7 @@ 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.4.66 , page 96) option is set, mutt will + and if the _$_f_o_l_l_o_w_u_p___t_o (section 7.4.72 , page 105) 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 @@ -2894,7 +3070,7 @@ 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.4.88 , page 101) configuration variable is set. Using list-reply + (section 7.4.94 , page 110) 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. @@ -2907,30 +3083,29 @@ 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 address given in the ``Reply-To'' field. Mutt-ng uses the _$_r_e_p_l_y___t_o (section - 6.4.233 , page 137) variable to help decide which address to use. If set to + 7.4.246 , page 148) 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 will be used when present. + The Mutt Next Generation E-Mail Client 62 + 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.4.110 , page 106) variable's ``%y'' and ``%Y'' + _$_i_n_d_e_x___f_o_r_m_a_t (section 7.4.116 , page 115) 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 easily be inserted by procmail and other mail filtering agents. - Lastly, Mutt-ng has the ability to _s_o_r_t (section 6.4.291 , page 150) the mail- + Lastly, Mutt-ng has the ability to _s_o_r_t (section 7.4.304 , page 161) the mail- box into _t_h_r_e_a_d_s (section 2.5.3 , page 11). 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 - - The Mutt Next Generation E-Mail Client 59 - - graphically. If you've ever used a threaded news client, this is the same con- - cept. It makes dealing with large volume mailing lists easier because you can - easily delete uninteresting threads and quickly find topics of value. + 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_1 _E_d_i_t_i_n_g _t_h_r_e_a_d_s @@ -2967,6 +3142,8 @@ Users can make use of it in one of the following two ways: + The Mutt Next Generation E-Mail Client 63 + +o 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. @@ -2975,12 +3152,10 @@ To support this, there are two variables: - +o _$_d_s_n___n_o_t_i_f_y (section 6.4.51 , page 92) is used to request receipts for + +o _$_d_s_n___n_o_t_i_f_y (section 7.4.56 , page 101) is used to request receipts for different results (such as failed message, message delivered, etc.). - The Mutt Next Generation E-Mail Client 60 - - +o _$_d_s_n___r_e_t_u_r_n (section 6.4.52 , page 93) requests how much of your message + +o _$_d_s_n___r_e_t_u_r_n (section 7.4.57 , page 102) requests how much of your message should be returned with the receipt (headers or full message). Please see the reference chapter for possible values. @@ -3002,7 +3177,7 @@ Polling for new mail is more expensive over POP3 than locally. For this reason 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.4.208 , page 132) variable, which defaults + by the _$_p_o_p___m_a_i_l___c_h_e_c_k (section 7.4.221 , page 142) variable, which defaults to every 60 seconds. If Mutt-ng was compiled with SSL support (by running the _c_o_n_f_i_g_u_r_e script with @@ -3012,13 +3187,15 @@ 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.4.206 , page 131), fetch all your - new mail and place it in the local _s_p_o_o_l_f_i_l_e (section 6.4.297 , page 152). + It allows to connect to _p_o_p___h_o_s_t (section 7.4.219 , page 142), fetch all your + new mail and place it in the local _s_p_o_o_l_f_i_l_e (section 7.4.310 , page 163). 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 + The Mutt Next Generation E-Mail Client 64 + _4_._1_4 _I_M_A_P _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) If Mutt-ng was compiled with IMAP support (by running the _c_o_n_f_i_g_u_r_e script with @@ -3030,9 +3207,6 @@ 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 imap://imapserver/path/to/folder where path/to/folder is the path of the folder - - The Mutt Next Generation E-Mail Client 61 - you want to access. You can select an alternative port by specifying it with the server, i.e.: @@ -3056,12 +3230,12 @@ 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.4.97 , page 103) vari- - able. + command. See also the _$_i_m_a_p___l_i_s_t___s_u_b_s_c_r_i_b_e_d (section 7.4.103 , page 113) + variable. 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.4.99 , page 104) and - _$_t_i_m_e_o_u_t (section 6.4.321 , page 160) variables. + want to carefully tune the _$_i_m_a_p___m_a_i_l___c_h_e_c_k (section 7.4.105 , page 113) and + _$_t_i_m_e_o_u_t (section 7.4.334 , page 170) 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 @@ -3077,7 +3251,9 @@ sages and subfolders. On Cyrus-like servers folders will often contain both messages and subfolders. - +o For the case where an entry can contain both messages and subfolders, the + The Mutt Next Generation E-Mail Client 65 + + +o For the case where an entry can contain both messages and subfolders, the selection key (bound to enter by default) will choose to descend into the subfolder view. If you wish to view the messages in that folder, you must use view-file instead (bound to space by default). @@ -3087,8 +3263,6 @@ respectively). You may also subscribe and unsubscribe to mailboxes (nor- mally these are bound to s and u, respectively). - The Mutt Next Generation E-Mail Client 62 - _4_._1_4_._2 _A_u_t_h_e_n_t_i_c_a_t_i_o_n Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI, @@ -3111,15 +3285,15 @@ There are a few variables which control authentication: - +o _$_i_m_a_p___u_s_e_r (section 6.4.105 , page 105) - controls the username under + +o _$_i_m_a_p___u_s_e_r (section 7.4.111 , page 114) - 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.4.100 , page 104) - a password which you may pre- + +o _$_i_m_a_p___p_a_s_s (section 7.4.106 , page 113) - a password which you may pre- set, 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.4.91 , page 102) - a colon-delimited list + +o _$_i_m_a_p___a_u_t_h_e_n_t_i_c_a_t_o_r_s (section 7.4.97 , page 111) - 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). @@ -3130,9 +3304,12 @@ newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup'' function from the index/pager which is by default bound to i. - The Default newsserver can be obtained from the $NNTPSERVER environment vari- - able. Like other news readers, info about subscribed newsgroups is saved in a - file as specified by the _$_n_n_t_p___n_e_w_s_r_c (section 6.4.156 , page 119) variable. + The Default newsserver can be obtained from the $NNTPSERVER environment + + The Mutt Next Generation E-Mail Client 66 + + variable. Like other news readers, info about subscribed newsgroups is saved in + a file as specified by the _$_n_n_t_p___n_e_w_s_r_c (section 7.4.169 , page 130) variable. Article headers are cached and can be loaded from a file when a newsgroup is entered instead loading from newsserver; currently, this caching mechanism still is different from the header caching for maildir/IMAP. @@ -3141,11 +3318,8 @@ Especially for Usenet, people often ask for advanced filtering and scoring functionality. Of course, mutt-ng has scoring and allows a killfile, too. How - - The Mutt Next Generation E-Mail Client 63 - - to use a killfile has been discussed in _M_e_s_s_a_g_e _s_c_o_r_i_n_g (section 3.25 , page - 38). + to use a killfile has been discussed in _M_e_s_s_a_g_e _s_c_o_r_i_n_g (section 3.26 , page + 41). What has not been discusses in detail is mutt-ng's built-in realname filter. For may newsreaders including those for ``advanced users'' like _s_l_r_n or _t_i_n, @@ -3178,32 +3352,33 @@ _4_._1_6 _S_M_T_P _S_u_p_p_o_r_t _(_O_P_T_I_O_N_A_L_) Mutt-ng can be built using a library called ``libESMTP'' which provides SMTP + + The Mutt Next Generation E-Mail Client 67 + functionality. When configure was called with --with-libesmtp or the output muttng -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP support includes support for Delivery Status Notification (see _D_e_l_i_v_e_r_y _S_t_a_t_u_s - _N_o_t_i_f_i_c_a_t_i_o_n (section 4.12 , page 58) section) as well as handling the 8BIT- - MIME flag controlled via _$_u_s_e___8_b_i_t_m_i_m_e (section 6.4.328 , page 161). + _N_o_t_i_f_i_c_a_t_i_o_n (section 4.12 , page 62) section) as well as handling the 8BIT- + MIME flag controlled via _$_u_s_e___8_b_i_t_m_i_m_e (section 7.4.341 , page 172). To enable sending mail directly via SMTP without an MTA such as Postfix or - SSMTP and the like, simply set the _$_s_m_t_p___h_o_s_t (section 6.4.286 , page 149) + SSMTP and the like, simply set the _$_s_m_t_p___h_o_s_t (section 7.4.299 , page 160) variable pointing to your SMTP server. - The Mutt Next Generation E-Mail Client 64 - - Authentication mechanisms are available via the _$_s_m_t_p___u_s_e_r (section 6.4.290 , - page 150) and _$_s_m_t_p___p_a_s_s (section 6.4.287 , page 149) variables. + Authentication mechanisms are available via the _$_s_m_t_p___u_s_e_r (section 7.4.303 , + page 161) and _$_s_m_t_p___p_a_s_s (section 7.4.300 , page 160) variables. Transport Encryption via the StartTLS command is also available. For this to work, first of all Mutt-ng must be built with SSL or GNUTLS. Secondly, the - _$_s_m_t_p___u_s_e___t_l_s (section 6.4.289 , page 150) variable must be either set to + _$_s_m_t_p___u_s_e___t_l_s (section 7.4.302 , page 161) variable must be either set to ``enabled'' or ``required.'' In both cases, StartTLS will be used if the server supports it: for the second case, the connection will fail if it doesn't while switching back to unencrypted communication for the first one. Some mail providers require user's to set a particular envelope sender, i.e. they allow for only one value which may not be what the user wants to send as - the From: header. In this case, the variable _$_s_m_t_p___e_n_v_e_l_o_p_e (section 6.4.285 , - page 149) may be used to set the envelope different from the From: header. + the From: header. In this case, the variable _$_s_m_t_p___e_n_v_e_l_o_p_e (section 7.4.298 , + page 160) may be used to set the envelope different from the From: header. _4_._1_7 _M_a_n_a_g_i_n_g _m_u_l_t_i_p_l_e _I_M_A_P_/_P_O_P_/_N_N_T_P _a_c_c_o_u_n_t_s _(_O_P_T_I_O_N_A_L_) @@ -3230,6 +3405,8 @@ macro index \cb |urlview\n macro pager \cb |urlview\n + The Mutt Next Generation E-Mail Client 68 + _4_._1_9 _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-ng was compiled with compressed folders support (by running the _c_o_n_f_i_g_- @@ -3237,8 +3414,6 @@ an arbitrary format, provided that the user has a script to convert from/to this format to one of the accepted. - The Mutt Next Generation E-Mail Client 65 - The most common use is to open compressed archived folders e.g. with gzip. In addition, the user can provide a script that gets a folder in an accepted @@ -3246,8 +3421,8 @@ may be faster than converting the entire folder to the accepted format, append- ing to it and converting back to the user-defined format. - There are three hooks defined (_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 64), _c_l_o_s_e_- - _h_o_o_k (section 4.19.2 , page 65) and _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 65)) + There are three hooks defined (_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 68), _c_l_o_s_e_- + _h_o_o_k (section 4.19.2 , page 69) and _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 69)) which define commands to uncompress and compress a folder and to append mes- sages to an existing compressed folder respectively. @@ -3258,17 +3433,17 @@ append-hook \\.gz$ "gzip -c %t >> %f" You do not have to specify all of the commands. If you omit _a_p_p_e_n_d_-_h_o_o_k (sec- - tion 4.19.3 , page 65), the folder will be open and closed again each time you - will add to it. If you omit _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 65) (or give + tion 4.19.3 , page 69), the folder will be open and closed again each time you + will add to it. If you omit _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 69) (or give 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.19.3 , page 65) though you'll be able to append to the folder. + _h_o_o_k (section 4.19.3 , page 69) though you'll be able to append to the folder. 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.4.240 , page 139), so that the compressed file + unset _$_s_a_v_e___e_m_p_t_y (section 7.4.253 , page 149), so that the compressed file will be removed if you delete all of the messages. _4_._1_9_._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 @@ -3284,6 +3459,9 @@ %f and %t can be repeated any number of times in the command string, and all of the entries are replaced with the appropriate folder name. In addition, %% is + + The Mutt Next Generation E-Mail Client 69 + replaced by %, as in printf, and any other %anything is left as is. The _c_o_m_m_a_n_d should nnoott remove the original compressed file. The _c_o_m_m_a_n_d should @@ -3291,8 +3469,6 @@ Example: - The Mutt Next Generation E-Mail Client 66 - 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. @@ -3302,12 +3478,12 @@ Usage: close-hook _r_e_g_e_x_p '_c_o_m_m_a_n_d' This is used to close the folder that was open with the _o_p_e_n_-_h_o_o_k (section - 4.19.1 , page 64) command after some changes were made to it. + 4.19.1 , page 68) command after some changes were made to it. The _c_o_m_m_a_n_d string is the command that can be used for closing 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.19.1 , page 64) command. Temporary folder in this case is the folder previ- - ously produced by the <_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 64) command. + 4.19.1 , page 68) command. Temporary folder in this case is the folder previ- + ously produced by the <_o_p_e_n_-_h_o_o_k (section 4.19.1 , page 68) command. The _c_o_m_m_a_n_d should nnoott remove the decompressed file. The _c_o_m_m_a_n_d should return non-zero exit status if it fails, so mutt knows something's wrong. @@ -3319,7 +3495,7 @@ If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type, and the file can only be open in the readonly mode. - _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 65) is not called when you exit from the + _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 69) is not called when you exit from the folder if the folder was not changed. _4_._1_9_._3 _A_p_p_e_n_d _a _m_e_s_s_a_g_e _t_o _a _c_o_m_p_r_e_s_s_e_d _m_a_i_l_b_o_x @@ -3328,7 +3504,7 @@ This command is used for saving to an existing compressed folder. The _c_o_m_m_a_n_d 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.19.1 , page 64) + _r_e_g_e_x_p. It has the same format as in the _o_p_e_n_-_h_o_o_k (section 4.19.1 , page 68) command. The temporary folder in this case contains the messages that are being appended. @@ -3337,23 +3513,22 @@ Example: + The Mutt Next Generation E-Mail Client 70 + append-hook \\.gz$ "gzip -c %t >> %f" - When _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 65) is used, the folder is not opened, + When _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 69) 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.4.125 , page 112)) type is always - - The Mutt Next Generation E-Mail Client 67 - + is. Thus the default (_$_m_b_o_x___t_y_p_e (section 7.4.132 , page 121)) type is always 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.19.2 , - page 65) is called, and not _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 65). _a_p_p_e_n_d_- - _h_o_o_k (section 4.19.3 , page 65) is only for appending to existing folders. + page 69) is called, and not _a_p_p_e_n_d_-_h_o_o_k (section 4.19.3 , page 69). _a_p_p_e_n_d_- + _h_o_o_k (section 4.19.3 , page 69) is only for appending to existing folders. If the _c_o_m_m_a_n_d is empty, this operation is disabled for this file type. In this case, the folder will be open and closed again (using _o_p_e_n_-_h_o_o_k (section - 4.19.1 , page 64) and _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 65)respectively) each + 4.19.1 , page 68) and _c_l_o_s_e_-_h_o_o_k (section 4.19.2 , page 69)respectively) each time you will add to it. _4_._1_9_._4 _E_n_c_r_y_p_t_e_d _f_o_l_d_e_r_s @@ -3386,15 +3561,14 @@ 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. + The Mutt Next Generation E-Mail Client 71 + _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-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-ng recognizes a - - The Mutt Next Generation E-Mail Client 68 - variety of PGP MIME types, including PGP/MIME and application/pgp. Mutt-ng will denote attachments with a couple lines describing them. These @@ -3442,13 +3616,12 @@ - 1 [text/plain, 7bit, 1K] /tmp/mutt-euler-8082-0 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz + The Mutt Next Generation E-Mail Client 72 + 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 - - The Mutt Next Generation E-Mail Client 69 - attachment, which allows a binary message to be encoded for transmission on 7bit links. It can be changed with the edit-encoding command (default: ^E). The next field is the size of the attachment, rounded to kilobytes or @@ -3494,13 +3667,13 @@ 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, + + The Mutt Next Generation E-Mail Client 73 + XMosaic, lynx and metamail. 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 - - The Mutt Next Generation E-Mail Client 70 - handler. The default search string for these files is a colon delimited list set to @@ -3549,12 +3722,12 @@ text/plain; more %s + The Mutt Next Generation E-Mail Client 74 + Perhaps you would like to use lynx to interactively view a text/html message: text/html; lynx %s - The Mutt Next Generation E-Mail Client 71 - In this case, lynx does not support viewing a file from stdin, so you must use the %s syntax. NNoottee:: _S_o_m_e _o_l_d_e_r _v_e_r_s_i_o_n_s _o_f _l_y_n_x _c_o_n_t_a_i_n _a _b_u_g _w_h_e_r_e _t_h_e_y _w_i_l_l _c_h_e_c_k _t_h_e _m_a_i_l_c_a_p _f_i_l_e _f_o_r _a _v_i_e_w_e_r _f_o_r _t_e_x_t_/_h_t_m_l_. _T_h_e_y _w_i_l_l _f_i_n_d _t_h_e _l_i_n_e @@ -3579,7 +3752,7 @@ The interpretation of shell meta-characters embedded in MIME parameters can 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.4.117 , page 110) variable. + them, see the _m_a_i_l_c_a_p___s_a_n_i_t_i_z_e (section 7.4.123 , page 119) 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. @@ -3601,12 +3774,12 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ && test "`echo $charset | tr '[A-Z]' '[a-z]'`" != iso-8859-1 + The Mutt Next Generation E-Mail Client 75 + _5_._3_._3 _A_d_v_a_n_c_e_d _m_a_i_l_c_a_p _U_s_a_g_e _5_._3_._3_._1 _O_p_t_i_o_n_a_l _F_i_e_l_d_s - The Mutt Next Generation E-Mail Client 72 - 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-ng recog- nizes the following optional fields: @@ -3627,11 +3800,11 @@ needsterminal Mutt-ng uses this flag when viewing attachments with _a_u_t_o_v_i_e_w (sec- - tion 5.4 , page 74), in order to decide whether it should honor - the setting of the _$_w_a_i_t___k_e_y (section 6.4.335 , page 162) variable + tion 5.4 , page 78), in order to decide whether it should honor + the setting of the _$_w_a_i_t___k_e_y (section 7.4.347 , page 173) 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.4.335 , page 162) and the exit + ng will use _$_w_a_i_t___k_e_y (section 7.4.347 , page 173) 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. @@ -3656,11 +3829,12 @@ edit= This flag specifies the command to use to edit a specific MIME type. Mutt-ng supports this from the compose menu, and also uses + + The Mutt Next Generation E-Mail Client 76 + it to compose new attachments. Mutt-ng will default to the defined editor for text attachments. - The Mutt Next Generation E-Mail Client 73 - nametemplate=