From 3ef6910fc7a0dc52132598e46dac9475bb28f5eb Mon Sep 17 00:00:00 2001 From: Rocco Rutte Date: Thu, 28 May 2009 15:19:14 +0200 Subject: [PATCH] Manual: Wrap muttrc commands in --- ChangeLog | 12 ++ doc/manual.xml.head | 310 ++++++++++++++++++++++---------------------- doc/mutt.css | 1 + 3 files changed, 168 insertions(+), 155 deletions(-) diff --git a/ChangeLog b/ChangeLog index 86331669d..102759d07 100644 --- a/ChangeLog +++ b/ChangeLog @@ -1,3 +1,15 @@ +2009-05-27 23:14 -0700 Brendan Cully (5502fb790bab) + + * mutt_ssl_gnutls.c: gnutls: do not ignore certificate problems. + Specifically, do not allow revoked certificates or those signed by + non-CAs unless they have been explicitly stored in the trusted + certificate file. Thanks to Miroslav Lichvar. + +2009-05-27 22:55 -0700 Miroslav Lichvar (85f41efec6bf) + + * ChangeLog, mutt_ssl_gnutls.c: Don't prompt to save certificates that + are already saved but invalid. + 2009-05-27 22:52 -0700 Brendan Cully (90ef283c103e) * mutt_ssl_gnutls.c: Don't leak gnutls certs on preauth validation diff --git a/doc/manual.xml.head b/doc/manual.xml.head index c207498f3..7284975d3 100644 --- a/doc/manual.xml.head +++ b/doc/manual.xml.head @@ -556,7 +556,7 @@ short descriptions. You can remap the editor functions using the -bind command. For example, to make +bind command. For example, to make the <Delete> key delete the character in front of the cursor rather than under, you could use: @@ -776,7 +776,7 @@ backspace (ˆH), the letter again for bold or the letter, bac _ for denoting underline. Mutt will attempt to display these in bold and underline respectively if your terminal supports them. If not, you can use the bold and underline color -objects to specify a color or mono attribute for them. +objects to specify a color or mono attribute for them. @@ -939,7 +939,7 @@ menus have these interesting functions: Creates a new alias based upon the current message (or prompts for a -new one). Once editing is complete, an alias +new one). Once editing is complete, an alias command is added to the file specified by the $alias_file variable for future use @@ -948,7 +948,7 @@ for future use Mutt does not read the $alias_file -upon startup so you must explicitly source the file. +upon startup so you must explicitly source the file. @@ -1056,7 +1056,7 @@ you misspelled the passphrase. Reply to the current or tagged message(s) by extracting any addresses which -match the regular expressions given by the lists or subscribe +match the regular expressions given by the lists or subscribe commands, but also honor any Mail-Followup-To header(s) if the $honor_followup_to configuration variable is set. Using this when replying to messages posted @@ -1221,7 +1221,7 @@ Reply to the author directly. Reply to the author as well to all recipients except you; this consults -alternates. +alternates. @@ -1888,9 +1888,9 @@ question marks into regular expressions). -group is used to directly add either addresses or +group is used to directly add either addresses or regular expressions to the specified group or groups. The different -categories of arguments to the group command can be +categories of arguments to the group command can be in any order. The flags -rx and -addr specify what the following strings (that cannot begin with a hyphen) should be interpreted as: either a regular @@ -1899,9 +1899,9 @@ expression or an email address, respectively. These address groups can also be created implicitly by the -alias, lists, +alias, lists, subscribe and -alternates commands by specifying the +alternates commands by specifying the optional -group option. @@ -1912,9 +1912,9 @@ display to messages matching a group. -ungroup is used to remove addresses or regular +ungroup is used to remove addresses or regular expressions from the specified group or groups. The syntax is similar to -the group command, however the special character +the group command, however the special character * can be used to empty a group of all of its contents. @@ -1972,7 +1972,7 @@ one address, you must separate the addresses with a comma ( The optional -group argument to -alias causes the aliased address(es) to be added to +alias causes the aliased address(es) to be added to the named group. @@ -1987,8 +1987,8 @@ alias theguys manny, moe, jack Unlike other mailers, Mutt doesn't require aliases to be defined -in a special file. The alias command can appear anywhere in -a configuration file, as long as this file is sourced. Consequently, you can have multiple alias files, or +in a special file. The alias command can appear anywhere in +a configuration file, as long as this file is sourced. Consequently, you can have multiple alias files, or you can have all aliases defined in your .muttrc. @@ -1997,7 +1997,7 @@ On the other hand, the <create-alias> function can use only one file, the one pointed to by the $alias_file variable (which is ˜/.muttrc by default). This file is not special either, in the sense that Mutt will happily append aliases to any file, but in -order for the new aliases to take effect you need to explicitly source this file too. +order for the new aliases to take effect you need to explicitly source this file too. @@ -2073,7 +2073,7 @@ This is not a real menu, but is used as a fallback for all of the other menus except for the pager and editor modes. If a key is not defined in another menu, Mutt will look for a binding to use in this menu. This allows you to bind a key to a certain function in multiple menus instead of having -multiple bind statements to accomplish the same task. +multiple bind statements to accomplish the same task. @@ -2267,13 +2267,13 @@ sequence. -The charset-hook command defines an alias for a character set. +The charset-hook command defines an alias for a character set. This is useful to properly display messages which are tagged with a character set name not known to Mutt. -The iconv-hook command defines a system-specific name for a +The iconv-hook command defines a system-specific name for a character set. This is helpful when your systems character conversion library insists on using strange, system-specific names for character sets. @@ -2298,10 +2298,10 @@ for character sets. It is often desirable to change settings based on which mailbox you are -reading. The folder-hook command provides a method by which you can execute +reading. The folder-hook command provides a method by which you can execute any configuration command. regexp is a regular expression specifying in which mailboxes to execute command before loading. If a mailbox -matches multiple folder-hook's, they are executed in the order given in the +matches multiple folder-hooks, they are executed in the order given in the .muttrc. @@ -2324,8 +2324,8 @@ folder-hook mutt "set sort=threads" However, the sorting method is not restored to its previous value when reading a different mailbox. To specify a default command, use the -pattern . before other folder-hooks adjusting a value on a per-folder basis -because folder-hooks are evaluated in the order given in the +pattern . before other folder-hooks adjusting a value on a per-folder basis +because folder-hooks are evaluated in the order given in the configuration file. @@ -2569,9 +2569,9 @@ setting this variable. -The uncolor command can be applied to the index, header and body objects only. It +The uncolor command can be applied to the index, header and body objects only. It removes entries from the list. You must specify the same pattern -specified in the color command for it to be removed. The pattern * is +specified in the color command for it to be removed. The pattern * is a special token which means to clear the color list of all entries. @@ -2649,7 +2649,7 @@ attributes through the use of the mono command. Usage: -For object, see the color command. attribute +For object, see the color command. attribute can be one of the following: @@ -2752,12 +2752,12 @@ unignore posted-to: -With the hdr_order command you can specify an order in +With the hdr_order command you can specify an order in which Mutt will attempt to present these headers to you when viewing messages. -unhdr_order * will clear all previous headers from the order list, +unhdr_order * will clear all previous headers from the order list, thus removing the header order effects set by the system-wide startup file. @@ -2817,7 +2817,7 @@ yourself won't make much sense in many cases. (See &do 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 addresses you receive mail under. That's the -purpose of the alternates command: It takes a list of regular +purpose of the alternates command: It takes a list of regular expressions, each of which can identify an address under which you receive e-mail. @@ -2848,20 +2848,20 @@ to be added to the named group. -The unalternates command can be used to write exceptions to -alternates patterns. If an address matches something in an -alternates command, but you nonetheless do not think it is -from you, you can list a more precise pattern under an unalternates +The unalternates command can be used to write exceptions to +alternates patterns. If an address matches something in an +alternates command, but you nonetheless do not think it is +from you, you can list a more precise pattern under an unalternates command. -To remove a regular expression from the alternates list, use the -unalternates command with exactly the same regexp. -Likewise, if the regexp for an alternates command matches -an entry on the unalternates list, that unalternates -entry will be removed. If the regexp for unalternates -is *, all entries on alternates will be removed. +To remove a regular expression from the alternates list, use the +unalternates command with exactly the same regexp. +Likewise, if the regexp for an alternates command matches +an entry on the unalternates list, that unalternates +entry will be removed. If the regexp for unalternates +is *, all entries on alternates will be removed. @@ -2933,7 +2933,7 @@ lists you are subscribed to. Mutt also has limited support for auto-detecting mailing lists: it supports parsing mailto: links in the common List-Post: header which has the same effect as -specifying the list address via the lists command +specifying the list address via the lists command (except the group feature). Once you have done this, the <list-reply> function will work for all known lists. @@ -2957,8 +2957,8 @@ to send Cc upons replies (which is more a group- than a list-reply). More precisely, Mutt maintains lists of patterns for the addresses of known and subscribed mailing lists. Every subscribed mailing -list is known. To mark a mailing list as known, use the lists -command. To mark it as subscribed, use subscribe. +list is known. To mark a mailing list as known, use the list +command. To mark it as subscribed, use subscribe. @@ -2980,11 +2980,11 @@ example, if you've subscribed to the Mutt mailing list, you will receive mail addressed to mutt-users@mutt.org. So, to tell Mutt that this is a mailing list, you could add lists mutt-users@ to your initialization file. To tell Mutt that you are subscribed to it, -add subscribe mutt-users to your initialization file instead. +add subscribe mutt-users to your initialization file instead. If you also happen to get mail from someone whose address is mutt-users@example.com, you could use -lists ^mutt-users@mutt\\.org$ -or subscribe ^mutt-users@mutt\\.org$ to +lists ^mutt-users@mutt\\.org$ +or subscribe ^mutt-users@mutt\\.org$ to match only mail from the actual list. @@ -3001,7 +3001,7 @@ tokens. To remove a mailing list from the list of subscribed mailing lists, -but keep it on the list of known mailing lists, use unsubscribe. +but keep it on the list of known mailing lists, use unsubscribe. @@ -3091,10 +3091,10 @@ tokens. -The folders in the mailboxes command are resolved when +The folders in the mailboxes command are resolved when the command is executed, so if these names contain shortcut characters (such as = and !), any variable definition that affects these characters (like $folder and $spoolfile) -should be set before the mailboxes command. If +should be set before the mailboxes command. If none of these shorcuts are used, a local path should be absolute as otherwise Mutt tries to find it relative to the directory from where Mutt was started which may not always be desired. @@ -3145,7 +3145,7 @@ mail detection instead which won't work for size-neutral changes. -The my_hdr command allows you to create your own header +The my_hdr command allows you to create your own header fields which will be added to every message you send and appear in the editor if $edit_headers is set. @@ -3179,7 +3179,7 @@ that you can edit the header of your message along with the body. -To remove user defined header fields, use the unmy_hdr +To remove user defined header fields, use the unmy_hdr command. You may specify an asterisk (*) to remove all header fields, or the fields to remove. For example, to remove all To and Cc header fields, you could use: @@ -3220,7 +3220,7 @@ expandos of $index_format to -Using %-expandos in <literal>save-hook</literal> +Using %-expandos in <command>save-hook</command> # default: save all to ~/Mail/<author name> save-hook . ~/Mail/%F @@ -3234,7 +3234,7 @@ save-hook aol\\.com$ +spam -Also see the fcc-save-hook command. +Also see the fcc-save-hook command. @@ -3276,7 +3276,7 @@ See for information on the exact format of ...will save a copy of all messages going to the aol.com domain to -the `+spammers' mailbox by default. Also see the fcc-save-hook command. +the `+spammers' mailbox by default. Also see the fcc-save-hook command. @@ -3297,8 +3297,8 @@ the `+spammers' mailbox by default. Also see the -This command is a shortcut, equivalent to doing both a fcc-hook -and a save-hook with its arguments, +This command is a shortcut, equivalent to doing both a fcc-hook +and a save-hook with its arguments, including %-expansion on mailbox according to $index_format. @@ -3347,35 +3347,35 @@ is executed when pattern matches. -reply-hook is matched against the message you are replying to, -instead of the message you are sending. send-hook is +reply-hook is matched against the message you are replying to, +instead of the message you are sending. send-hook is matched against all messages, both new and replies. -reply-hooks are matched before the send-hook, regardless +reply-hooks are matched before the send-hook, regardless of the order specified in the user's configuration file. -send2-hook is matched every time a message is changed, either +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 +or subject. send2-hook is executed after send-hook, and can, e.g., be used to set parameters such as the $sendmail variable depending on the message's sender address. -For each type of send-hook or reply-hook, when multiple matches +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). -Example: send-hook mutt "set mime_forward signature=''" +Example: send-hook mutt "set mime_forward signature=''" @@ -3387,15 +3387,15 @@ signatures based upon the recipients. -send-hook's are only executed once after getting the +send-hook's are only executed once after getting the initial list of recipients. Adding a recipient after replying or -editing the message will not cause any send-hook to be executed, +editing the message will not cause any send-hook to be executed, similarily if $autoedit is set (as then the initial list of recipients is empty). Also note that my_hdr commands which +linkend="my-hdr">my_hdr commands which modify recipient headers, or the message's subject, don't have any effect on the current message when executed from a -send-hook. +send-hook. @@ -3460,7 +3460,7 @@ When encrypting messages with PGP/GnuPG or OpenSSL, you may want to associate a 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 would -normally use. The crypt-hook command provides a +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. @@ -3495,7 +3495,7 @@ shows how to automatically collapse all threads when entering a folder. -Embedding <literal>push</literal> in <literal>folder-hook</literal> +Embedding <command>push</command> in <command>folder-hook</command> folder-hook . 'push <collapse-all>' @@ -3521,7 +3521,7 @@ folder-hook . 'push <collapse-all>' This command can be used to execute any function. Functions are listed in the function reference. -exec function is equivalent to +execfunction is equivalent to push <function>. @@ -3553,19 +3553,19 @@ listed in the function reference. -The score commands adds value to a message's score if pattern +The score commands adds value to a message's score if pattern matches it. pattern is a string in the format described in the patterns section (note: For efficiency reasons, patterns which scan information not available in the index, such as ˜b, ˜B or ˜h, may not be used). value is a positive or negative integer. A message's final score is the sum total of all -matching score entries. However, you may optionally prefix value with +matching score entries. However, you may optionally prefix value with an equal sign (=) to cause evaluation to stop at a particular entry if there is a match. Negative final scores are rounded up to 0. -The unscore command removes score entries from the list. You must -specify the same pattern specified in the score command for it to be +The unscore command removes score entries from the list. You must +specify the same pattern specified in the score command for it to be removed. The pattern * is a special token which means to clear the list of all score entries. @@ -3599,7 +3599,7 @@ of all score entries. Mutt has generalized support for external spam-scoring filters. -By defining your spam patterns with the spam and nospam +By defining your spam patterns with the spam and nospam commands, you can limit, search, and sort your mail based on its spam attributes, as determined by the external filter. You also can display the spam attributes in your index @@ -3609,10 +3609,10 @@ to display spam tags only when they are defined for a given message.) Your first step is to define your external filter's spam patterns using -the spam command. pattern should be a regular expression +the spam command. pattern should be a regular expression that matches a header in a mail message. If any message in the mailbox matches this regular expression, it will receive a spam tag or -spam attribute (unless it also matches a nospam pattern — see +spam attribute (unless it also matches a nospam pattern — see below.) The appearance of this attribute is entirely up to you, and is governed by the format parameter. format can be any static text, but it also can include back-references from the pattern @@ -3631,7 +3631,7 @@ to be adjusted. If you're using multiple spam filters, a message can have more than -one spam-related header. You can define spam patterns for each +one spam-related header. You can define spam patterns for each filter you use. If a message matches two or more of these patterns, and the $spam_separator variable is set to a string, then the message's spam tag will consist of all the format strings joined @@ -3689,7 +3689,7 @@ that is, by ordering strings alphanumerically. However, if a spam tag begins with a number, Mutt will sort numerically first, and lexically only when two numbers are equal in value. (This is like UNIX's sort -n.) A message with no spam attributes at all — that is, one -that didn't match any of your spam patterns — is sorted at +that didn't match any of your spam patterns — is sorted at lowest priority. Numbers are sorted next, beginning with 0 and ranging upward. Finally, non-numeric strings are sorted, with a taking lower priority than z. Clearly, in general, sorting by spam tags is most @@ -3698,28 +3698,28 @@ in case you can't, Mutt can still do something useful. -The nospam command can be used to write exceptions to spam -patterns. If a header pattern matches something in a spam command, +The nospam command can be used to write exceptions to spam +patterns. If a header pattern matches something in a spam command, but you nonetheless do not want it to receive a spam tag, you can list a -more precise pattern under a nospam command. +more precise pattern under a nospam command. -If the pattern given to nospam is exactly the same as the -pattern on an existing spam list entry, the effect will be to +If the pattern given to nospam is exactly the same as the +pattern on an existing spam list entry, the effect will be to remove the entry from the spam list, instead of adding an exception. -Likewise, if the pattern for a spam command matches an entry -on the nospam list, that nospam entry will be removed. If the -pattern for nospam is *, all entries on both lists -will be removed. This might be the default action if you use spam -and nospam in conjunction with a folder-hook. +Likewise, if the pattern for a spam command matches an entry +on the nospam list, that nospam entry will be removed. If the +pattern for nospam is *, all entries on both lists +will be removed. This might be the default action if you use spam +and nospam in conjunction with a folder-hook. -You can have as many spam or nospam commands as you like. -You can even do your own primitive spam detection within Mutt — for +You can have as many spam or nospam commands as you like. +You can even do your own primitive spam detection within Mutt — for example, if you consider all mail from MAILER-DAEMON to be spam, -you can use a spam command like this: +you can use a spam command like this: @@ -3901,22 +3901,22 @@ action to be carried out as if you had answered no. A value of -Prefixing a variable with no will unset it. Example: set noaskbcc. +Prefixing a variable with no will unset it. Example: set noaskbcc. For boolean variables, you may optionally prefix the variable name with inv to toggle the value (on or off). This is useful when writing -macros. Example: set invsmart_wrap. +macros. Example: set invsmart_wrap. -The toggle command automatically prepends the inv prefix to all +The toggle command automatically prepends the inv prefix to all specified variables. -The unset command automatically prepends the no prefix to all +The unset command automatically prepends the no prefix to all specified variables. @@ -3936,14 +3936,14 @@ variables. -The reset command resets all given variables to the compile time +The reset command resets all given variables to the compile time defaults (hopefully mentioned in this manual). If you use the command -set and prefix the variable with & this has the same -behavior as the reset command. +set and prefix the variable with & this has the same +behavior as the reset command. -With the reset command there exists the special variable all, +With the reset command there exists the special variable all, which allows you to reset all variables to their system defaults. @@ -3964,9 +3964,9 @@ example, my_cfgdir. -The set command either creates a +The set command either creates a custom my_ variable or changes its -value if it does exist already. The unset and reset +value if it does exist already. The unset and reset commands remove the variable entirely. @@ -3985,7 +3985,7 @@ files more readable. The following example defines and uses the variable my_cfgdir -to abbreviate the calls of the source command: +to abbreviate the calls of the source command: @@ -4045,8 +4045,8 @@ macro pager <PageDown> "\ Note that there is a space between <enter-command> and -the set configuration command, preventing Mutt from -recording the macro's commands into its history. +the set configuration command, preventing Mutt from +recording the macro's commands into its history. @@ -4082,7 +4082,7 @@ path of your home directory. If the filename ends with a vertical bar (|), then filename is considered to be an executable program from which to read input (eg. -source ˜/bin/myscript|). +source ˜/bin/myscript|). @@ -4108,7 +4108,7 @@ considered to be an executable program from which to read input (eg. This command permits you to flush hooks you have previously defined. You can either remove all hooks by giving the * character as an argument, or you can remove all hooks of a specific type by saying -something like unhook send-hook. +something like unhook send-hook. @@ -4611,8 +4611,8 @@ shows several ways to select messages. ~n [MIN]-[MAX]messages with a score in the range MIN to MAX *) ~Nnew messages ~Oold messages -~pmessages addressed to you (consults alternates) -~Pmessages from you (consults alternates) +~pmessages addressed to you (consults alternates) +~Pmessages from you (consults alternates) ~Qmessages which have been replied to ~r [MIN]-[MAX]messages with date-received in a Date range ~Rread messages @@ -4970,7 +4970,7 @@ automatically, without requiring the tag-prefix. -In macros or push commands, +In macros or push commands, you can use the <tag-prefix-cond> operator. If there are no tagged messages, Mutt will eat the rest of the macro to abort it's execution. Mutt will stop eating the macro when it encounters the <end-cond> @@ -4996,79 +4996,79 @@ configuration option/command. See: -account-hook +account-hook -charset-hook +charset-hook -crypt-hook +crypt-hook -fcc-hook +fcc-hook -fcc-save-hook +fcc-save-hook -folder-hook +folder-hook -iconv-hook +iconv-hook -mbox-hook +mbox-hook -message-hook +message-hook -reply-hook +reply-hook -save-hook +save-hook -send-hook +send-hook -send2-hook +send2-hook @@ -5107,8 +5107,8 @@ to <b@b.b>, the From: header is changed to Message Matching in Hooks -Hooks that act upon messages (message-hook, reply-hook, -send-hook, send2-hook, save-hook, fcc-hook) are evaluated in a +Hooks that act upon messages (message-hook, reply-hook, +send-hook, send2-hook, save-hook, fcc-hook) are evaluated in a slightly different manner. For the other types of hooks, a regular expression is sufficient. But in dealing with messages a finer grain of control is @@ -5347,7 +5347,7 @@ work at the beginning of a string. For example, to store a copy of outgoing messages in the folder they were composed in, -a folder-hook can +a folder-hook can be used to set $record: @@ -5365,7 +5365,7 @@ amounts of mail easier. The first thing you must do is to let Mutt know what addresses you consider to be mailing lists (technically this does not have to be a mailing 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 lists and subscribe commands in your .muttrc. +accomplished through the use of the lists and subscribe commands in your .muttrc. @@ -5469,7 +5469,7 @@ be monitored for new mail (see for details). When in the index menu and being idle (also see $timeout), Mutt periodically checks for new mail in all folders which have been configured via the -mailboxes command. The interval depends on the folder +mailboxes command. The interval depends on the folder type: for local/IMAP folders it consults $mail_check and $pop_checkinterval @@ -5480,7 +5480,7 @@ for POP folders. Outside the index menu the directory browser supports checking for new mail using the <check-new> function which is unbound by default. Pressing TAB will bring up a -menu showing the files specified by the mailboxes command, +menu showing the files specified by the mailboxes command, and indicate which contain new messages. Mutt will automatically enter this mode when invoked from the command line with the -y option. @@ -6075,7 +6075,7 @@ and Mutt will use your standard pager to display the results. needsterminal -Mutt uses this flag when viewing attachments with auto_view, in order to decide whether it should honor the setting +Mutt uses this flag when viewing attachments with auto_view, in order to decide whether it should honor the setting of the $wait_key variable or not. When an attachment is viewed using an interactive program, and the corresponding mailcap entry has a needsterminal flag, Mutt will use @@ -6199,7 +6199,7 @@ entry with the print command. -In addition, you can use this with auto_view +In addition, you can use this with auto_view to denote two commands for viewing an attachment, one to be viewed automatically, the other to be viewed interactively from the attachment menu. In addition, you can then use the test feature to determine which @@ -6213,7 +6213,7 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput -For auto_view, Mutt will choose the third +For auto_view, Mutt will choose the third entry because of the copiousoutput tag. For interactive viewing, Mutt will run the program RunningX to determine if it should use the first entry. If the program returns non-zero, Mutt will use the second entry @@ -6402,7 +6402,7 @@ representation which you can view in the pager. -You then use the auto_view .muttrc command to list the +You then use the auto_view .muttrc command to list the content-types that you wish to view automatically. For instance, if you set it to: @@ -6427,9 +6427,9 @@ application/postscript; ps2ascii %s; copiousoutput -unauto_view can be used to remove previous entries from the autoview list. -This can be used with message-hook to autoview messages based on size, etc. -unauto_view * will remove all previous entries. +unauto_view can be used to remove previous entries from the autoview list. +This can be used with message-hook to autoview messages based on size, etc. +unauto_view * will remove all previous entries. @@ -6440,7 +6440,7 @@ This can be used with message-hook to autovi Mutt has some heuristics for determining which attachment of a multipart/alternative type to display. First, Mutt will check the -alternative_order list +alternative_order list to determine if one of the available types is preferred. It consists of a number of mimetypes in order, including support for implicit and explicit wildcards, for example: @@ -6452,14 +6452,14 @@ alternative_order text/enriched text/plain text application/postscript image/* Next, Mutt will check if any of the types have a defined -auto_view, and use that. Failing +auto_view, and use that. Failing that, Mutt will look for any text type. As a last attempt, Mutt will look for any type it knows how to handle. -To remove a MIME type from the alternative_order list, use the -unalternative_order command. +To remove a MIME type from the alternative_order list, use the +unalternative_order command. @@ -6473,7 +6473,7 @@ attachment-counting and -searching support might be for you. You can make your message index display the number of qualifying attachments in each message, or search for messages by attachment count. You also can configure what kinds of attachments qualify for this feature with the -attachments and unattachments commands. +attachments and unattachments commands. @@ -6536,9 +6536,9 @@ any MIME type.) -The MIME types you give to the attachments directive are a kind of -pattern. When you use the attachments directive, the patterns you -specify are added to a list. When you use unattachments, the pattern +The MIME types you give to the attachments directive are a kind of +pattern. When you use the attachments directive, the patterns you +specify are added to a list. When you use unattachments, the pattern is removed from the list. The patterns are not expanded and matched to specific MIME types at this time — they're just text in a list. They're only matched when actually evaluating a message. @@ -6602,7 +6602,7 @@ attachments -I message/external-body -Entering the command attachments ? +Entering the command attachments ? as a command will list your current settings in Muttrc format, so that it can be pasted elsewhere. @@ -6644,7 +6644,7 @@ mime-type is listed in mime_lookup, then the extension of the filename wi be compared to the list of extensions in the mime.types file. The mime-type associated with this extension will then be used to process the attachment according to the rules in the mailcap file and according to any other configuration -options (such as auto_view) specified. Common usage would be: +options (such as auto_view) specified. Common usage would be: @@ -7032,15 +7032,15 @@ Usage: If you happen to have accounts on multiple IMAP, POP and/or SMTP servers, you may find managing all the authentication settings inconvenient and -error-prone. The account-hook command may help. This hook works like -folder-hook but is invoked whenever Mutt needs to access a remote mailbox +error-prone. The account-hook command may help. This hook works like +folder-hook but is invoked whenever Mutt needs to access a remote mailbox (including inside the folder browser), not just when you open the mailbox. This includes (for example) polling for new mail, storing Fcc messages and saving messages to a folder. As a consequence, -account-hook should only be used to set connection-related settings such +account-hook should only be used to set connection-related settings such as passwords or tunnel commands but not settings such as sender address or name (because in general it should be considered unpredictable -which account-hook was last used). +which account-hook was last used). @@ -7057,9 +7057,9 @@ account-hook smtp://user@host3/ 'set tunnel="ssh host3 /usr/libexec/smtpd"' To manage multiple accounts with, for example, different values of $record or sender addresses, -folder-hook +folder-hook has to be be used together with -the mailboxes command. +the mailboxes command. @@ -7076,8 +7076,8 @@ folder-hook imap://user@host2/ 'set folder=imap://host2/ ; set record=+INBOX/Sen In example the folders are defined using -mailboxes so Mutt polls them for new -mail. Each folder-hook triggers when +mailboxes so Mutt polls them for new +mail. Each folder-hook triggers when one mailbox below each IMAP account is opened and sets $folder to the account's root folder. Next, it sets $record to @@ -7422,7 +7422,7 @@ For example, when opening a maildir folder with a few thousand messages, the default value for $read_inc may be too low. It can be tuned on on a folder-basis using -folder-hooks: +folder-hooks: @@ -7538,7 +7538,7 @@ to send messages from the command line as well. -sspecify a subject (enclose in quotes if it contains spaces) -vshow version number and compile-time definitions -xsimulate the mailx(1) compose mode --yshow a menu containing the files specified by the mailboxes command +-yshow a menu containing the files specified by the mailboxes command -zexit immediately if there are no messages in the mailbox -Zopen the first folder with new message, exit immediately if none diff --git a/doc/mutt.css b/doc/mutt.css index 6483de296..8aeb4bfb2 100644 --- a/doc/mutt.css +++ b/doc/mutt.css @@ -19,3 +19,4 @@ div.example p.title { margin-left:2%; } div.note h3 { font-size:small; font-style:italic; font-variant: small-caps; } div.note h3:after { content: ":" } div.note { margin-bottom: 5px; } +strong.command { font-family: monospace; font-weight: normal; } -- 2.40.0