X-Git-Url: http://git.madism.org/?a=blobdiff_plain;f=doc%2Fmanual.sgml.head;h=f11b7119696df846a4b713b1e9e0078fb5473cc2;hb=1b29c92e5a96be51f4a16728a73485eb4daf6563;hp=085c5c9b62cca55ee4b177351fb4bf7c287954ed;hpb=84641f7b7a15e9e7eeb4be30c5fac8ffd1253f99;p=apps%2Fmadmutt.git diff --git a/doc/manual.sgml.head b/doc/manual.sgml.head index 085c5c9..f11b711 100644 --- a/doc/manual.sgml.head +++ b/doc/manual.sgml.head @@ -117,7 +117,7 @@ configuration file is to source ~/.muttrc in ~/.muttngrc.

Information is presented in menus, very similar to ELM. Here is a table -showing the common keys used to navigate menus in Mutt. +showing the common keys used to navigate menus in Mutt-ng. j or Down next-entry move to the next entry @@ -172,7 +172,7 @@ front of the cursor rather than under, you could use Similar to many other mail clients, there are two modes in which mail is read in Mutt-ng. The first is the index of messages in the mailbox, which is -called the ``index'' in Mutt. The second mode is the display of the +called the ``index'' in Mutt-ng. The second mode is the display of the message contents. This is called the ``pager.'' The next few sections describe the functions provided in each of these @@ -506,10 +506,10 @@ you are replying to or forwarding a message. See also , , , , and for changing how Mutt asks these +name="$fast_reply"> for changing how Mutt-ng asks these questions. -Mutt will then automatically start your on the message body. If the variable is set, the headers will be at the top of the message in your editor. Any messages you are replying @@ -563,7 +563,7 @@ special features available. If you specify -Mutt will pick up @@ -572,12 +572,12 @@ where . -Using Mutt with PGP +Using Mutt-ng with PGP

If you want to use PGP, you can specify @@ -590,7 +590,7 @@ id="pgp_sign_as" name="$pgp_sign_as"> permanently. If you have told mutt to PGP encrypt a message, it will guide you through a key selection process when you try to send the message. -Mutt will not ask you any questions about keys which have a +Mutt-ng will not ask you any questions about keys which have a certified user ID matching one of the message recipients' mail addresses. However, there may be situations in which there are several keys, weakly certified user ID fields, or where no matching @@ -650,7 +650,7 @@ of which the latest appears to be called 2.9b23. To use it, you'll have to obey certain restrictions. Most important, you cannot use the variable. This means that you can recall the -message even if you exit Mutt and then restart it at a later time. +message even if you exit Mutt-ng and then restart it at a later time. Once a message is postponed, there are several ways to resume it. From the command line you can use the ``-p'' option, or if you quad-option. Reading news via NNTP

-If compiled with ``--enable-nntp'' option, Mutt can read news from newsserver -via NNTP. You can open a newsgroup with function ``change-newsgroup'' -(default: i). Default newsserver can be obtained from -variable. Article headers are cached and can be loaded from file when +If compiled with ``--enable-nntp'' option, Mutt-ng can read news from +newsserver via NNTP. You can open a newsgroup with function +``change-newsgroup'' (default: i). Default newsserver can be obtained +from variable. Article +headers are cached and can be loaded from file when newsgroup entered instead loading from newsserver. Configuration

While the default configuration (or ``preferences'') make Mutt-ng usable right out -of the box, it is often desirable to tailor Mutt to suit your own tastes. When +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'' option is specified. This file is @@ -763,13 +764,13 @@ does not exist and your home directory has a subdirectory named .muttng/muttngrc. .muttrc (or .muttngrc for Mutt-ng) is the file where you will -usually place your to configure Mutt. +usually place your to configure Mutt-ng. In addition, mutt supports version specific configuration files that are parsed instead of the default files as explained above. For instance, if your system has a . Each line of the file may contain one or more commands. When multiple commands are used, they must be separated by a semicolon (;). -set realname='Mutt user' ; ignore x- +set realname='Mutt-ng user' ; ignore x- The hash mark, or pound sign (``#''), is used as a ``comment'' character. You can use it to @@ -876,7 +877,7 @@ For a complete list, see the . Usage: -Unlike other mailers, Mutt doesn't require aliases to be defined +Unlike other mailers, Mutt-ng doesn't require aliases to be defined in a special file. The . Consequently, you can have multiple alias files, or @@ -901,14 +902,14 @@ On the other hand, the function can use only one file, the one pointed to by the 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 +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 this file too. For example: -source /usr/local/share/Mutt.aliases +source /usr/local/share/Mutt-ng.aliases source ~/.mail_aliases set alias_file=~/.mail_aliases @@ -945,7 +946,7 @@ allowed). The currently defined maps are: Usage: -If your terminal supports color, you can spice up Mutt by creating your own +If your terminal supports color, you can spice up Mutt-ng by creating your own color scheme. To define the color of an object (type of information), you must specify both a foreground color attachment body (match bold (highlighting bold patterns in the body of messages) -error (error messages printed by Mutt) +error (error messages printed by Mutt-ng) header (match hdrdefault (default color of the message header in the pager) index (match Usage: . 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 configuration variable. -More precisely, Mutt maintains lists of patterns for the addresses +More precisely, Mutt-ng maintains lists of patterns for the addresses of known and subscribed mailing lists. Every subscribed mailing list is known. To mark a mailing list as known, use the ``lists'' command. To mark it as subscribed, use ``subscribe''. @@ -1290,8 +1291,8 @@ tracking system as list mail, for instance, you could say give a portion of the list's e-mail address. Specify as much of the address as you need to to remove ambiguity. For -example, if you've subscribed to the Mutt mailing list, you will receive mail -addressed to Pressing TAB in the directory browser will bring up a menu showing the files specified by the @@ -1377,7 +1378,7 @@ in your variable, @@ -1433,7 +1434,7 @@ Also see the command. Usage: . Mutt searches the initial list of +. Mutt-ng searches the initial list of message recipients for the first matching mailbox. @@ -1525,7 +1526,7 @@ Usage: Usage: Configuring features conditionally

-Usage: Usage: +These commands allow testing for a variable, function or certain feature +being available or not respectively, before actually executing the +command given. + +

+ +All names of variables, functions and menus may be tested. Additionally, the +following compile-features may be tested when prefixed with +' Examples follow. -To only source a file with IMAP related settings only if IMAP support is +

+To only source a file with IMAP related settings if IMAP support is compiled in, use: ifdef feature_imap 'source ~/.mutt-ng/imap_setup' @@ -1774,6 +1785,7 @@ ifdef feature_imap 'source ~/.mutt-ng/imap_setup' # ... +

To exit mutt-ng directly if no NNTP support is compiled in: ifndef feature_nntp 'push q' @@ -1783,11 +1795,12 @@ ifndef feature_nntp 'push q' # ... -To only set the when the system's SVN -is recent enough to have it: +

+To only set the variable if +the system's mutt-ng is aware of it, use: -ifdef imap_mail_check 'set imap_mail_check=300' +ifdef imap_mail_check 'set imap_mail_check=500' Removing hooks

-All string patterns in Mutt including those in more complex +All string patterns in Mutt-ng including those in more complex 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 @@ -1939,7 +1952,7 @@ Repetition takes precedence over concatenation, which in turn takes precedence over alternation. A whole subexpression may be enclosed in parentheses to override these precedence rules. - @@ -1966,7 +1979,7 @@ they may or may not be available in stock libraries on various systems. Patterns

-Many of Mutt's commands allow you to specify a pattern to match +Many of Mutt-ng's commands allow you to specify a pattern to match (limit, tag-pattern, delete-pattern, etc.). There are several ways to select messages: @@ -1986,7 +1999,7 @@ messages: ~G cryptographically encrypted messages ~H EXPR messages with a spam attribute matching EXPR ~h EXPR messages which contain EXPR in the message header -~k message contains PGP key material +~k message contains PGP key material ~i ID message which match ID in the ``Message-ID'' field ~L EXPR message is either originated or received by EXPR ~l message is addressed to a known mailing list @@ -2004,22 +2017,24 @@ messages: ~T tagged messages ~t USER messages addressed to USER ~U unread messages -~v message is part of a collapsed thread. -~V cryptographically verified messages +~v message is part of a collapsed thread. +~V cryptographically verified messages +~w EXPR messages which contain EXPR in the `Newsgroups' field + (if compiled with NNTP support) ~x EXPR messages which contain EXPR in the `References' field ~y EXPR messages which contain EXPR in the `X-Label' field ~z [MIN]-[MAX] messages with a size in the range MIN to MAX *) -~= duplicated messages (see $duplicate_threads) -~$ unreferenced messages (requires threaded view) -~* ``From'' contains realname and (syntactically) valid - address (excluded are addresses matching against - alternates or any alias) +~= duplicated messages (see $duplicate_threads) +~$ unreferenced messages (requires threaded view) +~* ``From'' contains realname and (syntactically) valid + address (excluded are addresses matching against + alternates or any alias) Where EXPR, USER, ID, and SUBJECT are . Special attention has to be made when using regular expressions inside of patterns. Specifically, -Mutt's parser for these patterns will strip one level of backslash (\), +Mutt-ng's parser for these patterns will strip one level of backslash (\), which is normally used for quoting. If it is your intention to use a backslash in the regular expression, you will need to use two backslashes instead (\\). @@ -2055,7 +2070,7 @@ would select messages which contain the word ``mutt'' in the list of recipients @@ -2083,7 +2098,7 @@ or ``Ed +SomeoneElse'': Note that if a regular expression contains parenthesis, or a veritical bar ("|"), you @@ -2096,7 +2111,7 @@ and Searching by Date

-Mutt supports two types of dates, for Mutt's pattern +default. See for Mutt-ng's pattern matching syntax. Once you have tagged the desired messages, you can use the @@ -2185,7 +2200,7 @@ automatically, without requiring the ``tag-prefix''. In or 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'' +Mutt-ng will stop "eating" the macro when it encounters the ``end-cond'' operator; after this operator the rest of the macro will be executed as normal. @@ -2194,7 +2209,7 @@ normal. A or along with a configuration option/command. See @@ -2229,7 +2244,7 @@ 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 allows the use of the +Mutt-ng allows the use of the language for matching messages in hook commands. This works in exactly the same way as it would when -send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt User ' +send-hook '~t ^me@cs\.hmc\.edu$' 'my_hdr From: Mutt-ng User ' which would execute the given command when sending mail to variable. The pattern is translated at the time the hook is declared, so the value of @@ -2308,7 +2323,7 @@ switch on and off the sidebar simply by pressing 'B'. External Address Queries

-Mutt supports connecting to external directory databases such as LDAP, +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 variable, you specify the wrapper @@ -2352,10 +2367,10 @@ added to the prompt. Mailbox Formats

-Mutt supports reading and writing of four different mailbox formats: +Mutt-ng supports reading and writing of four different mailbox formats: mbox, MMDF, MH and Maildir. The mailbox type is autodetected, so there is no need to use a flag for different mailbox types. When creating new -mailboxes, Mutt uses the default specified with the variable. as determined by the address of the alias Handling Mailing Lists

-Mutt has a few configuration options that make dealing with large +Mutt-ng has a few configuration options that make dealing with large amounts of mail easier. The first thing you must do is to let Mutt know what addresses you consider to be mailing lists (technically this does not have to be a mailing list, but that is what it is most @@ -2416,7 +2431,7 @@ often used for), and what lists you are subscribed to. This is accomplished through the use of the commands in your muttrc. -Now that Mutt knows what your mailing lists are, it can do several +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 option is set, mutt will generate @@ -2455,7 +2470,7 @@ that the reply goes to the mailing list, even if it's not specified in the list of recipients in the +field. Mutt-ng uses the variable to help decide which address to use. If set to variable's ``%y'' and ``%Y'' escapes can be used to expand ``X-Label:'' fields in the -index, and Mutt's pattern-matcher can match regular expressions to +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 has the ability to the mailbox into +Lastly, Mutt-ng has the ability to the mailbox into . A thread is a group of messages which all relate to the same subject. This is usually organized into a tree-like structure where a message and all of its replies are represented graphically. If you've ever @@ -2492,7 +2507,7 @@ uninteresting threads and quickly find topics of value. Editing threads

-Mutt has the ability to dynamically restructure threads that are broken +Mutt-ng has the ability to dynamically restructure threads that are broken either by misconfigured software or bad behavior from some correspondents. This allows to clean your mailboxes formats) from these annoyances which make it hard to follow a discussion. @@ -2502,7 +2517,7 @@ annoyances which make it hard to follow a discussion. Some mailers tend to "forget" to correctly set the "In-Reply-To:" and "References:" headers when replying to a message. This results in broken -discussions because Mutt has not enough information to guess the correct +discussions because Mutt-ng has not enough information to guess the correct threading. You can fix this by tagging the reply, then moving to the parent message and using the ``link-threads'' function (bound to & by default). The @@ -2540,7 +2555,7 @@ message). Refer to the man page on sendmail for more details on DSN. POP3 Support (OPTIONAL)

-If Mutt was compiled with POP3 support (by running the pop://username@popserver[:port]/. Polling for new mail is more expensive over POP3 than locally. For this -reason the frequency at which Mutt will check for mail remotely can be +reason the frequency at which Mutt-ng will check for mail remotely can be controlled by the - + variable, which defaults to every 60 seconds. -If Mutt was compiled with SSL support (by running the , fetch all your new mail and place it in the local . After this -point, Mutt runs exactly as if the mail had always been local. +point, Mutt-ng runs exactly as if the mail had always been local. IMAP Support (OPTIONAL)

-If Mutt was compiled with IMAP support (by running the imap://username@imapserver[:port]/INBOX. -If Mutt was compiled with SSL support (by running the {[username@]imapserver[:port][/ssl]}path/to/folder -Note that not all servers use / as the hierarchy separator. Mutt should +Note that not all servers use / as the hierarchy separator. Mutt-ng should correctly notice which separator is being used by the server and convert paths accordingly. @@ -2656,7 +2671,7 @@ following differences: Authentication

-Mutt supports four authentication methods with IMAP servers: SASL, +Mutt-ng supports four authentication methods with IMAP servers: SASL, GSSAPI, CRAM-MD5, and LOGIN (there is a patch by Grant Edwards to add NTLM authentication for you poor exchange users out there, but it has yet to be integrated into the main tree). There is also support for @@ -2672,7 +2687,7 @@ encrypted and invisible to those teeming network snoops. It is the best option if you have it. To use it, you must have the Cyrus SASL library installed on your system and compile mutt with the -Mutt will try whichever methods are compiled in and available on the server, +Mutt-ng will try whichever methods are compiled in and available on the server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN. There are a few variables which control authentication: @@ -2726,7 +2741,7 @@ macro pager \cb |urlview\n Compressed folders Support (OPTIONAL)

-If Mutt was compiled with compressed folders support (by running the +If Mutt-ng was compiled with compressed folders support (by running the though you'll be able to append to the folder. -Note that Mutt will only try to use hooks if the file is not in one of +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 @@ -2885,33 +2900,33 @@ folder, so there is no append-hook defined. directory, where it can be read by your system administrator. So think about the security aspects of this. -Mutt's MIME Support +Mutt-ng's MIME Support

-Quite a bit of effort has been made to make Mutt the premier text-mode +Quite a bit of effort has been made to make Mutt-ng the premier text-mode MIME MUA. Every effort has been made to provide the functionality that the discerning MIME user requires, and the conformance to the standards -wherever possible. When configuring Mutt for MIME, there are two extra -types of configuration files which Mutt uses. One is the +wherever possible. When configuring Mutt-ng for MIME, there are two extra +types of configuration files which Mutt-ng uses. One is the Using MIME in Mutt

-There are three areas/menus in Mutt which deal with MIME, they are the +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. Viewing MIME messages in the pager

When you select a message from the index and view it in the pager, Mutt -decodes the message to a text representation. Mutt internally supports +decodes the message to a text representation. Mutt-ng internally supports a number of MIME types, including text/plain, text/enriched, message/rfc822, and message/news. In addition, the export -controlled version of Mutt recognizes a variety of PGP MIME types, +controlled version of Mutt-ng recognizes a variety of PGP MIME types, including PGP/MIME and application/pgp. -Mutt will denote attachments with a couple lines describing them. +Mutt-ng will denote attachments with a couple lines describing them. These lines are of the form: [-- Attachment #1: Description --] @@ -2921,7 +2936,7 @@ Where the 7bit/8bit/quoted-printable/base64/binary. -If Mutt cannot deal with a MIME type, it will display a message like: +If Mutt-ng cannot deal with a MIME type, it will display a message like: [-- image/gif is unsupported (use 'v' to view this part) --] @@ -2960,7 +2975,7 @@ Attachments appear as follows: 2 [applica/x-gunzip, base64, 422K] ~/src/mutt-0.85.tar.gz -The '-' denotes that Mutt will delete the file after sending (or +The '-' denotes that Mutt-ng will delete the file after sending (or postponing, or canceling) the message. It can be toggled with the MIME Type configuration with -When you add an attachment to your mail message, Mutt searches your +When you add an attachment to your mail message, Mutt-ng searches your personal mime.types file at ${HOME}/.mime.types, and then the system mime.types file at /usr/local/share/mutt/mime.types or /etc/mime.types @@ -2987,19 +3002,19 @@ application/postscript ps eps application/pgp pgp audio/x-aiff aif aifc aiff -A sample text/plain. If the file contains binary information, then Mutt will +information, Mutt-ng will assume that the file is plain text, and mark it +as text/plain. If the file contains binary information, then Mutt-ng will mark it as application/octet-stream. You can change the MIME -type that Mutt assigns to an attachment by using the MIME Viewer configuration with -Mutt supports RFC 1524 MIME Configuration, in particular the Unix +Mutt-ng supports RFC 1524 MIME Configuration, in particular the Unix specific format specified in Appendix A of RFC 1524. This file format is commonly referred to as the mailcap format. Many MIME compliant programs utilize the mailcap format, allowing you to specify handling for all MIME types in one place for all programs. Programs known to use this format include Netscape, XMosaic, lynx and metamail. -In order to handle various MIME types that Mutt can not handle -internally, Mutt parses a series of external configuration files to +In order to handle various MIME types that Mutt-ng can not handle +internally, Mutt-ng parses a series of external configuration files to find an external handler. The default search string for these files is a colon delimited list set to @@ -3054,9 +3069,9 @@ The view command is a Unix command for viewing the type specified. There are two different types of commands supported. The default is to send the body of the MIME message to the command on stdin. You can change this behavior by using %s as a parameter to your view command. -This will cause Mutt to save the body of the MIME message to a temporary +This will cause Mutt-ng to save the body of the MIME message to a temporary file, and then call the view command with the %s replaced by -the name of the temporary file. In both cases, Mutt will turn over the +the name of the temporary file. In both cases, Mutt-ng will turn over the terminal to the view program until the program quits, at which time Mutt will remove the temporary file if it exists. @@ -3099,7 +3114,7 @@ This is the simplest form of a mailcap file. Secure use of mailcap

The interpretation of shell meta-characters embedded in MIME parameters -can lead to security problems in general. Mutt tries to quote 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 variable. @@ -3109,7 +3124,7 @@ safe, there are other applications parsing mailcap, maybe taking less care of it. Therefore you should pay attention to the following rules: In addition to the required content-type and view command fields, you can add semi-colon ';' separated fields to set flags and other options. -Mutt recognizes the following optional fields: +Mutt-ng recognizes the following optional fields: more in the lynx -dump example in the Basic section: text/html; lynx -dump %s ; copiousoutput This will cause lynx to format the text/html output as text/plain -and Mutt will use your standard pager to display the results. +and Mutt-ng will use your standard pager to display the results. , in order to decide whether it should honor the setting of the variable or not. When an attachment is viewed using an interactive program, and the -corresponding mailcap entry has a and the exit status of the program to decide if it will ask you to press a key after the external program has exited. In all other situations it will not prompt you for a key. compose=<command> This flag specifies the command to use to create a new attachment of a -specific MIME type. Mutt supports this from the compose menu. +specific MIME type. Mutt-ng supports this from the compose menu. composetyped=<command> This flag specifies the command to use to create a new attachment of a specific MIME type. This command differs from the compose command in that mutt will expect standard MIME headers on the data. This can be used to specify parameters, filename, description, etc. for a new -attachment. Mutt supports this from the compose menu. +attachment. Mutt-ng supports this from the compose menu. print=<command> This flag specifies the command to use to print a specific MIME type. -Mutt supports this from the attachment and compose menus. +Mutt-ng supports this from the attachment and compose menus. edit=<command> This flag specifies the command to use to edit a specific MIME type. -Mutt supports this from the compose menu, and also uses it to compose -new attachments. Mutt will default to the defined editor for text +Mutt-ng supports this from the compose menu, and also uses it to compose +new attachments. Mutt-ng will default to the defined editor for text attachments. nametemplate=<template> This field specifies the format for the file denoted by %s in the @@ -3189,34 +3204,34 @@ text/html; lynx %s; nametemplate=%s.html This field specifies a command to run to test whether this mailcap entry should be used. The command is defined with the command expansion rules defined in the next section. If the command returns 0, then the -test passed, and Mutt uses this entry. If the command returns non-zero, -then the test failed, and Mutt continues searching for the right entry. -the content-type must match before Mutt performs the test. +test passed, and Mutt-ng uses this entry. If the command returns non-zero, +then the test failed, and Mutt-ng continues searching for the right entry. +the content-type must match before Mutt-ng performs the test. For example: text/html; netscape -remote 'openURL(%s)' ; test=RunningX text/html; lynx %s -In this example, Mutt will run the program RunningX which will return 0 +In this example, Mutt-ng will run the program RunningX which will return 0 if the X Window manager is running, and non-zero if it isn't. If -RunningX returns 0, then Mutt will call netscape to display the -text/html object. If RunningX doesn't return 0, then Mutt will go on +RunningX returns 0, then Mutt-ng will call netscape to display the +text/html object. If RunningX doesn't return 0, then Mutt-ng will go on to the next entry and use lynx to display the text/html object. Search Order

-When searching for an entry in the mailcap file, Mutt will search for +When searching for an entry in the mailcap file, Mutt-ng will search for the most useful entry for its purpose. For instance, if you are attempting to print an image/gif, and you have the following -entries in your mailcap file, Mutt will search for an entry with the +entries in your mailcap file, Mutt-ng will search for an entry with the print command: image/*; xv %s image/gif; ; print= anytopnm %s | pnmtops | lpr; \ nametemplate=%s.gif -Mutt will skip the image/* entry and use the image/gif +Mutt-ng will skip the image/* entry and use the image/gif entry with the print command. In addition, you can use this with @@ -3229,10 +3244,10 @@ text/html; netscape -remote 'openURL(%s)' ; test=RunningX text/html; lynx %s; nametemplate=%s.html text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput -For , Mutt will choose the third +For , Mutt-ng 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 +entry. If the program returns non-zero, Mutt-ng will use the second entry for interactive viewing. Command Expansion @@ -3240,37 +3255,37 @@ for interactive viewing. The various commands defined in the mailcap files are passed to the /bin/sh shell using the system() function. Before the command is passed to /bin/sh -c, it is parsed to expand -various special parameters with information from Mutt. The keywords -Mutt expands are: +various special parameters with information from Mutt-ng. The keywords +Mutt-ng expands are: text/html or image/gif. %{<parameter>} -Mutt will expand this to the value of the specified parameter +Mutt-ng will expand this to the value of the specified parameter from the Content-Type: line of the mail message. For instance, if Your mail message contains: Content-Type: text/plain; charset=iso-8859-1 -then Mutt will expand %{charset} to iso-8859-1. The default metamail +then Mutt-ng will expand %{charset} to iso-8859-1. The default metamail mailcap file uses this feature to test the charset to spawn an xterm using the right charset to view the message. \% This will be replaced by a % -Mutt does not currently support the %F and %n keywords +Mutt-ng does not currently support the %F and %n keywords specified in RFC 1524. The main purpose of these parameters is for -multipart messages, which is handled internally by Mutt. +multipart messages, which is handled internally by Mutt-ng. Example mailcap files

@@ -3326,8 +3341,8 @@ application/ms-excel; open.pl %s MIME Autoview

-In addition to explicitly telling Mutt to view an attachment with the -MIME viewer defined in the mailcap file, Mutt has support for +In addition to explicitly telling Mutt-ng to view an attachment with the +MIME viewer defined in the mailcap file, Mutt-ng has support for automatically viewing MIME attachments while in the pager. To work, you must define a viewer in the mailcap file which uses the @@ -3343,7 +3358,7 @@ For instance, if you set auto_view to: auto_view text/html application/x-gunzip application/postscript image/gif application/x-tar-gz -Mutt could use the following mailcap entries to automatically view +Mutt-ng could use the following mailcap entries to automatically view attachments of these types. text/html; lynx -dump %s; copiousoutput; nametemplate=%s.html @@ -3359,7 +3374,7 @@ This can be used with message-hook to autoview messages based on size, etc. MIME Multipart/Alternative

-Mutt has some heuristics for determining which attachment of a +Mutt-ng has some heuristics for determining which attachment of a multipart/alternative type to display. First, mutt will check the alternative_order list to determine if one of the available types is preferred. The alternative_order list consists of a number of @@ -3371,7 +3386,7 @@ alternative_order text/enriched text/plain text application/postscript image/* Next, mutt will check if any of the types have a defined , and use that. Failing -that, Mutt will look for any text type. As a last attempt, mutt will +that, Mutt-ng 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 MIME Lookup

-Mutt's mime_lookup list specifies a list of mime-types that should not +Mutt-ng's mime_lookup list specifies a list of mime-types that should not be treated according to their mailcap entry. This option is designed to deal with binary types such as application/octet-stream. When an attachment's mime-type is listed in mime_lookup, then the extension of the filename will @@ -3398,7 +3413,7 @@ muttrc. Reference Command line options

-Running mutt -s &dquot;data set for run #2&dquot; professor@bigschool.edu