X-Git-Url: http://git.madism.org/?a=blobdiff_plain;f=doc%2Fmanual.sgml.head;h=0f3dd6bf44872e8da41f9d94bee22574b09b53d7;hb=2c522cac0278dd774896f25048da2c5cc1d9cf99;hp=085c5c9b62cca55ee4b177351fb4bf7c287954ed;hpb=84641f7b7a15e9e7eeb4be30c5fac8ffd1253f99;p=apps%2Fmadmutt.git diff --git a/doc/manual.sgml.head b/doc/manual.sgml.head index 085c5c9..0f3dd6b 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.
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.
-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
-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.
-
-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.
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:
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:
-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:
@@ -3326,8 +3341,8 @@ application/ms-excel; open.pl %s
-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.
-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.
-Running mutt -s &dquot;data set for run #2&dquot; professor@bigschool.edu