From daf6df95bfcc7efc888b488a825e467268f20d3c Mon Sep 17 00:00:00 2001 From: Pierre Habouzit Date: Tue, 7 Nov 2006 22:35:00 +0100 Subject: [PATCH] more muttng -> madmutt Signed-off-by: Pierre Habouzit --- curs_lib.c | 2 +- curs_main.c | 4 +- doc/PGP-Notes.txt | 16 +- doc/devel-notes.txt | 16 +- doc/dotlock.man | 50 +- doc/madmutt-manual.xsl | 4 +- doc/madmutt-tex.xsl | 6 +- doc/madmutt.sty | 8 +- doc/manual.xml.head | 2168 ++++++++++++++++++++-------------------- doc/manual.xml.tail | 1132 ++++++++++----------- doc/mbox.man | 4 +- doc/mutt.man | 68 +- doc/muttbug.man | 4 +- doc/muttrc.man.head | 54 +- doc/muttrc.man.tail | 8 +- doc/patch-notes.txt | 4 +- dotlock.c | 2 +- init.c | 8 +- init.h | 426 ++++---- lib/debug.c | 2 +- main.c | 12 +- mutt_menu.h | 2 +- muttlib.c | 2 +- status.c | 2 +- 24 files changed, 2002 insertions(+), 2002 deletions(-) diff --git a/curs_lib.c b/curs_lib.c index e938adf..165c4fd 100644 --- a/curs_lib.c +++ b/curs_lib.c @@ -264,7 +264,7 @@ void mutt_query_exit (void) curs_set (1); if (Timeout) timeout (-1); /* restore blocking operation */ - if (mutt_yesorno (_("Exit Mutt-ng?"), M_YES) == M_YES) { + if (mutt_yesorno (_("Exit Madmutt?"), M_YES) == M_YES) { mutt_endwin (NULL); exit (1); } diff --git a/curs_main.c b/curs_main.c index ae62c47..92c6922 100644 --- a/curs_main.c +++ b/curs_main.c @@ -990,7 +990,7 @@ int mutt_index_menu (void) break; } - if (query_quadoption (OPT_QUIT, _("Quit Mutt-ng?")) == M_YES) { + if (query_quadoption (OPT_QUIT, _("Quit Madmutt?")) == M_YES) { int check; oldcount = Context ? Context->msgcount : 0; @@ -1319,7 +1319,7 @@ int mutt_index_menu (void) if ((menu->menu == MENU_MAIN) && (query_quadoption (OPT_QUIT, - _("Exit Mutt-ng without saving?")) == M_YES)) + _("Exit Madmutt without saving?")) == M_YES)) { if (Context) { mx_fastclose_mailbox (Context); diff --git a/doc/PGP-Notes.txt b/doc/PGP-Notes.txt index 6268b35..f9e3b2a 100644 --- a/doc/PGP-Notes.txt +++ b/doc/PGP-Notes.txt @@ -1,4 +1,4 @@ -User's guide - Using PGP/GnuPG with Mutt-ng +User's guide - Using PGP/GnuPG with Madmutt =========================================== How do I use mutt with PGP, PGP5, or GnuPG? @@ -9,7 +9,7 @@ three files there, pgp2.rc, pgp5.rc, and gpg.rc. These files contain ready-to-use configurations for using mutt with pgp2, pgp5, and gpg. -Include one of these files with your Mutt-ng config file (e.g. ~/.muttngrc), +Include one of these files with your Madmutt config file (e.g. ~/.madmuttrc), and things should work out fine. You may wish to verify that all paths and the language parameters @@ -20,7 +20,7 @@ given to the PGP binaries match your needs. Frequently Asked Questions and Tips ----------------------------------- -Q: "People are sending PGP messages which Mutt-ng doesn't +Q: "People are sending PGP messages which Madmutt doesn't recognize. What can I do?" A: The new way is to leave headers alone and use mutt's @@ -88,12 +88,12 @@ if (/^$BPGPS/:b && /^$EPGPS/:b) Q: "I don't like that PGP/MIME stuff, but want to use the old way of PGP-signing my mails. Can't you include - that with Mutt-ng?" + that with Madmutt?" A: No. Application/pgp is not really suited to a world with MIME, non-textual body parts and similar things. Anyway, if you really want to generate these old-style attachments, include the - following macro in your ~/.muttngrc (line breaks for readability, + following macro in your ~/.madmuttrc (line breaks for readability, this is actually one line): macro compose S "Fpgp +verbose=0 -fast @@ -103,7 +103,7 @@ A: No. Application/pgp is not really suited to a world with MIME, There's a new answer, though: Set the pgp_autoinline configuration variable (it's a quad-option) to something different -from "no" (that's the default). Mutt-ng will then try to use +from "no" (that's the default). Madmutt will then try to use application/pgp whereever it makes sense. In particular, it does not make any sense with multiparts, or non-ASCII or non-text bodies. In all other cases, PGP/MIME is used unconditionally. @@ -147,7 +147,7 @@ BACKGROUND Auxiliary Programs ------------------ -Mutt-ng needs two auxiliary programs for its PGP support: pgpewrapng and +Madmutt needs two auxiliary programs for its PGP support: pgpewrapng and pgpringng. @@ -196,7 +196,7 @@ line interfaces can't be properly served by mutt's format mechanism. The Configuration Interface --------------------------- -As usual within Mutt-ng, the configuration interface for the PGP +As usual within Madmutt, the configuration interface for the PGP commands relies on printf-like formats. For all PGP commands, the following %-sequences are defined. diff --git a/doc/devel-notes.txt b/doc/devel-notes.txt index f6455f6..18b0b73 100644 --- a/doc/devel-notes.txt +++ b/doc/devel-notes.txt @@ -1,13 +1,13 @@ Required tools -------------- -If you are planning to hack on Mutt-ng, please subscribe to the -Mutt-ng-devel mailinglist (mutt-ng-deve-l@lists.berlios.de). +If you are planning to hack on Madmutt, please subscribe to the +Madmutt-devel mailinglist (Madmutt-deve-l@lists.berlios.de). Announcements about recent development versions go to that mailing list, as go technical discussions and patches. -You'll need several GNU development utilities for working on mutt-ng: +You'll need several GNU development utilities for working on Madmutt: - automake @@ -56,7 +56,7 @@ Getting started from SVN ------------------------ Once you've checked out a copy of the source from SVN from -svn.berlios.de/svnroot/repos/mutt-ng , you'll need to run the script +svn.berlios.de/svnroot/repos/Madmutt , you'll need to run the script called 'autogen.sh' that is in the root directory. The script does all the automake/autoconf magic that needs to be done with a fresh checkout. If all steps succeed, you'll have a configure script to start off with. @@ -65,13 +65,13 @@ all steps succeed, you'll have a configure script to start off with. A word about warnings --------------------- -Mutt-ng's default build process sets some pretty restrictive compiler +Madmutt's default build process sets some pretty restrictive compiler flags which may lead to lots of warnings. Generally, warnings are something which should be eliminated. Nevertheless, the code in intl/ is said to generate some warnings with the compiler settings we usually rely upon. This code is not -maintained by the Mutt-ng developpers, so please redirect any comments to +maintained by the Madmutt developpers, so please redirect any comments to the GNU gettext library's developpers. @@ -98,7 +98,7 @@ Style Guide - When adding new options, make the old behaviour the default. Also, add them to UPGRADING in the top-level source directory. -- try to keep Mutt-ng as portable as possible. +- try to keep Madmutt as portable as possible. Documentation ------------- @@ -184,7 +184,7 @@ Do _not_ use any other SGML or nroff formatting instructions here! String comparison ----------------- -A word of warning about string comparisons: Since Mutt-ng may run in a +A word of warning about string comparisons: Since Madmutt may run in a huge variety of locales, case-insensitive string comparisons and case conversions may be dangerous. For instance, in iso-8859-9, tolower('I') is DIFFERENT from 'i' - it's indeed the Turkish dotless diff --git a/doc/dotlock.man b/doc/dotlock.man index f86ae0b..73a6a21 100644 --- a/doc/dotlock.man +++ b/doc/dotlock.man @@ -20,14 +20,14 @@ .\" .TH dotlock 1 "AUGUST 1999" Unix "User Manuals" .SH NAME -muttng_dotlock \- Lock mail spool files. +madmutt_dotlock \- Lock mail spool files. .SH SYNOPSIS .PP -.B muttng_dotlock +.B madmutt_dotlock [-t|-f|-u|-d] [-p] [-r \fIretries\fP] \fIfile\fP .SH DESCRIPTION .PP -.B muttng_dotlock +.B madmutt_dotlock implements the traditional mail spool file locking method: To lock \fIfile\fP, a file named \fIfile\fP.lock is created. The program operates with group mail privileges @@ -36,53 +36,53 @@ if necessary. .PP .IP "-t" Just try. -.B muttng_dotlock +.B madmutt_dotlock won't actually lock a file, but inform the invoking process if it's at all possible to lock \fIfile\fP. .IP "-f" Force the lock. If another process holds a lock on \fIfile\fP longer than a certain amount of time, -.B muttng_dotlock +.B madmutt_dotlock will break that lock by removing the lockfile. .IP "-u" Unlock. -.B muttng_dotlock +.B madmutt_dotlock will remove \fIfile\fP.lock. .IP "-d" Delete. -.B muttng_dotlock +.B madmutt_dotlock will lock \fIfile\fP, remove it if it has length 0, and afterwards remove \fIfile\fP.lock. .IP "-p" Use privileges. If given this option, -.B muttng_dotlock +.B madmutt_dotlock will operate with group mail privileges when creating and deleting lock files. .IP "-r \fIretries\fP" This command line option tells -.B muttng_dotlock +.B madmutt_dotlock to try locking \fIretries\fP times before giving up or (if invoked with the .B -f command line option) break a lock. The default value is 5. -.B muttng_dotlock +.B madmutt_dotlock waits one second between successive locking attempts. .SH FILES .PP .IP "\fIfile\fP.lock" The lock file -.B muttng_dotlock +.B madmutt_dotlock generates. .SH SEE ALSO .PP .BR fcntl (2), .BR flock (2), .BR lockfile (1), -.BR muttng (1) +.BR madmutt (1) .SH DIAGNOSTICS .PP -.B muttng_dotlock +.B madmutt_dotlock gives all diagnostics in its return values: .TP .B "0 \- DL_EX_OK" @@ -96,37 +96,37 @@ lack of system memory and the like has occured. The user wants to lock a file which has been locked by another process already. If -.B muttng_dotlock +.B madmutt_dotlock is invoked with the .B -f command line option, -.B muttng_dotlock +.B madmutt_dotlock won't generate this error, but break other processes' locks. .TP .B "4 \- DL_EX_NEED_RPIVS" This return value only occurs if -.B muttng_dotlock +.B madmutt_dotlock has been invoked with the .B -t command line option. It means that -.B muttng_dotlock +.B madmutt_dotlock will have to use its group mail privileges to lock \fIfile\fP. .TP .B "5 \- DL_EX_IMPOSSIBLE" This return value only occurs if -.B muttng_dotlock +.B madmutt_dotlock has been invoked with the .B -t command line option. It means that -.B muttng_dotlock +.B madmutt_dotlock is unable to lock \fIfile\fP even with group mail privileges. .SH NOTES .PP -.B muttng_dotlock +.B madmutt_dotlock tries to implement an NFS-safe dotlocking method which was borrowed from .B lockfile @@ -134,7 +134,7 @@ borrowed from .PP If the user can't open \fIfile\fP for reading with his normal privileges, -.B muttng_dotlock +.B madmutt_dotlock will return the .B DL_EX_ERROR exit value to avoid certain attacks against other users' @@ -143,8 +143,8 @@ when checking permissions; for details of all this see the comments in dotlock.c. .SH HISTORY .PP -.B muttng_dotlock -is part of the Mutt-ng mail user agent package. It has been -created to avoid running Mutt-ng with group mail privileges. +.B madmutt_dotlock +is part of the Madmutt mail user agent package. It has been +created to avoid running Madmutt with group mail privileges. .SH AUTHOR -Thomas Roessler , Nico Golde > +Thomas Roessler , Nico Golde > diff --git a/doc/madmutt-manual.xsl b/doc/madmutt-manual.xsl index 2763a03..94392fa 100644 --- a/doc/madmutt-manual.xsl +++ b/doc/madmutt-manual.xsl @@ -1,6 +1,6 @@ - + @@ -11,7 +11,7 @@ - + @@ -12,13 +12,13 @@ - + + xmlns:madmutt-doc="http://madmutt.berlios.de/doc/#NS"> diff --git a/doc/madmutt.sty b/doc/madmutt.sty index 36f2ab9..fc75e66 100644 --- a/doc/madmutt.sty +++ b/doc/madmutt.sty @@ -1,6 +1,6 @@ % this is pseudo-package with some definitions exluded -% from muttng-tex.xsl to muttng.sty -% written for mutt-ng by: +% from madmutt-tex.xsl to madmutt.sty +% written for madmutt by: % Rocco Rutte % packages @@ -50,9 +50,9 @@ \addtocounter{app}{1} } -% from here on, these implement the muttng-doc namespace, +% from here on, these implement the madmutt-doc namespace, % see Hacking Documentation for details -% muttng-tex.xsl passes most of the content as-is so that +% madmutt-tex.xsl passes most of the content as-is so that % we do it here via LaTeX rather than XSL for good reason... \newcommand{\uglyesc}[1]{\lstinline[basicstyle=\ttfamily]{#1}} diff --git a/doc/manual.xml.head b/doc/manual.xml.head index 5079bf7..07fac53 100644 --- a/doc/manual.xml.head +++ b/doc/manual.xml.head @@ -2,7 +2,7 @@ - + The Mutt Next Generation E-Mail Client @@ -33,8 +33,8 @@ Overview - Mutt-ng is a small but very - powerful text-based MIME mail client. Mutt-ng is highly + Madmutt is a small but very + powerful text-based MIME mail client. Madmutt is highly configurable, and is well suited to the mail power user with advanced features like key bindings, keyboard macros, mail threading, regular expression searches and a powerful pattern @@ -43,13 +43,13 @@ This documentation additionally contains documentation to - Mutt-NG ,a fork from Mutt + Madmutt ,a fork from Mutt with the goal to fix all the little annoyances of Mutt, to integrate all the Mutt patches that are floating around in the - web, and to add other new features. Features specific to Mutt-ng + web, and to add other new features. Features specific to Madmutt will be discussed in an extra section. Don't be confused when - most of the documentation talk about Mutt and not Mutt-ng, - Mutt-ng contains all Mutt features, plus many more. + most of the documentation talk about Mutt and not Madmutt, + Madmutt contains all Mutt features, plus many more. @@ -59,10 +59,10 @@ - Mutt-ng Home Page + Madmutt Home Page - + @@ -80,15 +80,15 @@ - mutt-ng-users@lists.berlios.de: This is - where the mutt-ng user support happens. + Madmutt-users@lists.berlios.de: This is + where the Madmutt user support happens. - mutt-ng-devel@lists.berlios.de: The - development mailing list for mutt-ng + Madmutt-devel@lists.berlios.de: The + development mailing list for Madmutt @@ -106,8 +106,8 @@ Software Distribution Sites - So far, there are no official releases of Mutt-ng, but you can - download daily snapshots from + So far, there are no official releases of Madmutt, but you can + download daily snapshots from @@ -120,10 +120,10 @@ IRC - Visit channel #muttng on #madmutt on irc.freenode.net (www.freenode.net) to chat with other people - interested in Mutt-ng. + interested in Madmutt. @@ -133,10 +133,10 @@ If you want to read fresh news about the latest development in - Mutt-ng, and get informed about stuff like interesting, - Mutt-ng-related articles and packages for your favorite + Madmutt, and get informed about stuff like interesting, + Madmutt-related articles and packages for your favorite distribution, you can read and/or subscribe to our Mutt-ng development + url="http://Madmutt.supersized.org/">Madmutt development weblog. @@ -187,32 +187,32 @@ in a typewriter font and both prefixed with a dollar sign as it's common for UNIX-like environments. Configuration variables are lower-case only while environment variables - are upper-case only. is a configuration variable while - is an environment + is an environment variable. - Muttng-specific functions are enclosed in + madmutt-specific functions are enclosed in <> and printed in a typewriter font, - too, as in . + too, as in . As common for UNIX-like environments, references to manual pages are printed with the section enclosed in - braces, as in or . Execute man [section] + braces, as in or . Execute man [section] [name] to view the manual page. Keys are presented in the following way: ordinary keys are just given as-is, e.g. - q. Control characters are + q. Control characters are prefixed with C- (e.g. the screen can be - redraw by pressing L) and E- for + redraw by pressing L) and E- for Escape, e.g. a folder can be opened read-only with - c. + c. @@ -221,7 +221,7 @@ If, while reading this fine manual, you find any inconsistencies of whatever kind, please contact the developers via - mutt-ng-devel@lists.berlios.de to report it. + Madmutt-devel@lists.berlios.de to report it. @@ -239,7 +239,7 @@ Screens and Menus - mutt-ng offers different screens of which every has its special + Madmutt offers different screens of which every has its special purpose: @@ -269,7 +269,7 @@ The file browser offers operations on and displays - information of all folders mutt-ng should watch for mail. + information of all folders Madmutt should watch for mail. @@ -335,7 +335,7 @@ - When mutt-ng is started without any further options, it'll open + When Madmutt is started without any further options, it'll open the users default mailbox and display the index. @@ -350,7 +350,7 @@ Configuration - Mutt-ng does not feature an internal + Madmutt does not feature an internal configuration interface or menu due to the simple fact that this would be too complex to handle (currently there are several hundred @@ -358,13 +358,13 @@ - Mutt-ng is configured using configuration files which allow + Madmutt is configured using configuration files which allow users to add comments or manage them via version control systems to ease maintenance. - Also, mutt-ng comes with a shell script named grml-muttng + Also, Madmutt comes with a shell script named grml-madmutt kindly contributed by users which really helps and eases the creation of a user's configuration file. When downloading the source code via a snapshot or via subversion, it can be found in @@ -382,8 +382,8 @@ Functions - Mutt-ng offers great flexibility due to the use of functions: - internally, every action a user can make mutt-ng perform is named + Madmutt offers great flexibility due to the use of functions: + internally, every action a user can make Madmutt perform is named ``function.'' Those functions are assigned to keys (or even key sequences) and may be completely adjusted to user's needs. The basic idea is that the impatient users get a very intuitive @@ -402,7 +402,7 @@ Interaction - Mutt-ng has two basic concepts of user interaction: + Madmutt has two basic concepts of user interaction: @@ -448,13 +448,13 @@ Modularization - Although mutt-ng has many functionality built-in, many + Although Madmutt has many functionality built-in, many features can be delegated to external tools to increase flexibility: users can define programs to filter a message through before displaying, users can use any program they want for displaying a message, message types (such as PDF or PostScript) - for which mutt-ng doesn't have a built-in filter can be rendered - by arbitrary tools and so forth. Although mutt-ng has an alias + for which Madmutt doesn't have a built-in filter can be rendered + by arbitrary tools and so forth. Although Madmutt has an alias mechanism built-in, it features using external tools to query for nearly every type of addresses from sources like LDAP, databases or just the list of locally known users. @@ -471,7 +471,7 @@ Patterns - Mutt-ng has a built-in pattern matching ``language'' which is + Madmutt has a built-in pattern matching ``language'' which is as widely used as possible to present a consistent interface to users. The same ``pattern terms'' can be used for searching, scoring, message selection and much more. @@ -500,7 +500,7 @@ The index is the screen that you usually see first when you - start mutt-ng. It gives an overview over your emails in the + start Madmutt. It gives an overview over your emails in the currently opened mailbox. By default, this is your system mailbox. The information you see in the index is a list of emails, each with its number on the left, its flags (new email, important email, @@ -540,7 +540,7 @@ To give the user a good overview, it is possible to configure - mutt-ng to show different things in the pager with different + Madmutt to show different things in the pager with different colors. Virtually everything that can be described with a regular expression can be colored, e.g. URLs, email addresses or smileys. @@ -575,7 +575,7 @@ The sidebar comes in handy to manage mails which are spread - over different folders. All folders users setup mutt-ng to watch + over different folders. All folders users setup Madmutt to watch for new mail will be listed. The listing includes not only the name but also the number of total messages, the number of new and flagged messages. Items with new mail may be colored different @@ -598,7 +598,7 @@ lists the current configuration of key bindings and their associated commands including a short description, and currently unbound functions that still need to be associated with a key - binding (or alternatively, they can be called via the mutt-ng + binding (or alternatively, they can be called via the Madmutt command prompt). @@ -656,7 +656,7 @@ Attachment Menu - As will be later discussed in detail, mutt-ng features a good + As will be later discussed in detail, Madmutt features a good and stable MIME implementation, that is, is greatly supports sending and receiving messages of arbitrary type. The attachment menu displays a message's structure in detail: what @@ -697,7 +697,7 @@ Information is presented in menus, very similar to ELM. Here is a - tableshowing the common keys used to navigate menus in Mutt-ng. + tableshowing the common keys used to navigate menus in Madmutt. @@ -714,43 +714,43 @@ - j or Down - + j or Down + move to the next entry - k or Up - + k or Up + move to the previous entry - z or PageDn - + z or PageDn + go to the next page - Z or PageUp - + Z or PageUp + go to the previous page - = or Home - + = or Home + jump to the first entry - * or End - + * or End + jump to the last entry - q - + q + exit the current menu - ? - + ? + list all key bindings for the current menu @@ -771,7 +771,7 @@ Editing Input Fields - Mutt-ng has a builtin line editor which is used as the primary way to + Madmutt has a builtin line editor which is used as the primary way to input textual data such as email addresses or filenames. The keys used to move @@ -792,112 +792,112 @@ - A or Home - + A or Home + move to the start of the line - B or Left - + B or Left + move back one char - B - + B + move back one word - D or Delete - + D or Delete + delete the char under the cursor - E or End - + E or End + move to the end of the line - F or Right - + F or Right + move forward one char - F - + F + move forward one word - Tab - + Tab + complete filename or alias - T - + T + complete address with query - K - + K + delete to the end of the line - d - + d + delete to the end of the word - W - + W + kill the word in front of the cursor - U - + U + delete entire line - V - + V + quote the next typed key - Up - + Up + recall previous string from history - Down - + Down + recall next string from history - BackSpace - + BackSpace + kill the char in front of the cursor - u - + u + convert word to upper case - l - + l + convert word to lower case - c - + c + capitalize the word - G + G abort - Return + Return finish editing @@ -909,7 +909,7 @@ You can remap the editor functions using the - command. For example, to make + command. For example, to make the Delete key delete the character in front of the cursor rather than under, you could use @@ -926,9 +926,9 @@ Similar to many other mail clients, there are two modes in which mail - isread in Mutt-ng. The first is the index of messages in the mailbox, + isread in Madmutt. The first is the index of messages in the mailbox, which is - called the ``index'' in Mutt-ng. The second mode is the display of the + called the ``index'' in Madmutt. The second mode is the display of the message contents. This is called the ``pager.'' @@ -954,147 +954,147 @@ - c + c change to a different mailbox - c + c change to a folder in read-only mode - C + C copy the current message to another mailbox - C + C decode a message and copy it to a folder - s + s decode a message and save it to a folder - D + D delete messages matching a pattern - d + d delete the current message - F + F mark as important - l + l show messages matching a pattern - N + N mark message as new - o + o change the current sort method - O + O reverse sort the mailbox - q + q save changes and exit - s + s save-message - T + T tag messages matching a pattern - t + t toggle the tag on a message - t + t toggle tag on entire message thread - U + U undelete messages matching a pattern - u + u undelete-message - v + v view-attachments - x + x abort changes and exit - Return + Return display-message - Tab + Tab jump to the next new or unread message - @ + @ show the author's full e-mail address - $ + $ save changes to mailbox - / + / search - / + / search-reverse - L + L clear and redraw the screen - T + T untag messages matching a pattern @@ -1236,7 +1236,7 @@ Furthermore, the following flags reflect who the message is addressed to. They can be customized with the - variable. + variable. @@ -1293,7 +1293,7 @@ The Pager - By default, Mutt-ng uses its builtin pager to display the body of + By default, Madmutt uses its builtin pager to display the body of messages. The pager is very similar to the Unix program less though not nearly as featureful. @@ -1313,57 +1313,57 @@ - Return + Return go down one line - Space + Space display the next page (or next message if at the end of a message) - - + - go back to the previous page - n + n search for next match - S + S skip beyond quoted text - T + T toggle display of quoted text - ? + ? show key bindings - / + / search for a regular expression (pattern) - / + / search backwards for a regular expression - \ + \ toggle search pattern coloring - ^ + ^ jump to the top of the message @@ -1388,20 +1388,20 @@ features. For one, it will accept and translate the ``standard'' nroff sequences forbold and underline. These sequences are a series of either the letter, backspace - (H), the letter again for bold - or the letter, backspace, _ for denoting - underline. Mutt-ng will attempt to display these in bold and + (H), the letter again for bold + or the letter, backspace, _ for denoting + underline. Madmutt will attempt to display these in bold and underline respectively if your terminal supports them. If not, - you can use the bold and underline objects to specify a color or mono attribute for them. Additionally, the internal pager supports the ANSI escape - sequences for character attributes. Mutt-ng translates them + sequences for character attributes. Madmutt translates them into the correct color and character settings. The sequences - Mutt-ng supports are: ESC [ Ps;Ps;Ps;...;Ps + Madmutt supports are: ESC [ Ps;Ps;Ps;...;Ps m (see table below for possible values for Ps). @@ -1501,9 +1501,9 @@ - Mutt-ng uses these attributes for handling text/enriched messages, + Madmutt uses these attributes for handling text/enriched messages, and they - can also be used by an external + can also be used by an external script for highlighting purposes. Note: If you change the colors for your display, for example by changing the color associated with color2 for your xterm, then that color will be used instead of green. @@ -1539,73 +1539,73 @@ - D - + D + delete all messages in the current thread - U - + U + undelete all messages in the current thread - N - + N + jump to the start of the next thread - P - + P + jump to the start of the previous thread - R - + R + mark the current thread as read - d - + d + delete all messages in the current subthread - u - + u + undelete all messages in the current subthread - n - + n + jump to the start of the next subthread - p - + p + jump to the start of the previous subthread - r - + r + mark the current subthread as read - t - + t + toggle the tag on the current thread - v - + v + toggle collapse for the current thread - V - + V + toggle collapse for all threads - P - + P + jump to parent message in thread @@ -1621,18 +1621,18 @@ 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 onthe screen. See %M in - . + . For example, you could use - %?M?(#%03M)&(%4l)? in + %?M?(#%03M)&(%4l)? in to optionally display the number of hidden messages if the thread is collapsed. - See also the variable. + See also the variable. @@ -1641,21 +1641,21 @@ Miscellaneous Functions - a + a Creates a new alias based upon the current message (or prompts for a - new one). Once editing is complete, an - command is added to the file specified by the + new one). Once editing is complete, an + command is added to the file specified by the variable for future use. Note: - Specifying an - does not add the aliases specified there-in, you must also + Specifying an + does not add the aliases specified there-in, you must also the file. - P + P @@ -1663,22 +1663,22 @@ encrypted with PGP the "traditional" way, that is, without proper MIME tagging. Technically, this function will temporarily change the MIME content types of the body parts containing PGP data; this - is similar to the + is similar to the function's effect. - h + h - Toggles the weeding of message header fields specified by + Toggles the weeding of message header fields specified by commands. - e + e @@ -1690,9 +1690,9 @@ - - (default: E on the attachment menu, and in the pager and index - menus; T on the compose menu) + + (default: E on the attachment menu, and in the pager and index + menus; T on the compose menu) @@ -1712,7 +1712,7 @@ - : + : @@ -1720,13 +1720,13 @@ a configuration file. A common use is to check the settings of variables, or - in conjunction with to change + in conjunction with to change settings on the fly. - K + K @@ -1735,7 +1735,7 @@ - F + F @@ -1744,16 +1744,16 @@ - L + L Reply to the current or tagged message(s) by extracting any addresses which - match the regular expressions given by the + match the regular expressions given by the commands, but also honor any Mail-Followup-To header(s) if the - + configuration variable is set. Using this when replying to messages posted to mailing lists helps avoid duplicate copies being sent to the @@ -1762,21 +1762,21 @@ - + Asks for an external Unix command and pipes the current or tagged message(s) to it. The variables - , - , - and - + , + , + and + control the exact behavior of this function. - e + e @@ -1787,7 +1787,7 @@ folders". It can conveniently be used to forward MIME messages while preserving the original mail structure. Note that the amount of headers - included here depends on the value of the + included here depends on the value of the variable. @@ -1799,26 +1799,26 @@ - ! + ! Asks for an external Unix command and executes it. The - + can be used to control - whether Mutt-ng will wait for a key to be pressed when the command + whether Madmutt 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. - T + T The pager uses the - + variable to detect quoted text when displaying the body of the message. This function toggles the displayof the quoted material in the message. It is particularly @@ -1828,7 +1828,7 @@ - S + S @@ -1868,38 +1868,38 @@ - m - + m + compose a new message - r - + r + reply to sender - g - + g + reply to all recipients - L - + L + reply to mailing list address - f - + f + forward message - b - + b + bounce (remail) message - k - + k + mail a PGP public key to someone @@ -1919,50 +1919,50 @@ Composing new messages - When you want to send an email using mutt-ng, simply press m on - your keyboard. Then, mutt-ng asks for the recipient via a prompt in + When you want to send an email using Madmutt, simply press m on + your keyboard. Then, Madmutt asks for the recipient via a prompt in the last line: - -To: + +To: After you've finished entering the recipient(s), press return. If you want to send an email to more than one recipient, separate the email - addresses using the comma ",". Mutt-ng then asks + addresses using the comma ",". Madmutt then asks you for the email subject. Again, press return after you've entered it. After that, - mutt-ng + Madmutt got the most important information from you, and starts up an editor where you can then enter your email. The editor that is called is selected in the following way: you - can e.g. set it in the mutt-ng configuration: + can e.g. set it in the Madmutt configuration: - + set editor = "vim +/^$/ -c ':set tw=72'" set editor = "nano" -set editor = "emacs" +set editor = "emacs" - If you don't set your preferred editor in your configuration, mutt-ng - first looks whether the environment variable is set, and if + If you don't set your preferred editor in your configuration, Madmutt + first looks whether the environment variable is set, and if so, it takes its value as editor command. Otherwise, it has a look - at and takes its value if it is set. If no + at and takes its value if it is set. If no editor command - can be found, mutt-ng simply assumes to be the + can be found, Madmutt simply assumes to be the default editor, since it's the most widespread editor in the Unix world and it's pretty @@ -1971,7 +1971,7 @@ set editor = "emacs" When you've finished entering your message, save it and quit your - editor. Mutt-ng will then present you with a summary screen, the + editor. Madmutt will then present you with a summary screen, the compose menu. On the top, you see a summary of the most important available key commands. @@ -1989,13 +1989,13 @@ set editor = "emacs" - At this point, you can add more attachments, pressing a, you - can edit the recipient addresses, pressing t for + At this point, you can add more attachments, pressing a, you + can edit the recipient addresses, pressing t for the "To:" field, - c for the "Cc:" field, and b + c for the "Cc:" field, and b for the "Bcc: field. You can - also edit the subject the subject by simply pressing s or the - email message that you've entered before by pressing e. You will + also edit the subject the subject by simply pressing s or the + email message that you've entered before by pressing e. You will then again return to the editor. You can even edit the sender, by pressing <esc>f, but this shall only be used with @@ -2003,15 +2003,15 @@ set editor = "emacs" - Alternatively, you can configure mutt-ng in a way that most of the + Alternatively, you can configure Madmutt in a way that most of the above settings can be edited using the editor. Therefore, you only need to add the following to your configuration: - -set edit_headers + +set edit_headers @@ -2035,103 +2035,103 @@ set edit_headers - a - + a + attach a file - A - + A + attach message(s) to the message - k - + k + attach a PGP public key - d - + d + edit description on attachment - D - + D + detach a file - t - + t + edit the To field - f - + f + edit the From field - r - + r + edit the Reply-To field - c - + c + edit the Cc field - b - + b + edit the Bcc field - y - + y + send the message - s - + s + edit the Subject - S - + S + select S/MIME options - f - + f + specify an ``Fcc'' mailbox - p - + p + select PGP options - P - + P + postpone this message until later - q - + q + quit (abort) sending the message - w - + w + write the message to a folder - i - + i + check spelling (if available on your system) - F - + F + wipe passphrase(s) from memory @@ -2148,7 +2148,7 @@ set edit_headers certainoperations like composing a new mail, replying, forwarding, etc. are not permitted when you are in that folder. The %r - in + in will change to a 'A' to indicate that you are in attach-message mode. @@ -2167,22 +2167,22 @@ set edit_headers When you want to reply to an email message, select it in the index - menu and then press r. Mutt-ng's behaviour is + menu and then press r. Madmutt's behaviour is then similar to the behaviour when you compose a message: first, you will be asked for - the recipient, then for the subject, and then, mutt-ng will start + the recipient, then for the subject, and then, Madmutt will start the editor with the quote attribution and the quoted message. This can e.g. look like the example below. - + On Mon, Mar 07, 2005 at 05:02:12PM +0100, Michael Svensson wrote: > 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. +> project will go live. @@ -2199,28 +2199,28 @@ On Mon, Mar 07, 2005 at 05:02:12PM +0100, Michael Svensson wrote: The quote attribution is configurable, by default it is set to - -set attribution = "On %d, %n wrote:" + +set attribution = "On %d, %n wrote:" It can also be set to something more compact, e.g. - -set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:" + +set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:" The example above results in the following attribution: - + * Michael Svensson <svensson@foobar.com> [05-03-06 17:02]: > 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. +> project will go live. @@ -2252,8 +2252,8 @@ set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:"g - instead of r to do a reply, + functionalityensures that when you press g + instead of r to do a reply, each and every recipient that is contained in the original message will receive a copy of the message, either as normal recipient or as "Cc:" recipient. @@ -2271,16 +2271,16 @@ set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:" When you use mailing lists, it's generally better to send your reply to a message only to the list instead of the list and the - original author. To make this easy to use, mutt-ng features list + original author. To make this easy to use, Madmutt features list replies. - To do a list reply, simply press L. If the email + To do a list reply, simply press L. If the email contains a Mail-Followup-To: header, its value will be used as reply - address. Otherwise, mutt-ng searches through all mail addresses in + address. Otherwise, Madmutt searches through all mail addresses in the original message and tries to match them a list of regular expressions which can be specified using the lists command. If any of the regular expression matches, a mailing @@ -2289,8 +2289,8 @@ set attribution = "attribution="* %n <%a> [%(%y-%m-%d %H:%M)]:" - -lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ + +lists linuxevent@luga\.at vuln-dev@ Madmutt-users@ @@ -2327,7 +2327,7 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ Fcc: filename - Mutt-ng will pick up filename + Madmutt will pick up filename just as if you had used the edit-fcc function in the compose menu. @@ -2335,8 +2335,8 @@ lists linuxevent@luga\.at vuln-dev@ mutt-ng-users@ You can also attach files to your message by specifying - -Attach: filename [description] + +Attach: filename [description] where filename is the file to attach and description @@ -2347,13 +2347,13 @@ Attach: filename [description] When replying to messages, if you remove the In-Reply-To: field from - the header field, Mutt-ng will not generate a References: field, which + the header field, Madmutt will not generate a References: field, which allows you to create a new message thread. - Also see the and - variables + Also see the and + variables @@ -2363,24 +2363,24 @@ Attach: filename [description] - Using Mutt-ng with PGP + Using Madmutt with PGP If you want to use PGP, you can specify - -Pgp: [E | S | S id] + +Pgp: [E | S | S id] ``E'' encrypts, ``S'' signs and ``S<id>'' signs with the given key, setting - + 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 any questions about keys which have a + Madmutt 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 @@ -2391,7 +2391,7 @@ Pgp: [E | S | S id] In these cases, you are dropped into a menu with a list of keys from which you can select one. When you quit this menu, or mutt can't find any matching keys, you are prompted for a user ID. You can, as - usually, abort this prompt using G. When + usually, abort this prompt using G. When you do so, mutt will return to the compose screen. @@ -2403,7 +2403,7 @@ Pgp: [E | S | S id] Most fields of the entries in the key selection menu (see also - ) + ) have obvious meanings. But some explanations on the capabilities, flags, and validity fields are in order. @@ -2509,7 +2509,7 @@ Pgp: [E | S | S id] To use it, you'll have to obey certain restrictions. Most important, you cannot use the Cc and Bcc headers. To tell - Mutt-ng to use mixmaster, you have to select a remailer chain, using + Madmutt to use mixmaster, you have to select a remailer chain, using the mix function on the compose menu. @@ -2524,7 +2524,7 @@ Pgp: [E | S | S id] and chain-next functions, which are by default bound to the left - and right arrows and to the h and l keys (think vi + and right arrows and to the h and l keys (think vi keyboard bindings). To insert a remailer at the current chain position, use the insert function. To append a remailer behind @@ -2543,7 +2543,7 @@ Pgp: [E | S | S id] Note that different remailers do have different capabilities, indicated in the %c entry of the remailer menu lines (see - ). + ). Most important is the ``middleman'' capability, indicated by a capital ``M'': This means that the remailer in question cannot be used as the final @@ -2569,13 +2569,13 @@ Pgp: [E | S | S id] Often, it is necessary to forward mails to other people. - Therefore, mutt-ng supports forwarding messages in two different + Therefore, Madmutt supports forwarding messages in two different ways. The first one is regular forwarding, as you probably know it from - other mail clients. You simply press f, enter the + other mail clients. You simply press f, enter the recipient email address, the subject of the forwarded email, and then you can edit the message to be forwarded in the editor. The forwarded @@ -2585,7 +2585,7 @@ Pgp: [E | S | S id] - + ----- Forwarded message from Lucas User <luser@example.com> ----- From: Lucas User <luser@example.com> @@ -2596,7 +2596,7 @@ Subject: Re: blackmail Pay me EUR 50,000.- cash or your favorite stuffed animal will die a horrible death. ------ End forwarded message ----- +----- End forwarded message ----- @@ -2607,12 +2607,12 @@ a horrible death. - The second mode of forwarding emails with mutt-ng is the + The second mode of forwarding emails with Madmutt is the so-called bouncing: when you bounce an email to another address, it will be sent in practically the same format you send it (except for headers that are created during transporting the - message). To bounce a message, press b and enter the + message). To bounce a message, press b and enter the recipient email address. By default, you are then asked whether you really want to bounce the message to the specified recipient. If you answer @@ -2643,8 +2643,8 @@ a horrible death. used in the compose menu, the body of your message and attachments are stored in the mailbox specified by the - variable. This means that you can recall the - message even if you exit Mutt-ng and then restart it at a later time. + variable. This means that you can recall the + message even if you exit Madmutt and then restart it at a later time. @@ -2667,7 +2667,7 @@ a horrible death. - See also the quad-option. + See also the quad-option. @@ -2692,39 +2692,39 @@ a horrible death. Locations of Configuration Files - While the default configuration (or ``preferences'') make Mutt-ng + While the default configuration (or ``preferences'') make Madmutt usable right out - of the box, it is often desirable to tailor Mutt-ng to suit your own + of the box, it is often desirable to tailor Madmutt to suit your own tastes. When - Mutt-ng is first invoked, it will attempt to read the ``system'' + Madmutt is first invoked, it will attempt to read the ``system'' configuration file (defaults set by your local system administrator), unless the ``-n'' commandline option is specified. This file is - typically /usr/local/share/muttng/Muttngrc or - /etc/Muttngrc + typically /usr/local/share/madmutt/madmuttrc or + /etc/madmuttrc , - Mutt-ng users will find this file in - /usr/local/share/muttng/Muttrc + Madmutt users will find this file in + /usr/local/share/madmutt/Muttrc or - /etc/Muttngrc. Mutt will next look for a file named + /etc/madmuttrc. Mutt will next look for a file named .muttrc - in your home directory, Mutt-ng will look for .muttngrc. If this file + in your home directory, Madmutt will look for .madmuttrc. If this file does not exist and your home directory has a subdirectory named .mutt , - mutt try to load a file named .muttng/muttngrc. + mutt try to load a file named .madmutt/madmuttrc. - .muttrc (or .muttngrc for - Mutt-ng) is the file where you will + .muttrc (or .madmuttrc for + Madmutt) is the file where you will usually place your commands to - configure Mutt-ng. + configure Madmutt. @@ -2741,8 +2741,8 @@ a horrible death. When multiple commands are used, they must be separated by a semicolon (;). - -set realname='Mutt-ng user' ; ignore x- + +set realname='Madmutt user' ; ignore x- The hash mark, or pound sign (``#''), is used as a ``comment'' character. You can use it to @@ -2752,8 +2752,8 @@ set realname='Mutt-ng user' ; ignore x- - -my_hdr X-Disclaimer: Why are you listening to me? # This is a comment + +my_hdr X-Disclaimer: Why are you listening to me? # This is a comment @@ -2783,8 +2783,8 @@ my_hdr X-Disclaimer: Why are you listening to me? # This is a comment -set realname="Michael \"MuttDude\" Elkins" + +set realname="Michael \"MuttDude\" Elkins" @@ -2801,7 +2801,7 @@ set realname="Michael \"MuttDude\" Elkins" - Please note that, unlike the various shells, mutt-ng interprets a + Please note that, unlike the various shells, Madmutt interprets a ``\'' at the end of a line also in comments. This allows you to disable a command @@ -2810,9 +2810,9 @@ set realname="Michael \"MuttDude\" Elkins" - + # folder-hook . \ -set realname="Michael \"MuttDude\" Elkins" +set realname="Michael \"MuttDude\" Elkins" @@ -2834,12 +2834,12 @@ set realname="Michael \"MuttDude\" Elkins" - + line1\ line2a # line2b\ line3\ line4 -line5 +line5 @@ -2880,8 +2880,8 @@ line5 - -my_hdr X-Operating-System: `uname -a` + +my_hdr X-Operating-System: `uname -a` @@ -2905,16 +2905,16 @@ my_hdr X-Operating-System: `uname -a` - -set record=+sent_on_$HOSTNAME + +set record=+sent_on_$HOSTNAME - sets the variable to the + sets the variable to the string +sent_on_ and appends the value of the evironment - variable . + variable . @@ -2935,23 +2935,23 @@ set record=+sent_on_$HOSTNAME - -set imap_home_namespace = $folder + +set imap_home_namespace = $folder - would set the value of - to the value to which + would set the value of + to the value to which is currently set to. Note: There're no logical links established in such cases so - that the the value for + that the the value for won't change even - if gets changed. + if gets changed. @@ -2967,7 +2967,7 @@ set imap_home_namespace = $folder Self-Defined Variables - Mutt-ng flexibly allows users to define their own variables. To + Madmutt 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 @@ -2982,9 +2982,9 @@ set imap_home_namespace = $folder - + macro generic <F1> "!less -r /path/to/manual" "Show manual" -macro pager <F1> "!less -r /path/to/manual" "Show manual" +macro pager <F1> "!less -r /path/to/manual" "Show manual" @@ -2998,11 +2998,11 @@ macro pager <F1> "!less -r /path/to/manual" "Show manual" - + set user_manualcmd = "!less -r /path/to_manual" macro generic <F1> "$user_manualcmd<enter>" "Show manual" macro pager <F1> "$user_manualcmd<enter>" "Show manual" -macro index <F1> "$user_manualcmd<enter>" "Show manual" +macro index <F1> "$user_manualcmd<enter>" "Show manual" @@ -3012,8 +3012,8 @@ macro index <F1> "$user_manualcmd<enter>" "Show manual" - -macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns" + +macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns" @@ -3041,9 +3041,9 @@ macro index <F2> "$user_manualcmd | grep '\^[ ]\\+~. '" "Show Patterns" - + set user_foo = 42 -set user_foo = 666 +set user_foo = 666 @@ -3055,8 +3055,8 @@ set user_foo = 666 - -set ?user_foo + +set ?user_foo @@ -3066,8 +3066,8 @@ set ?user_foo - -reset user_foo + +reset user_foo @@ -3078,8 +3078,8 @@ reset user_foo - -unset user_foo + +unset user_foo @@ -3097,7 +3097,7 @@ unset user_foo 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 variables. These are prefixed with - muttng_ and are read-only, i.e. they cannot + madmutt_ and are read-only, i.e. they cannot be set, unset or reset. The reference chapter lists all available variables. @@ -3113,8 +3113,8 @@ unset user_foo - -$ muttng -Q muttng_docdir + +$ madmutt -Q madmutt_docdir @@ -3126,8 +3126,8 @@ $ muttng -Q muttng_docdir - -set user_manualcmd = '!less -r /path/to_manual' + +set user_manualcmd = '!less -r /path/to_manual' @@ -3137,8 +3137,8 @@ set user_manualcmd = '!less -r /path/to_manual' - -set user_manualcmd = "!less -r $muttng_docdir/manual.txt" + +set user_manualcmd = "!less -r $madmutt_docdir/manual.txt" @@ -3147,7 +3147,7 @@ set user_manualcmd = "!less -r $muttng_docdir/manual.txt" - Please note that by the type of quoting, muttng determines when + Please note that by the type of quoting, madmutt determines when to expand these values: when it finds double quotes, the value will be expanded during reading the setup files but when it finds single quotes, it'll expand it at runtime as needed. @@ -3159,8 +3159,8 @@ set user_manualcmd = "!less -r $muttng_docdir/manual.txt" - -folder-hook . "set user_current_folder = $muttng_folder_name" + +folder-hook . "set user_current_folder = $madmutt_folder_name" @@ -3171,21 +3171,21 @@ folder-hook . "set user_current_folder = $muttng_folder_name" - -folder-hook . "set user_current_folder = some_folder" + +folder-hook . "set user_current_folder = some_folder" with some_folder being the name of the - first folder muttng + first folder madmutt opens. On the contrary, - -folder-hook . 'set user_current_folder = $muttng_folder_name' + +folder-hook . 'set user_current_folder = $madmutt_folder_name' @@ -3202,8 +3202,8 @@ folder-hook . 'set user_current_folder = $muttng_folder_name' - -folder-hook . 'source ~/.mutt/score-$muttng_folder_name' + +folder-hook . 'source ~/.mutt/score-$madmutt_folder_name' @@ -3223,17 +3223,17 @@ folder-hook . 'source ~/.mutt/score-$muttng_folder_name' operation they're converted to and from string. That means that there's no need to worry about types when referencing any variable. As an example, the following can be used without harm (besides - makeing muttng very likely behave strange): + makeing madmutt very likely behave strange): - + set read_inc = 100 set folder = $read_inc set read_inc = $folder set user_magic_number = 42 -set folder = $user_magic_number +set folder = $user_magic_number @@ -3245,15 +3245,15 @@ set folder = $user_magic_number Defining/Using aliases - + key address [, address,...] - + It's usually very cumbersome to remember or type out the address of someone - you are communicating with. Mutt-ng allows you to create ``aliases'' + you are communicating with. Madmutt allows you to create ``aliases'' which map a short string to a full address. @@ -3270,38 +3270,38 @@ set folder = $user_magic_number - + [* | key ... ] - + - + alias muttdude me@cs.hmc.edu (Michael Elkins) -alias theguys manny, moe, jack +alias theguys manny, moe, jack - Unlike other mailers, Mutt-ng doesn't require aliases to be defined + Unlike other mailers, Madmutt 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 . + a configuration file, as long as this file is . Consequently, you can have multiple alias files, or you can have all aliases defined in your muttrc. - On the other hand, the + 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-ng will happily append aliases to any file, but + in the sense that Madmutt will happily append aliases to any file, but in - order for the new aliases to take effect you need to explicitly + order for the new aliases to take effect you need to explicitly this file too. @@ -3311,10 +3311,10 @@ alias theguys manny, moe, jack - -source /usr/local/share/Mutt-ng.aliases + +source /usr/local/share/Madmutt.aliases source ~/.mail_aliases -set alias_file=~/.mail_aliases +set alias_file=~/.mail_aliases @@ -3326,7 +3326,7 @@ set alias_file=~/.mail_aliases prompt. You can also enter aliases in your editor at the appropriate headers if you have the - + variable set. @@ -3361,9 +3361,9 @@ set alias_file=~/.mail_aliases Changing the default key bindings - + map key function - + @@ -3390,7 +3390,7 @@ set alias_file=~/.mail_aliases the other menus except for the pager and editor modes. If a key is not defined in - another menu, Mutt-ng will look for a binding to use in this + another menu, Madmutt 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 @@ -3648,21 +3648,21 @@ set alias_file=~/.mail_aliases - Usage: alias charset + Usage: alias charset - Usage: charset local-charset + Usage: charset local-charset - The command defines an alias for a + The 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 command defines a system-specific + The 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 @@ -3679,25 +3679,25 @@ set alias_file=~/.mail_aliases Setting variables based upon mailbox - Usage: [!]regexp command + Usage: [!]regexp command It is often desirable to change settings based on which mailbox you are - reading. The command provides a method by which you can + reading. The 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 's, they are executed in the order given in + matches multiple 's, they are executed in the order given in the muttrc. Note: if you use the ``!'' shortcut - for at the beginning of the + for at the beginning of the pattern, you must place it inside of double or single quotes in order to distinguish it from the logical not operator for the expression. @@ -3712,8 +3712,8 @@ set alias_file=~/.mail_aliases - -folder-hook mutt set sort=threads + +folder-hook mutt set sort=threads @@ -3726,8 +3726,8 @@ folder-hook mutt set sort=threads - -folder-hook . set sort=date-sent + +folder-hook . set sort=date-sent @@ -3741,9 +3741,9 @@ folder-hook . set sort=date-sent Keyboard macros - + menu key sequence [description] - + @@ -3752,7 +3752,7 @@ folder-hook . set sort=date-sent actions. When you press key in menu menu - ,Mutt-ng will behave as if + ,Madmutt will behave as if you had typed sequence. So if you have a common sequence of commands you type, you can create a macro to execute those commands with a @@ -3769,7 +3769,7 @@ folder-hook . set sort=date-sent key and sequence are - expanded by the same rules as the . There are some additions however. The first is that control characters in sequence can also be specified as ^x. In order to get a @@ -3778,7 +3778,7 @@ folder-hook . set sort=date-sent invoke a function directly, you can use the format <key name> and <function name> .For a listing of key names see the - section on . Functions are + section on . Functions are listed in the functions. @@ -3789,7 +3789,7 @@ folder-hook . set sort=date-sent the user having particular key definitions. This makes them more robustand portable, and also facilitates defining of macros in files used by more - than one user (eg. the system Muttngrc). + than one user (eg. the system madmuttrc). @@ -3813,17 +3813,17 @@ folder-hook . set sort=date-sent Using color and mono video attributes - object foreground background [regexp] + object foreground background [regexp] - index foreground pattern + index foreground pattern - index pattern [pattern ...] + index pattern [pattern ...] - If your terminal supports color, you can spice up Mutt-ng by creating + If your terminal supports color, you can spice up Madmutt by creating your own color scheme. To define the color of an object (type of information), you @@ -3859,7 +3859,7 @@ folder-hook . set sort=date-sent - error (error messages printed by Mutt-ng) + error (error messages printed by Madmutt) @@ -3909,7 +3909,7 @@ folder-hook . set sort=date-sent - quoted (text matching in the body of a message) + quoted (text matching in the body of a message) @@ -4044,18 +4044,18 @@ folder-hook . set sort=date-sent If your terminal supports it, the special keyword default can be used as a transparent color. The value brightdefault is also valid. - If Mutt-ng is linked against the S-Lang library, + If Madmutt is linked against the S-Lang library, you also need to set - the environment variable to the default + the environment variable to the default colors of your terminal for this to work; for example (for Bourne-like shells): - + set COLORFGBG="green;black" -export COLORFGBG +export COLORFGBG @@ -4080,7 +4080,7 @@ export COLORFGBG - Mutt-ng also recognizes the keywords color0, + Madmutt also recognizes the keywords color0, color1 ,..., @@ -4102,13 +4102,13 @@ export COLORFGBG - object attribute [regexp] + object attribute [regexp] - index attribute pattern + index attribute pattern - index pattern [pattern ...] + index pattern [pattern ...] @@ -4163,11 +4163,11 @@ export COLORFGBG Ignoring (weeding) unwanted message headers - pattern [pattern ...] + pattern [pattern ...] - pattern [pattern ...] + pattern [pattern ...] @@ -4188,7 +4188,7 @@ export COLORFGBG To remove a previously added token from the list, use the ``unignore'' command. - The ``unignore'' command will make Mutt-ng display headers with the + The ``unignore'' command will make Madmutt display headers with the given pattern. For example, if you do ``ignore x-'' it is possible to ``unignore x-mailer''. @@ -4201,12 +4201,12 @@ export COLORFGBG For example: - + # Sven's draconian header weeding ignore * unignore from date subject to cc unignore organization organisation x-mailer: x-newsreader: x-mailing-list: -unignore posted-to: +unignore posted-to: @@ -4220,11 +4220,11 @@ unignore posted-to: Alternative addresses - regexp [regexp ...] + regexp [regexp ...] - regexp [regexp ...] + regexp [regexp ...] @@ -4234,7 +4234,7 @@ unignore posted-to: 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 .) + (See .) @@ -4290,7 +4290,7 @@ unignore posted-to: Introduction - Mutt-ng contains support for so-called format=flowed messages. + Madmutt contains support for so-called format=flowed messages. In the beginning of email, each message had a fixed line width, and it was enough for displaying them on fixed-size terminals. But times changed, and nowadays hardly anybody still uses fixed-size terminals: @@ -4305,7 +4305,7 @@ unignore posted-to: For introductory information on format=flowed messages, see - . + . @@ -4315,7 +4315,7 @@ unignore posted-to: When you receive emails that are marked as format=flowed - messages, and is formatted correctly, mutt-ng will try to reformat + messages, and is formatted correctly, Madmutt 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: @@ -4323,8 +4323,8 @@ unignore posted-to: - -set wrapmargin = 10 + +set wrapmargin = 10 @@ -4340,8 +4340,8 @@ set wrapmargin = 10 - -set max_line_length = 120 + +set max_line_length = 120 @@ -4358,24 +4358,24 @@ set max_line_length = 120 - + >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. +>project will go live. This obviously doesn't look very nice, and it makes it very hard to differentiate between text and quoting character. The - solution is to configure mutt-ng to "stuff" the quoting: + solution is to configure Madmutt to "stuff" the quoting: - -set stuff_quoted + +set stuff_quoted @@ -4385,11 +4385,11 @@ set stuff_quoted - + > 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. +> project will go live. @@ -4399,20 +4399,20 @@ set stuff_quoted Sending - If you want mutt-ng to send emails with format=flowed set, you + If you want Madmutt to send emails with format=flowed set, you need to explicitly set it: - -set text_flowed + +set text_flowed Additionally, you have to use an editor which supports writing - format=flowed-conforming emails. For , this is + format=flowed-conforming emails. For , this is done by adding w to the formatoptions (see :h formatoptions @@ -4428,8 +4428,8 @@ set text_flowed 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 () as it does not + making manual formattings within the editor. Also note that Madmutt + currently violates the standard () as it does not space-stuff lines starting with: @@ -4458,7 +4458,7 @@ set text_flowed Additional Notes - For completeness, the variable provides the mechanism + For completeness, the variable provides the mechanism to generate a DelSp=yes parameter on outgoing @@ -4486,20 +4486,20 @@ set text_flowed Mailing lists - regexp [regexp ...] + regexp [regexp ...] - regexp [regexp ...] + regexp [regexp ...] - regexp [regexp ...] + regexp [regexp ...] - regexp [regexp ...] + regexp [regexp ...] - Mutt-ng has a few nice features for using-lists. + Madmutt has a few nice features for using-lists. 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 @@ -4513,12 +4513,12 @@ set text_flowed against receiving personal CCs of list messages. Also note that the generation of the Mail-Followup-To header is controlled by the - + configuration variable. - More precisely, Mutt-ng maintains lists of patterns for the addresses + More precisely, Madmutt 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''. @@ -4534,10 +4534,10 @@ set text_flowed Specify as much of the address as you need to to remove ambiguity. For - example, if you've subscribed to the Mutt-ng mailing list, you will + example, if you've subscribed to the Madmutt mailing list, you will receive mail addressed to mutt-users@mutt.org. So, to tell - Mutt-ng that this is a + Madmutt 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. @@ -4569,7 +4569,7 @@ set text_flowed Using Multiple spool mailboxes - Usage: [!]pattern mailbox + Usage: [!]pattern mailbox @@ -4602,10 +4602,10 @@ set text_flowed Defining mailboxes which receive mail - [!]filename [filename ... ] + [!]filename [filename ... ] - [!]filename [filename ... ] + [!]filename [filename ... ] @@ -4625,7 +4625,7 @@ set text_flowed files specified by the mailboxes command, and indicate which contain new - messages. Mutt-ng will automatically enter this mode when invoked from + messages. Madmutt will automatically enter this mode when invoked from the command line with the -y option. @@ -4643,7 +4643,7 @@ set text_flowed frm or any other - program which accesses the mailbox might cause Mutt-ng to never detect + program which accesses the mailbox might cause Madmutt to never detect new mail for that mailbox if they do not properly reset the access time. Backup tools are another common reason for updated access times. @@ -4656,8 +4656,8 @@ set text_flowed command are resolved when the command is executed, so if these names contain shortcuts (such as ``='' and ``!''), any variable - definition that affect these characters (like - and ) + definition that affect these characters (like + and ) should be executed before the mailboxes command. @@ -4671,10 +4671,10 @@ set text_flowed User defined headers - string + string - field [field ...] + field [field ...] @@ -4689,8 +4689,8 @@ set text_flowed - -my_hdr Organization: A Really Big Company, Anytown, USA + +my_hdr Organization: A Really Big Company, Anytown, USA @@ -4702,13 +4702,13 @@ my_hdr Organization: A Really Big Company, Anytown, USA not allowed between the keyword and - the colon (``:''). The standard for electronic mail () says that - space is illegal there, so Mutt-ng enforces the rule. + the colon (``:''). The standard for electronic mail () says that + space is illegal there, so Madmutt enforces the rule. If you would like to add a header field to a single message, you should - either set the + either set the variable, or use the edit-headers function (default: ``E'') in the send-menu so @@ -4723,8 +4723,8 @@ my_hdr Organization: A Really Big Company, Anytown, USA - -unmy_hdr to cc + +unmy_hdr to cc @@ -4737,11 +4737,11 @@ unmy_hdr to cc Defining the order of headers when viewing messages - header header [header ...] + header header [header ...] - [ * | header header ...] + [ * | header header ...] @@ -4758,8 +4758,8 @@ unmy_hdr to cc - -hdr_order From Date: From: To: Cc: Subject: + +hdr_order From Date: From: To: Cc: Subject: @@ -4773,7 +4773,7 @@ hdr_order From Date: From: To: Cc: Subject: Specify default save filename - Usage: [!]pattern filename + Usage: [!]pattern filename @@ -4788,7 +4788,7 @@ hdr_order From Date: From: To: Cc: Subject: - See for information on + See for information on the exact format of pattern. @@ -4798,14 +4798,14 @@ hdr_order From Date: From: To: Cc: Subject: - + save-hook me@(turing\\.)?cs\\.hmc\\.edu$ +elkins -save-hook aol\\.com$ +spam +save-hook aol\\.com$ +spam - Also see the + Also see the command. @@ -4819,22 +4819,22 @@ save-hook aol\\.com$ +spam Specify default Fcc: mailbox when composing - Usage: [!]pattern mailbox + Usage: [!]pattern mailbox This command is used to save outgoing mail in a mailbox other than - . Mutt-ng searches the initial + . Madmutt searches the initial list of message recipients for the first matching regexp and uses mailbox as the default Fcc: mailbox. If no match is found the message will be saved - to mailbox. + to mailbox. - See for information on + See for information on the exact format of pattern. @@ -4843,14 +4843,14 @@ save-hook aol\\.com$ +spam - -fcc-hook [@.]aol\\.com$ +spammers + +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 - command. + command. @@ -4863,12 +4863,12 @@ fcc-hook [@.]aol\\.com$ +spammers Specify default save filename and default Fcc: mailbox at once - Usage: [!]pattern mailbox + Usage: [!]pattern mailbox - This command is a shortcut, equivalent to doing both a - and a with its arguments. + This command is a shortcut, equivalent to doing both a + and a with its arguments. @@ -4883,13 +4883,13 @@ fcc-hook [@.]aol\\.com$ +spammers - Usage: [!]pattern command + Usage: [!]pattern command - Usage: [!]pattern command + Usage: [!]pattern command - Usage: [!]pattern command + Usage: [!]pattern command @@ -4903,42 +4903,42 @@ fcc-hook [@.]aol\\.com$ +spammers - is matched against the message you are + is matched against the message you are replying to, instead of the message you are sending - . is + . is matched against all messages, both new and replies .Note: - s are matched before the - , regardless + s are matched before the + , regardless of the order specified in the users's configuration file. - is matched every time a message is + is matched every time a message is changed, either by editing it, or by using the compose menu to change its recipients - or subject. is executed after + or subject. is executed after ,and - can, e.g., be used to set parameters such as the + can, e.g., be used to set parameters such as the variable depending on the message's sender address. - For each type of or , when multiple matches + For each type of or , when multiple matches occur, commands are executed in the order they are specified in the muttrc (for that type of hook). - See for information on + See for information on the exact format of pattern. @@ -4950,21 +4950,21 @@ fcc-hook [@.]aol\\.com$ +spammers Another typical use for this command is to change the values of the - , - and , + and variables in order to change the language of the attributions and signatures based upon the recipients. - Note: the 's are only + Note: the '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 to be executed. Also note that + message will NOT cause any to be executed. Also note that 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 . + from a . @@ -4977,7 +4977,7 @@ fcc-hook [@.]aol\\.com$ +spammers Change settings before formatting a message - Usage: [!]pattern command + Usage: [!]pattern command @@ -4991,16 +4991,16 @@ fcc-hook [@.]aol\\.com$ +spammers - See for + See for information on the exact format of pattern. Example: - + message-hook ~A 'set pager=builtin' -message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""' +message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""' @@ -5014,7 +5014,7 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""'Choosing the cryptographic key of the recipient - Usage: pattern keyid + Usage: pattern keyid @@ -5022,8 +5022,8 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""' command provides a method by which + or because, for some reasons, you need to override the key Madmutt + wouldnormally use. The 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. @@ -5045,20 +5045,20 @@ message-hook '~f freshmeat-news' 'set pager="less \"+/^ subject:.*\""'Adding key sequences to the keyboard buffer - string + string This command adds the named string to the keyboard buffer. The string may contain control characters, key names and function - names like the sequence string in the command. You may use it to + names like the sequence string in the command. You may use it to automatically run a sequence of commands at startup, or when entering certain folders. For example, the following command will automatically collapse all threads when entering a folder: - -folder-hook . 'push <collapse-all>' + +folder-hook . 'push <collapse-all>' @@ -5072,7 +5072,7 @@ folder-hook . 'push <collapse-all>' Executing functions - function [function ... ] + function [function ... ] @@ -5091,10 +5091,10 @@ folder-hook . 'push <collapse-all>' Message Scoring - pattern value + pattern value - pattern [pattern ... ] + pattern [pattern ... ] @@ -5102,7 +5102,7 @@ folder-hook . 'push <collapse-all>' when you read many different mailing lists, and take part in discussions, it is always useful to have the important messages marked and the annoying messages or the ones that you aren't - interested in deleted. For this purpose, mutt-ng features a + interested in deleted. For this purpose, Madmutt features a mechanism called ``scoring''. @@ -5117,9 +5117,9 @@ folder-hook . 'push <collapse-all>' - -score "~f nion@muttng\.org" 50 -score "~f @sco\.com" -100 + +score "~f nion@madmutt\.org" 50 +score "~f @sco\.com" -100 @@ -5131,8 +5131,8 @@ score "~f @sco\.com" -100 - -score "~f santaclaus@northpole\.int" =666 + +score "~f santaclaus@northpole\.int" =666 @@ -5182,14 +5182,14 @@ score "~f santaclaus@northpole\.int" =666 These three thresholds can be set via the variables - , - and - . + , + and + . By default, - and - + and + are set to -1, which means that in the default threshold configuration no @@ -5201,14 +5201,14 @@ score "~f santaclaus@northpole\.int" =666 color command - and the pattern: + and the pattern: - + color index black yellow "~n 10-" -color index red yellow "~n 100-" +color index red yellow "~n 100-" @@ -5230,14 +5230,14 @@ color index red yellow "~n 100-" Spam detection - pattern format + pattern format - pattern + pattern - Mutt-ng has generalized support for external spam-scoring filters. + Madmutt has generalized support for external spam-scoring filters. By defining your spam patterns with the spam and nospam @@ -5248,7 +5248,7 @@ color index red yellow "~n 100-" mail based on its spam attributes, as determined by the external filter. You also can display the spam attributes in your index display using the %H selector in the - + variable. (Tip: try %?H?[%H] ? to display spam tags only when they are defined for a given message.) @@ -5288,11 +5288,11 @@ color index red yellow "~n 100-" For example, suppose I use DCC, SpamAssassin, and PureMessage. I might define these spam settings: - + spam "X-DCC-.*-Metrics:.*(....)=many" "90+/DCC-%1" spam "X-Spam-Status: Yes" "90+/SA" spam "X-PerlMX-Spam: .*Probability=([0-9]+)%" "%1/PM" -set spam_separator=", " +set spam_separator=", " @@ -5318,7 +5318,7 @@ set spam_separator=", " $index_format variable. It's also the - string that the pattern-matching expression + string that the pattern-matching expression matches against for search and limit functions. And it's what sorting by spam @@ -5374,7 +5374,7 @@ set spam_separator=", " will be removed. This might be the default action if you use spam - and nospam in conjunction with a . + and nospam in conjunction with a . @@ -5387,8 +5387,8 @@ set spam_separator=", " - -spam "^From: .*MAILER-DAEMON" "999" + +spam "^From: .*MAILER-DAEMON" "999" @@ -5402,16 +5402,16 @@ spam "^From: .*MAILER-DAEMON" "999" Setting variables - [no|inv]variable [=value] [variable...] + [no|inv]variable [=value] [variable...] - variable [variable ...] + variable [variable ...] - variable [variable ...] + variable [variable ...] - variable [variable ...] + variable [variable ...] @@ -5493,8 +5493,8 @@ spam "^From: .*MAILER-DAEMON" "999" - -set ?allow_8bit + +set ?allow_8bit @@ -5528,7 +5528,7 @@ set ?allow_8bit Reading initialization commands from another file - filename [filename ...] + filename [filename ...] @@ -5564,7 +5564,7 @@ set ?allow_8bit Removing hooks - [* | hook-type] + [* | hook-type] @@ -5587,31 +5587,31 @@ set ?allow_8bit Character Sets - As users may run mutt-ng on different systems, the configuration + As users may run Madmutt on different systems, the configuration must be maintained because it's likely that people want to use the - setup everywhere they use mutt-ng. And mutt-ng tries to help where it + setup everywhere they use Madmutt. And Madmutt tries to help where it can. - To not produce conflicts with different character sets, mutt-ng + To not produce conflicts with different character sets, Madmutt allows users to specify in which character set their configuration files are encoded. Please note that while reading the configuration files, this is only respected after the corresponding declaration appears. It's advised to put the following at the very beginning of a - users muttngrc: + users madmuttrc: - -set config_charset = "..." + +set config_charset = "..." and replacing the dots with the actual character set. To avoid - problems while maintaining the setup, user's may want to use + problems while maintaining the setup, user's may want to use modelines as show in: @@ -5624,7 +5624,7 @@ set config_charset = "..." while, again, replacing the dots with the appropriate name. This - tells as which character set to read and save the file. + tells as which character set to read and save the file. @@ -5659,20 +5659,20 @@ set config_charset = "..." When using a configuration on different systems, the user may not - always have influence on how mutt-ng is installed and which features + always have influence on how Madmutt is installed and which features it includes. - To solve this, mutt-ng contain a feature based on the ``ifdef'' + To solve this, Madmutt contain a feature based on the ``ifdef'' patch written for mutt. Its basic syntax is: - + ifdef <item> <command> -ifndef <item> <command> +ifndef <item> <command> @@ -5728,45 +5728,45 @@ ifndef <item> <command> As an example, one can use the following in - ~/.muttngrc: + ~/.madmuttrc: - -ifdef feature_imap 'source ~/.mutt-ng/setup-imap' -ifdef feature_pop 'source ~/.mutt-ng/setup-pop' -ifdef feature_nntp 'source ~/.mutt-ng/setup-nntp' + +ifdef feature_imap 'source ~/.Madmutt/setup-imap' +ifdef feature_pop 'source ~/.Madmutt/setup-pop' +ifdef feature_nntp 'source ~/.Madmutt/setup-nntp' - ...to only source ~/.mutt-ng/setup-imap if + ...to only source ~/.Madmutt/setup-imap if IMAP - support is built in, only source ~/.mutt-ng/setup-pop + support is built in, only source ~/.Madmutt/setup-pop if POP support is built in and only source - ~/.mutt-ng/setup-nntp if NNTP support is + ~/.Madmutt/setup-nntp if NNTP support is built in. An example for testing for variable names can be used if users - use different revisions of mutt-ng whereby the older one may not + use different revisions of Madmutt whereby the older one may not have a certain variable. To test for the availability of - + use: - -ifdef imap_mail_check 'set imap_mail_check = 300' + +ifdef imap_mail_check 'set imap_mail_check = 300' Provided for completeness is the test for menu names. To set - only if the pager menu is available, use: @@ -5774,8 +5774,8 @@ ifdef imap_mail_check 'set imap_mail_check = 300' - -ifdef pager 'set pager_index_lines = 10' + +ifdef pager 'set pager_index_lines = 10' @@ -5789,9 +5789,9 @@ ifdef pager 'set pager_index_lines = 10' - -ifdef feature_ncurses 'source ~/.mutt-ng/setup-ncurses' -ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang' + +ifdef feature_ncurses 'source ~/.Madmutt/setup-ncurses' +ifndef feature_ncurses 'source ~/.Madmutt/setup-slang' @@ -5801,9 +5801,9 @@ ifndef feature_ncurses 'source ~/.mutt-ng/setup-slang' - -ifdef feature_slang 'source ~/.mutt-ng/setup-slang' -ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' + +ifdef feature_slang 'source ~/.Madmutt/setup-slang' +ifndef feature_slang 'source ~/.Madmutt/setup-ncurses' @@ -5849,7 +5849,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' Regular Expressions - All string patterns in Mutt-ng including those in more complex + All string patterns in Madmutt including those in more complex patterns must be specified using regular expressions (regexp) in the ``POSIX extended'' syntax (which @@ -6177,7 +6177,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - Note: If you compile Mutt-ng with the + Note: If you compile Madmutt with the GNU rx package, the following operators may also be used in regular expressions: @@ -6269,7 +6269,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' Patterns - Mutt-ng's pattern language provides a simple yet effective way to + Madmutt'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 consists of one or more sub-pattern, which can be logically grouped, ORed, and negated. For a complete listing of @@ -6296,7 +6296,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - 'SPAM' + 'SPAM' @@ -6314,16 +6314,16 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - ("nion@muttng\.org"|"ak@muttng\.org"|"pdmef@muttng\.org") -( mutt-ng| Mutt-ng) -! '@synflood\.at' + ("nion@madmutt\.org"|"ak@madmutt\.org"|"pdmef@madmutt\.org") +( Madmutt| Madmutt) +! '@synflood\.at' The first pattern matches all messages that were sent by one of - the mutt-ng maintainers, while the seconds pattern matches all - messages that contain ``mutt-ng'' in the message body or ``Mutt-ng'' + the Madmutt maintainers, while the seconds pattern matches all + messages that contain ``Madmutt'' in the message body or ``Madmutt'' in the subject. The third pattern matches all messages that do not contain ``@synflood\.at'' in the References: header, i.e. @@ -6365,9 +6365,9 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - 01/01/2005+1y - 18/10/2004-2w - 28/12/2004*1d + 01/01/2005+1y + 18/10/2004-2w + 28/12/2004*1d @@ -6388,9 +6388,9 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - >2w # messages older than two weeks - <3d # messages newer than 3 days - =1m # messages that are exactly one month old + >2w # messages older than two weeks + <3d # messages newer than 3 days + =1m # messages that are exactly one month old @@ -6411,7 +6411,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' The so called Format Strings offer great flexibility when - configuring mutt-ng. In short, they describe what items to print + configuring Madmutt. In short, they describe what items to print out how in menus and status messages. @@ -6422,7 +6422,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - For example, when running mutt-ng on different machines or + For example, when running Madmutt on different machines or different versions for testing purposes, it may be interesting to have the following information always printed on screen when one is in the index: @@ -6441,7 +6441,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - the current mutt-ng version number + the current Madmutt version number @@ -6452,7 +6452,7 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' The setting for the status bar of the index is controlled via the - + variable. For the hostname and version string, there's an expando for $status_format: %h @@ -6464,24 +6464,24 @@ ifndef feature_slang 'source ~/.mutt-ng/setup-ncurses' - -set status_format = "%v on %h: ..." + +set status_format = "%v on %h: ..." - mutt-ng will replace the sequence %v with + Madmutt will replace the sequence %v with the version string and %h with the host's name. When you are, for example, running - mutt-ng version 1.5.9i on host mailhost, you'll see the + Madmutt version 1.5.9i on host mailhost, you'll see the following when you're in the index: -Mutt-ng 1.5.9i on mailhost: ... +Madmutt 1.5.9i on mailhost: ... @@ -6525,8 +6525,8 @@ Mutt-ng 1.5.9i on mailhost: ... - -set status_format = "%v on %h: %B: ... + +set status_format = "%v on %h: %B: ... @@ -6539,7 +6539,7 @@ set status_format = "%v on %h: %B: ... -Mutt-ng 1.5.9i on mailhost: Inbox: ... +Madmutt 1.5.9i on mailhost: Inbox: ... @@ -6570,8 +6570,8 @@ Mutt-ng 1.5.9i on mailhost: Inbox: ... - -set status_format = "%v on %h: %B %?n?%n new? ... + +set status_format = "%v on %h: %B %?n?%n new? ... @@ -6591,7 +6591,7 @@ set status_format = "%v on %h: %B %?n?%n new? ... - which tells mutt-ng to only look at <string if + which tells Madmutt to only look at <string if nonzero> if the value of the %<item%gt; @@ -6603,7 +6603,7 @@ set status_format = "%v on %h: %B %?n?%n new? ... But this is not all: this feature only offers one alternative: - ``print something if not zero.'' Mutt-ng does, as you might guess, + ``print something if not zero.'' Madmutt does, as you might guess, also provide a logically complete version: ``if zero, print something and else print something else.'' This is achieved by the following syntax for those expandos which may be printed nonzero: @@ -6617,7 +6617,7 @@ set status_format = "%v on %h: %B %?n?%n new? ... - Using this we can make mutt-ng to do the following: + Using this we can make Madmutt to do the following: @@ -6652,8 +6652,8 @@ set status_format = "%v on %h: %B %?n?%n new? ... - -set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ... + +set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ... @@ -6664,8 +6664,8 @@ set status_format = "%v on %h: %B: %?n?%n new messages&no new messages? ...< - -set status_format = "%v on %h: %B: %?n?%n&no? new messages ... + +set status_format = "%v on %h: %B: %?n?%n&no? new messages ... @@ -6697,7 +6697,7 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... When specifying %_<item> instead of - just %<item>, mutt-ng will + just %<item>, Madmutt will convert all characters in the expansion of <item> to @@ -6710,7 +6710,7 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... When specifying %:<item> instead of just - %<item>, mutt-ng will convert + %<item>, Madmutt will convert all dots in the expansion of <item> to underscores (_). @@ -6740,7 +6740,7 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... - When this occurs, mutt-ng will fill the + When this occurs, Madmutt will fill the rest of the line with the character X. In our example, filling the rest of the line with dashes is done by setting: @@ -6748,8 +6748,8 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages ... - -set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-" + +set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-" @@ -6774,8 +6774,8 @@ set status_format = "%v on %h: %B: %?n?%n&no? new messages %|-" - -set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" + +set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" @@ -6806,7 +6806,7 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)"patterns for Mutt-ng's + default. See patterns for Madmutt's pattern matching syntax. @@ -6819,16 +6819,16 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" operation will be applied to all tagged messages if that operation can be used in that - manner. If the + manner. If the variable is set, the next operation applies to the tagged messages automatically, without requiring the ``tag-prefix''. - In or commands, + 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-ng will stop "eating" the macro when it encounters the + execution.Madmutt will stop "eating" the macro when it encounters the ``end-cond'' operator; after this operator the rest of the macro will be executed asnormal. @@ -6850,7 +6850,7 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" + reading, or to whom you are sending mail. In the Madmutt world, a hook consists of a regexp or @@ -6861,43 +6861,43 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" - + - + - + - + - + - + - + @@ -6913,16 +6913,16 @@ set status_format = "%B: %?n?%n&no? new messages %> (%v on %h)" and + restore configuration defaults. Here is an example with and the my_hdr directive: - + send-hook . 'unmy_hdr From:' -send-hook '~C ^b@b\.b$' my-hdr from: c@c.c +send-hook '~C ^b@b\.b$' my-hdr from: c@c.c @@ -6930,8 +6930,8 @@ send-hook '~C ^b@b\.b$' my-hdr from: c@c.c Message Matching in Hooks - Hooks that act upon messages (, , - , + Hooks that act upon messages (, , + , )are evaluated in a slightly different manner. For the other types of hooks, a regexp is @@ -6941,7 +6941,7 @@ send-hook '~C ^b@b\.b$' my-hdr from: c@c.c - Mutt-ng allows the use of the patterns + Madmutt allows the use of the patterns language for matching messages in hook commands. This works in exactly the same way as it would when limiting orsearching the mailbox, except that you are @@ -6955,8 +6955,8 @@ send-hook '~C ^b@b\.b$' my-hdr from: c@c.c sending mail to a specific address, you could do something like: - -send-hook '~t ^me@cs\.hmc\.edu$' 'my-hdr From: Mutt-ng User <user@host>' + +send-hook '~t ^me@cs\.hmc\.edu$' 'my-hdr From: Madmutt User <user@host>' which would execute the given command when sending mail to me@cs.hmc.edu. @@ -6969,13 +6969,13 @@ send-hook '~t ^me@cs\.hmc\.edu$' 'my-hdr From: Mutt-ng User <user@host>' - like the other hooks, in which case Mutt-ng will translate your + like the other hooks, in which case Madmutt will translate your pattern into the full language, using the translation specified by the - variable. The + variable. The pattern is translated at the time the hook is declared, so the value of - that is in effect + that is in effect at that time will be used. @@ -6991,7 +6991,7 @@ send-hook '~t ^me@cs\.hmc\.edu$' 'my-hdr From: Mutt-ng User <user@host>'Using the sidebar - The sidebar, a feature specific to Mutt-ng, allows you to use a mailbox + The sidebar, a feature specific to Madmutt, allows you to use a mailbox listing which looks very similar to the ones you probably know from GUI mail clients. @@ -6999,37 +6999,37 @@ send-hook '~t ^me@cs\.hmc\.edu$' 'my-hdr From: Mutt-ng User <user@host>' + set sidebar_visible="yes" -set sidebar_width=25 +set sidebar_width=25 If you want to specify the mailboxes you can do so with: - + set mbox='=INBOX' mailboxes INBOX \ MBOX1 \ MBOX2 \ -... +... You can also specify the colors for mailboxes with new mails by using: - + color sidebar_new red black -color sidebar white black +color sidebar white black Reasonable key bindings look e.g. like this: - + bind index \Cp sidebar-prev bind index \Cn sidebar-next bind index \Cb sidebar-open @@ -7038,7 +7038,7 @@ bind pager \Cn sidebar-next bind pager \Cb sidebar-open macro index B ':toggle sidebar_visible^M' -macro pager B ':toggle sidebar_visible^M' +macro pager B ':toggle sidebar_visible^M' @@ -7057,19 +7057,19 @@ macro pager B ':toggle sidebar_visible^M' External Address Queries - Mutt-ng supports connecting to external directory databases such as + Madmutt 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 command to use. For example: - -set query_command = "mutt_ldap_query.pl '%s'" + +set query_command = "mutt_ldap_query.pl '%s'" @@ -7129,11 +7129,11 @@ roessler@guug.de Thomas Roessler mutt pgp Mailbox Formats - Mutt-ng supports reading and writing of four different mailbox formats: + Madmutt 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 - newmailboxes, Mutt-ng uses the default specified with the - + newmailboxes, Madmutt uses the default specified with the + variable. @@ -7146,8 +7146,8 @@ roessler@guug.de Thomas Roessler mutt pgp - -From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST + +From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST @@ -7172,7 +7172,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST and MMDF, a mailbox consists of a directory and each message is stored in a separate file. The filename indicates the message number (however, this is may not - correspond to the message number Mutt-ng displays). Deleted messages + correspond to the message number Madmutt displays). Deleted messages arerenamed with a comma (,) prepended to the filename. Note: @@ -7223,20 +7223,20 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - ! -- refers to your + ! -- refers to your (incoming) mailbox - > -- refers to your file + > -- refers to your file - < -- refers to your file + < -- refers to your file @@ -7260,14 +7260,14 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - = or + -- refers to your + = or + -- refers to your directory - @alias -- refers to the + @alias -- refers to the as determined by the address of the alias @@ -7286,23 +7286,23 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST Handling Mailing Lists - Mutt-ng has a few configuration options that make dealing with large + Madmutt 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 often used for), and what lists you are subscribed to. This is - accomplished through the use of the + accomplished through the use of the commands in your muttrc. - Now that Mutt-ng knows what your mailing lists are, it can do several + Now that Madmutt 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 index menu display. This is useful to distinguish between personal and list mail in the same mailbox. In the - + variable, the escape ``%L'' will return the string ``To <list>'' when ``list'' appears in the ``To'' field, and ``Cc <list>'' when it appears in the ``Cc'' @@ -7322,10 +7322,10 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - Mutt-ng also supports the Mail-Followup-To header. + Madmutt 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 + subscribed mailing lists, and if the 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 @@ -7339,7 +7339,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST Conversely, when group-replying or list-replying to a message which has a Mail-Followup-To header, mutt will respect this header if - the + the 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 @@ -7348,7 +7348,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST Note that, when header editing is enabled, you can create a - Mail-Followup-To header manually. Mutt-ng will only + Mail-Followup-To header manually. Madmutt will only auto-generate this header if it doesn't exist when you send the message. @@ -7359,7 +7359,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST than the author of the message. This can create problems when trying to reply directly to the author in private, since most mail clients will automatically reply to the address given in the ``Reply-To'' - field. Mutt-ng uses the + field. Madmutt uses the variable to help decide which address to use. If set to ask-yes @@ -7375,18 +7375,18 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST The ``X-Label:'' header field can be used to further identify mailing lists or list subject matter (or just to annotate messages - individually). The + individually). The 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 ``'' selector. ``X-Label:'' is + index, and Madmutt's pattern-matcher can match regular expressions to + ``X-Label:'' fields with the ``'' selector. ``X-Label:'' is not a standard message header field, but it can easily be inserted by procmailand other mail filtering agents. - Lastly, Mutt-ng has the ability to sort the + Lastly, Madmutt has the ability to sort the mailbox into threads. A thread is a group of messages which all relate to the same @@ -7409,7 +7409,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST Editing threads - Mutt-ng has the ability to dynamically restructure threads that are + Madmutt 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 @@ -7423,7 +7423,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST 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-ng has not enough information to guess the + discussions because Madmutt has not enough information to guess the correct threading. You can fix this by tagging the reply, then moving to the parent @@ -7467,7 +7467,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST Delivery Status Notification (DSN) Support - defines a set of MIME content types for relaying information + defines a set of MIME content types for relaying information about the status of electronic mail messages. These can be thought of as ``return receipts.'' @@ -7510,7 +7510,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - is used + is used to request receipts for different results (such as failed message,message delivered, etc.). @@ -7519,7 +7519,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST - requests + requests how much of your message should be returned with the receipt (headers or full message). @@ -7544,7 +7544,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST POP3 Support (OPTIONAL) - If Mutt-ng was compiled with POP3 support (by running the + If Madmutt was compiled with POP3 support (by running the configure script with the --enable-pop flag), it has the @@ -7571,15 +7571,15 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST 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 + reason the frequency at which Madmutt will check for mail remotely can be controlled by the - + variable, which defaults to every 60 seconds. - If Mutt-ng was compiled with SSL support (by running the + If Madmutt was compiled with SSL support (by running the configure script with the --with-ssl flag), connections to @@ -7595,15 +7595,15 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST (default: G). It allows to connect to pop-host ,fetch all your new mail and place it in the - local . After this - point, Mutt-ng runs exactly as if the mail had always been local. + local . After this + point, Madmutt runs exactly as if the mail had always been local. Note: If you only need to fetch all messages to local mailbox you should consider using a specialized program, such as - . + . @@ -7616,7 +7616,7 @@ From me@cs.hmc.edu Fri, 11 Apr 1997 11:44:56 PST IMAP Support (OPTIONAL) - If Mutt-ng was compiled with IMAP support (by running the + If Madmutt was compiled with IMAP support (by running the configure script with the --enable-imap flag), it has the ability to work with folders located on a remote IMAP server. @@ -7661,7 +7661,7 @@ imap://imapserver:port/INBOX - If Mutt-ng was compiled with SSL support (by running the + If Madmutt was compiled with SSL support (by running the configure script with the --with-ssl flag), connections to @@ -7673,7 +7673,7 @@ imap://imapserver:port/INBOX - Note that not all servers use / as the hierarchy separator. Mutt-ng + Note that not all servers use / as the hierarchy separator. Madmutt should correctly notice which separator is being used by the server and convertpaths accordingly. @@ -7683,7 +7683,7 @@ imap://imapserver:port/INBOX 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 toggle-subscribed command. See also the - + variable. @@ -7691,9 +7691,9 @@ imap://imapserver:port/INBOX Polling for new mail on an IMAP server can cause noticeable delays. So, you'll want to carefully tune the - + and - + variables. @@ -7761,7 +7761,7 @@ imap://imapserver:port/INBOX Authentication - Mutt-ng supports four authentication methods with IMAP servers: SASL, + Madmutt 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 @@ -7789,7 +7789,7 @@ imap://imapserver:port/INBOX - Mutt-ng will try whichever methods are compiled in and available on + Madmutt will try whichever methods are compiled in and available on the server, in the following order: SASL, ANONYMOUS, GSSAPI, CRAM-MD5, LOGIN. @@ -7801,7 +7801,7 @@ imap://imapserver:port/INBOX - - controls + - controls the username under which you request authentication on the IMAP server, for all authenticators. This is overridden by an explicit @@ -7813,7 +7813,7 @@ imap://imapserver:port/INBOX - - a + - a password which you may preset, used by all authentication methods where a password is needed. @@ -7822,7 +7822,7 @@ imap://imapserver:port/INBOX - + - a colon-delimited list of IMAP authentication methods to try, in the order you wish to try them. If @@ -7848,18 +7848,18 @@ imap://imapserver:port/INBOX NNTP Support (OPTIONAL) - If compiled with ``--enable-nntp'' option, Mutt-ng can read news from + If compiled with ``--enable-nntp'' option, Madmutt can read news from a newsserver via NNTP. You can open a newsgroup with the ``change-newsgroup'' function from the index/pager which is by default - bound to i. + bound to i. - The Default newsserver can be obtained from the + The Default newsserver can be obtained from the environment variable. Like other news readers, info about subscribed newsgroups is saved in a file as specified by the - variable. + 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 @@ -7871,13 +7871,13 @@ imap://imapserver:port/INBOX Especially for Usenet, people often ask for advanced filtering - and scoring functionality. Of course, mutt-ng has scoring and + and scoring functionality. Of course, Madmutt has scoring and allows a killfile, too. How to use a killfile has been discussed in Message Scoring. - What has not been discusses in detail is mutt-ng's built-in + What has not been discusses in detail is Madmutt's built-in realname filter. For may newsreaders including those for ``advanced users'' like slrn or tin, there are frequent request for such functionality. The solutions offered often are @@ -7885,25 +7885,25 @@ imap://imapserver:port/INBOX - In mutt-ng this is as easy as + In Madmutt this is as easy as - -score ~* =42 + +score ~* =42 - This tells mutt-ng to apply a score of 42 to all messages whose + This tells Madmutt to apply a score of 42 to all messages whose sender specified a valid realname and a valid email address. Using - -score !~* =42 + +score !~* =42 @@ -7918,7 +7918,7 @@ score !~* =42 - Email addresses must be valid according to + Email addresses must be valid according to @@ -7962,33 +7962,33 @@ score !~* =42 SMTP Support (OPTIONAL) - Mutt-ng can be built using a library called ``libESMTP'' which + Madmutt can be built using a library called ``libESMTP'' which provides SMTP functionality. When configure was called with - --with-libesmtp or the output muttng -v contains + --with-libesmtp or the output madmutt -v contains +USE_LIBESMTP, this will be or is the case already. The SMTP support includes support for Delivery Status Notification (see dsn section) as well as handling the 8BITMIME flag controlled via - . + . To enable sending mail directly via SMTP without an MTA such as - Postfix or SSMTP and the like, simply set the + Postfix or SSMTP and the like, simply set the variable pointing to your SMTP server. - Authentication mechanisms are available via the - and variables. + Authentication mechanisms are available via the + and 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 variable + this to work, first of all Madmutt must be built with SSL or GNUTLS. + Secondly, the 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 @@ -8001,7 +8001,7 @@ score !~* =42 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 - may be used + may be used to set the envelope different from the From: header. @@ -8013,8 +8013,8 @@ score !~* =42 If you happen to have accounts on multiple IMAP and/or POP servers, you may find managing all the authentication settings inconvenient and - error-prone. The command may help. This hook works like - but is invoked whenever you access a remote mailbox + error-prone. The command may help. This hook works like + but is invoked whenever you access a remote mailbox (including inside the folder browser), not just when you open the mailbox. @@ -8025,10 +8025,10 @@ score !~* =42 - + account-hook . 'unset imap_user; unset imap_pass; unset tunnel' account-hook imap://host1/ 'set imap_user=me1 imap_pass=foo' -account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"' +account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"' @@ -8047,12 +8047,12 @@ account-hook imap://host2/ 'set tunnel="ssh host2 /usr/libexec/imapd"' + retrieved at and the configuration commands: - + macro index \cb |urlview\n -macro pager \cb |urlview\n +macro pager \cb |urlview\n @@ -8066,7 +8066,7 @@ macro pager \cb |urlview\n Compressed folders Support (OPTIONAL) - If Mutt-ng was compiled with compressed folders support (by running the + If Madmutt was compiled with compressed folders support (by running the configure script with the --enable-compressed @@ -8089,8 +8089,8 @@ macro pager \cb |urlview\n - There are three hooks defined (, - and + There are three hooks defined (, + and )which define commands to uncompress and compress a folder and to append messages to an existing compressed folder respectively. @@ -8102,32 +8102,32 @@ macro pager \cb |urlview\n - + open-hook \\.gz$ "gzip -cd %f > %t" close-hook \\.gz$ "gzip -c %t > %f" -append-hook \\.gz$ "gzip -c %t >> %f" +append-hook \\.gz$ "gzip -c %t >> %f" - You do not have to specify all of the commands. If you omit + You do not have to specify all of the commands. If you omit ,the folder will be open and - closed again each time you will add to it. If you omit + closed again each time you will add to it. If you omit (or give empty command) , the - folder will be open in the mode. If you specify + folder will be open in the mode. If you specify 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 + Note that Madmutt 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 surprising if your compressing script produces empty files. In this situation, unset - + ,so that the compressed file will be removed if you delete all of the messages. @@ -8136,7 +8136,7 @@ append-hook \\.gz$ "gzip -c %t >> %f" Open a compressed mailbox for reading - Usage: regexp "command" + Usage: regexp "command" @@ -8173,8 +8173,8 @@ append-hook \\.gz$ "gzip -c %t >> %f" - -open-hook \\.gz$ "gzip -cd %f > %t" + +open-hook \\.gz$ "gzip -cd %f > %t" @@ -8190,11 +8190,11 @@ open-hook \\.gz$ "gzip -cd %f > %t" Write a compressed mailbox - Usage: regexp"command" + Usage: regexp"command" - This is used to close the folder that was open with the + This is used to close the folder that was open with the command after some changes were made to it. @@ -8203,9 +8203,9 @@ open-hook \\.gz$ "gzip -cd %f > %t" used for closing the folders whose names match regexp. It has the same format as in - the command. Temporary + the command. Temporary folder - in this case is the folder previously produced by the + in this case is the folder previously produced by the command. @@ -8222,8 +8222,8 @@ open-hook \\.gz$ "gzip -cd %f > %t" - -close-hook \\.gz$ "gzip -c %t > %f" + +close-hook \\.gz$ "gzip -c %t > %f" @@ -8234,7 +8234,7 @@ close-hook \\.gz$ "gzip -c %t > %f" - is not called when you + is not called when you exit from the folder if the folder was not changed. @@ -8245,7 +8245,7 @@ close-hook \\.gz$ "gzip -c %t > %f" Append a message to a compressed mailbox - Usage: regexp"command" + Usage: regexp"command" @@ -8254,7 +8254,7 @@ close-hook \\.gz$ "gzip -c %t > %f" appending to the folders whose names match regexp. It has the same format as in - the command. + the command. The temporary folder in this case contains the messages that are beingappended. @@ -8272,23 +8272,23 @@ close-hook \\.gz$ "gzip -c %t > %f" - -append-hook \\.gz$ "gzip -c %t >> %f" + +append-hook \\.gz$ "gzip -c %t >> %f" - When is used, the + When 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 ( + what the folder type is. Thus the default ( )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, - is called, and not . + If the file does not exist when you save to it, + is called, and not . is only for appending to existing folders. @@ -8297,7 +8297,7 @@ append-hook \\.gz$ "gzip -c %t >> %f" If the command is empty, this operation is disabled for this file type. In this case, the folder will be open and closed again (using - and + and respectively) each time you will add to it. @@ -8314,15 +8314,15 @@ append-hook \\.gz$ "gzip -c %t >> %f" - + open-hook \\.pgp$ "pgp -f < %f > %t" -close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" +close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" Please note, that PGP does not support appending to an encrypted - folder, so there is no defined. + folder, so there is no defined. @@ -8348,14 +8348,14 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" - Mutt-ng's MIME Support + Madmutt's MIME Support - Quite a bit of effort has been made to make Mutt-ng the premier text-mode + Quite a bit of effort has been made to make Madmutt 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-ng for MIME, there are two - extratypes of configuration files which Mutt-ng uses. One is the + wherever possible. When configuring Madmutt for MIME, there are two + extratypes of configuration files which Madmutt uses. One is the mime.types file, which contains the mapping of file extensions to IANA MIME types. The other is the mailcap file, which @@ -8367,7 +8367,7 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f"Using MIME in Mutt - There are three areas/menus in Mutt-ng which deal with MIME, they are + There are three areas/menus in Madmutt which deal with MIME, they are the pager (while viewing a message), the attachment menu and the compose menu. @@ -8379,18 +8379,18 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" 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 + decodes the message to a text representation. Madmutt 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-ng recognizes a variety of PGP MIME types, + controlled version of Madmutt recognizes a variety of PGP MIME types, including PGP/MIME and application/pgp. - Mutt-ng will denote attachments with a couple lines describing them. + Madmutt will denote attachments with a couple lines describing them. These lines are of the form: @@ -8404,7 +8404,7 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" - If Mutt-ng cannot deal with a MIME type, it will display a message + If Madmutt cannot deal with a MIME type, it will display a message like: @@ -8436,7 +8436,7 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" Finally, you can apply the usual message-related functions (like - , and the reply + , and the reply and forward functions) to attachments of type message/rfc822. @@ -8470,7 +8470,7 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" - The '-' denotes that Mutt-ng will delete the file after sending (or + The '-' denotes that Madmutt 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 @@ -8503,8 +8503,8 @@ close-hook \\.pgp$ "pgp -fe YourPgpUserIdOrKeyId < %t > %f" - When you add an attachment to your mail message, Mutt-ng searches your - personal mime.types file within and then + When you add an attachment to your mail message, Madmutt searches your + personal mime.types file within and then the system mime.types file at /usr/local/share/mutt/mime.types or /etc/mime.types @@ -8518,22 +8518,22 @@ application/postscript ps eps application/pgp pgp audio/x-aiff aif aifc aiff - A sample mime.types file comes with the Mutt-ng + A sample mime.types file comes with the Madmutt distribution, and should contain most of the MIME types you are likely to use. - If Mutt-ng can not determine the mime type by the extension of the file + If Madmutt can not determine the mime type by the extension of the file you attach, it will look at the file. If the file is free of binary - information, Mutt-ng will assume that the file is plain text, and mark + information, Madmutt will assume that the file is plain text, and mark it as text/plain. If the file contains binary - information, then Mutt-ng will + information, then Madmutt will mark it as application/octet-stream. You can change the MIME - type that Mutt-ng assigns to an attachment by using the + type that Madmutt assigns to an attachment by using the edit-type command from the compose menu (default: ^T). The MIME type is @@ -8541,7 +8541,7 @@ audio/x-aiff aif aifc aiff major mime type followed by the sub-type, separated by a '/'. 6 major types: application, text, image, video, audio, and model have been approved - after various internet discussions. Mutt-ng recognises all of these if + after various internet discussions. Madmutt recognises all of these if the appropriate entry is found in the mime.types file. It also recognises other @@ -8566,7 +8566,7 @@ audio/x-aiff aif aifc aiff - Mutt-ng supports MIME Configuration, in particular the Unix + Madmutt supports MIME Configuration, in particular the Unix specific format specified in Appendix A of the RfC. This file format is commonly referred to as the mailcap format. Many MIME compliant programs utilize the mailcap format, allowing you to specify handling @@ -8575,15 +8575,15 @@ audio/x-aiff aif aifc aiff - In order to handle various MIME types that Mutt-ng can not handle - internally, Mutt-ng parses a series of external configuration files to + In order to handle various MIME types that Madmutt can not handle + internally, Madmutt parses a series of external configuration files to find an external handler. The default search string for these files is a colon delimited list set to ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/etc/mailcap:/usr/local/etc/mailcap - where is your home directory. + where is your home directory. @@ -8639,10 +8639,10 @@ ${HOME}/.mailcap:/usr/local/share/mutt/mailcap:/etc/mailcap:/etc/mailcap:/usr/et 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-ng to save the body of the MIME message to a + This will cause Madmutt to save the body of the MIME message to a temporary file, and then call the view command with the %s replaced by - the name of the temporary file. In both cases, Mutt-ng will turn over + the name of the temporary file. In both cases, Madmutt will turn over the terminal to the view program until the program quits, at which time Mutt @@ -8709,11 +8709,11 @@ text/*; more The interpretation of shell meta-characters embedded in MIME parameters - can lead to security problems in general. Mutt-ng tries to quote + can lead to security problems in general. Madmutt tries to quote parameters in expansion of %s syntaxes properly, and avoids risky characters by - substituting them, see the + substituting them, see the variable. @@ -8726,7 +8726,7 @@ text/*; more Keep the %-expandos away from shell quoting. - Don't quote them with single or double quotes. Mutt-ng does this for + Don't quote them with single or double quotes. Madmutt does this for you, the right way, as should any other program which interprets mailcap. Don't put them into backtick expansions. Be highly careful with eval statements, and avoid them if possible at all. Trying to @@ -8766,20 +8766,20 @@ text/test-mailcap-bug; cat %s; copiousoutput; test=charset=%{charset} \ you can add semi-colon ';' separated fields to set flags and other options. - Mutt-ng recognizes the following optional fields: + Madmutt recognizes the following optional fields: copiousoutput - This flag tells Mutt-ng that the command passes possibly + This flag tells Madmutt that the command passes possibly large amounts of - text on stdout. This causes Mutt-ng to invoke a pager + text on stdout. This causes Madmutt to invoke a pager (either the internal pager or the external pager defined by the pager variable) on the output - of the view command. Without this flag, Mutt-ng assumes + of the view command. Without this flag, Madmutt assumes that the command is interactive. One could use this to replace the pipe to more @@ -8792,7 +8792,7 @@ text/html; lynx -dump %s ; copiousoutput This will cause lynx to format the text/html output as text/plain - and Mutt-ng will use your standard pager to display the + and Madmutt will use your standard pager to display the results. @@ -8801,13 +8801,13 @@ text/html; lynx -dump %s ; copiousoutput needsterminal - Mutt-ng uses this flag when viewing attachments with , + Madmutt uses this flag when viewing attachments with , in order to decide whether it should honor the setting - of the variable or + of the variable or not. When an attachment is viewed using an interactive program, and the - corresponding mailcap entry has a needsterminal flag, Mutt-ng will use - and the exit + corresponding mailcap entry has a needsterminal flag, Madmutt will use + and the exit statusof the program to decide if it will ask you to press a key after the external program has exited. In all other situations it @@ -8822,7 +8822,7 @@ text/html; lynx -dump %s ; copiousoutput This flag specifies the command to use to create a new attachment of a - specific MIME type. Mutt-ng supports this from the compose + specific MIME type. Madmutt supports this from the compose menu. @@ -8839,7 +8839,7 @@ text/html; lynx -dump %s ; copiousoutput This can be used to specify parameters, filename, description, etc. for a new - attachment. Mutt-ng supports this from the compose menu. + attachment. Madmutt supports this from the compose menu. @@ -8849,7 +8849,7 @@ text/html; lynx -dump %s ; copiousoutput This flag specifies the command to use to print a specific MIME type. - Mutt-ng supports this from the attachment and compose + Madmutt supports this from the attachment and compose menus. @@ -8860,9 +8860,9 @@ text/html; lynx -dump %s ; copiousoutput This flag specifies the command to use to edit a specific MIME type. - Mutt-ng supports this from the compose menu, and also uses + Madmutt supports this from the compose menu, and also uses it to compose - new attachments. Mutt-ng will default to the defined + new attachments. Madmutt will default to the defined editor for text attachments. @@ -8899,12 +8899,12 @@ text/html; lynx %s; nametemplate=%s.html command expansion rules defined in the next section. If the command returns 0, then the - test passed, and Mutt-ng uses this entry. If the command + test passed, and Madmutt uses this entry. If the command returns non-zero, - then the test failed, and Mutt-ng continues searching for + then the test failed, and Madmutt continues searching for the right entry. Note: the - content-type must match before Mutt-ng performs the test. + content-type must match before Madmutt performs the test. For example: @@ -8912,14 +8912,14 @@ text/html; lynx %s; nametemplate=%s.html text/html; netscape -remote 'openURL(%s)' ; test=RunningX text/html; lynx %s - In this example, Mutt-ng will run the program RunningX + In this example, Madmutt 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-ng will call netscape to + RunningX returns 0, then Madmutt will call netscape to display the text/html object. If RunningX doesn't return 0, then - Mutt-ng will go on + Madmutt will go on to the next entry and use lynx to display the text/html object. @@ -8934,12 +8934,12 @@ text/html; lynx %s Search Order - When searching for an entry in the mailcap file, Mutt-ng will + When searching for an entry in the mailcap file, Madmutt 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-ng will search for an entry with + entries in your mailcap file, Madmutt will search for an entry with the print command: @@ -8948,14 +8948,14 @@ image/*; xv %s image/gif; ; print= anytopnm %s | pnmtops | lpr; \ nametemplate=%s.gif - Mutt-ng will skip the image/* entry and use the + Madmutt will skip the image/* entry and use the image/gif entry with the print command. - In addition, you can use this with + In addition, you can use this with to denote two commands for viewing an attachment, one to be viewed automatically, the other to be viewed interactively from the attachment @@ -8968,13 +8968,13 @@ 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-ng will choose + For , Madmutt 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-ng will use the + entry. If the program returns non-zero, Madmutt will use the second entry for interactive viewing. @@ -8990,9 +8990,9 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput Before the command is passed to /bin/sh -c, it is parsed to expand - various special parameters with information from Mutt-ng. The + various special parameters with information from Madmutt. The keywords - Mutt-ng expands are: + Madmutt expands are: @@ -9007,7 +9007,7 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput composing program should place the results of composition. In addition, the - use of this keyword causes Mutt-ng to not pass the body of + use of this keyword causes Madmutt to not pass the body of the message to the view/print/edit program on stdin. @@ -9017,7 +9017,7 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput %t - Mutt-ng will expand %t to the text representation of + Madmutt will expand %t to the text representation of the content type of the message in the same form as the first parameter of the @@ -9030,16 +9030,16 @@ text/html; lynx -dump %s; nametemplate=%s.html; copiousoutput %{<parameter>} - Mutt-ng will expand this to the value of the specified + Madmutt 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 + +Content-Type: text/plain; charset=iso-8859-1 - then Mutt-ng will expand %{charset} to + then Madmutt will expand %{charset} to iso-8859-1. The default metamail mailcap file uses this feature to test the charset to spawn an xterm @@ -9056,10 +9056,10 @@ Content-Type: text/plain; charset=iso-8859-1 - Mutt-ng does not currently support the %F and %n + Madmutt does not currently support the %F and %n keywords - specified in . The main purpose of these parameters is for - multipart messages, which is handled internally by Mutt-ng. + specified in . The main purpose of these parameters is for + multipart messages, which is handled internally by Madmutt. @@ -9137,16 +9137,16 @@ application/ms-excel; open.pl %s MIME Autoview - mime-type [mime-type ...] + mime-type [mime-type ...] - mime-type [mime-type ...] + mime-type [mime-type ...] - In addition to explicitly telling Mutt-ng to view an attachment with - theMIME viewer defined in the mailcap file, Mutt-ng has support for + In addition to explicitly telling Madmutt to view an attachment with + theMIME viewer defined in the mailcap file, Madmutt has support for automatically viewing MIME attachments while in the pager. @@ -9167,14 +9167,14 @@ application/ms-excel; open.pl %s For instance, if you set auto_view to: - + auto_view text/html application/x-gunzip application/postscript -image/gif application/x-tar-gz +image/gif application/x-tar-gz - Mutt-ng could use the following mailcap entries to automatically view + Madmutt could use the following mailcap entries to automatically view attachments of these types. @@ -9189,7 +9189,7 @@ application/postscript; ps2ascii %s; copiousoutput ``unauto_view'' can be used to remove previous entries from the autoview list. - This can be used with to autoview messages based on size, + This can be used with to autoview messages based on size, etc. ``unauto_view *'' will remove all previous entries. @@ -9204,15 +9204,15 @@ application/postscript; ps2ascii %s; copiousoutput MIME Multipart/Alternative - mime-type [mime-type ...] + mime-type [mime-type ...] - mime-type [mime-type ...] + mime-type [mime-type ...] - Mutt-ng has some heuristics for determining which attachment of a + Madmutt 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 typesis preferred. The alternative_order list consists of a @@ -9220,16 +9220,16 @@ application/postscript; ps2ascii %s; copiousoutput MIME types in order, including support for implicit and explicit wildcards, for example: - + alternative_order text/enriched text/plain text -application/postscript image/* +application/postscript image/* Next, mutt will check if any of the types have a defined - , and use that. Failing - that, Mutt-ng will look for any text type. As a last attempt, mutt + , and use that. Failing + that, Madmutt will look for any text type. As a last attempt, mutt willlook for any type it knows how to handle. @@ -9262,14 +9262,14 @@ The syntax is: - + ( {+|-}disposition mime-type | ? ) - + - + {+|-}disposition mime-type - + @@ -9367,7 +9367,7 @@ that it can be pasted elsewhere. Please note that counting attachments may require lots of data be loaded. This may cause noticeable slowdowns over network links depending on the connection speed and message sizes. To fine-tune the - behavior on a per-folder or other basis, the variable may be used. @@ -9377,15 +9377,15 @@ that it can be pasted elsewhere. MIME Lookup - mime-type [mime-type ...] + mime-type [mime-type ...] - mime-type [mime-type ...] + mime-type [mime-type ...] - Mutt-ng's mime_lookup list specifies a list of mime-types that + Madmutt's mime_lookup list specifies a list of mime-types that should not be treated according to their mailcap entry. This option is designed todeal with binary types such as application/octet-stream. When an @@ -9400,8 +9400,8 @@ that it can be pasted elsewhere. configuration options (such as auto_view) specified. Common usage would be: - -mime_lookup application/octet-stream application/X-Lotus-Manuscript + +mime_lookup application/octet-stream application/X-Lotus-Manuscript @@ -9430,24 +9430,24 @@ mime_lookup application/octet-stream application/X-Lotus-ManuscriptSecurity Considerations - First of all, mutt-ng contains no security holes included by + First of all, Madmutt contains no security holes included by intention but may contain unknown security holes. As a consequence, - please run mutt-ng only with as few permissions as possible. + please run Madmutt only with as few permissions as possible. - Please do not run mutt-ng as the super user. + Please do not run Madmutt as the super user. - When configuring mutt-ng, there're some points to note about secure + When configuring Madmutt, there're some points to note about secure setups. - In practice, mutt-ng can be easily made as vulnerable as even the + In practice, Madmutt can be easily made as vulnerable as even the most insecure mail user agents (in their default configuration) just - by changing mutt-ng's configuration files: it then can execute + by changing Madmutt's configuration files: it then can execute arbitrary programs and scripts attached to messages, send out private data on its own, etc. Although this is not believed to the common type of setup, please read this chapter carefully. @@ -9457,7 +9457,7 @@ mime_lookup application/octet-stream application/X-Lotus-ManuscriptPasswords - Although mutt-ng can be told the various passwords for accounts, + Although Madmutt can be told the various passwords for accounts, please never store passwords in configuration files. Besides the fact that the system's operator can always read them, you could forget to replace the actual password with asterisks when reporting @@ -9472,12 +9472,12 @@ mime_lookup application/octet-stream application/X-Lotus-ManuscriptTemporary Files - Mutt-ng uses many temporary files for viewing messages, verifying - digital signatures, etc. The + Madmutt uses many temporary files for viewing messages, verifying + digital signatures, etc. The variable can be used to change the default permissions of these files. Please only change it if you really know what you are doing. Also, a different location for these files may be desired which can - be changed via the variable. + be changed via the variable. @@ -9489,7 +9489,7 @@ mime_lookup application/octet-stream application/X-Lotus-ManuscriptMessage-ID: headers - In the default configuration, mutt-ng will leak some information + In the default configuration, Madmutt will leak some information to the outside world when sending messages: the generation of Message-ID: headers includes a step counter which is increased @@ -9497,7 +9497,7 @@ mime_lookup application/octet-stream application/X-Lotus-Manuscript%P expando from the - default setting of the variable. Please make sure that + default setting of the variable. Please make sure that you really know how local parts of these Message-ID: headers are composed. @@ -9508,13 +9508,13 @@ mime_lookup application/octet-stream application/X-Lotus-Manuscriptmailto:-style links - As mutt-ng be can be set up to be the mail client to handle + As Madmutt be can be set up to be the mail client to handle mailto: style links in websites, there're security - considerations, too. To keep the old behavior by default, mutt-ng + considerations, too. To keep the old behavior by default, Madmutt will be strict in interpreting them which means that arbitrary header fields can be embedded in these links which could override existing header fields or attach arbitrary files. This may be - problematic if the + problematic if the variable is unset, i.e. the user doesn't want to see header fields while editing the message. @@ -9537,8 +9537,8 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - When unsetting the - variable, mutt-ng will + When unsetting the + variable, Madmutt will @@ -9557,7 +9557,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - turn on the + turn on the variable by force to let the user see all the headers (because they still may leak information.) @@ -9577,7 +9577,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg External applications - Mutt-ng in many places has to rely on external applications or + Madmutt in many places has to rely on external applications or for convenience supports mechanisms involving external applications. @@ -9587,10 +9587,10 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg One of these is the mailcap mechanism as defined - by . Mutt-ng can be set up to automatically + by . Madmutt can be set up to automatically execute any given utility as listed in one of the mailcap files (see the - + variable for details.) @@ -9600,7 +9600,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg other exploitable bugs. These vulnerabilities may go unnoticed by the user, especially when they are called automatically (and without interactive prompting) from the mailcap file(s). When - using mutt-ng's autoview mechanism in combination with mailcap + using Madmutt's autoview mechanism in combination with mailcap files, please be sure to... @@ -9634,7 +9634,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - leave the variable in its default + leave the variable in its default state to restrict mailcap expandos to a safe set of characters @@ -9650,13 +9650,13 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg Other - Besides the mailcap mechanism, mutt-ng uses a number of other + Besides the mailcap mechanism, Madmutt uses a number of other external utilities for operation. The same security considerations apply for these as for tools - involved via mailcap (for example, mutt-ng is vulnerable to Denial + involved via mailcap (for example, Madmutt is vulnerable to Denial of Service Attacks with compressed folders support if the uncompressed mailbox is too large for the disk it is saved to.) @@ -9680,7 +9680,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg Command line options - Running mutt with no arguments will make Mutt-ng + Running mutt with no arguments will make Madmutt attempt to read your spool mailbox. However, it is possible to read other mailboxes and to send messages from the command line as well. @@ -9744,7 +9744,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg -n - do not read the system Muttngrc + do not read the system madmuttrc -p @@ -9825,7 +9825,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - Mutt-ng also supports a ``batch'' mode to send prepared messages. + Madmutt also supports a ``batch'' mode to send prepared messages. Simply redirect input from the file you wish to send. For example, @@ -9868,227 +9868,227 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - + all messages - + EXPR messages which contain EXPR in the message body - + EXPR messages which contain EXPR in the whole message - + EXPR messages carbon-copied to EXPR - + EXPR message is either to: or cc: EXPR - + deleted messages - + [MIN]-[MAX] messages with ``date-sent'' in a Date range - + expired messages - + EXPR message which contains EXPR in the ``Sender'' field - + flagged messages - + EXPR messages originating from EXPR - + cryptographically signed messages - + cryptographically encrypted messages - + EXPR messages with a spam attribute matching EXPR - + EXPR messages which contain EXPR in the message header - + message contains PGP key material - + EXPR message which match ID in the ``Message-ID'' field - + EXPR message is either originated or received by EXPR - + message is addressed to a known mailing list - + [MIN]-[MAX] message in the range MIN to MAX *) - + multipart messages - + [MIN]-[MAX] messages with a score in the range MIN to MAX *) - + new messages - + old messages - + message is addressed to you (consults alternates) - + message is from you (consults alternates) - + messages which have been replied to - + read messages - + [MIN]-[MAX] messages with ``date-received'' in a Date range - + superseded messages - + EXPR messages having EXPR in the ``Subject'' field. - + tagged messages - + EXPR messages addressed to EXPR - + unread messages - + message is addressed to a subscribed mailing list - + message is part of a collapsed thread. - + cryptographically verified messages - + EXPR messages which contain EXPR in the `Newsgroups' field (if compiled with NNTP support) - + EXPR messages which contain EXPR in the `References' field - + [MIN]-[MAX] messages with MIN to MAX attachments *) - + EXPR messages which contain EXPR in the `X-Label' field - + [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) @@ -10102,7 +10102,7 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg Where EXPR are regexp. Special attention has to be made when using regular expressions inside of patterns. Specifically, - Mutt-ng's parser for these patterns will strip one level of backslash + Madmutt'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 @@ -10131,326 +10131,326 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg - pattern command + pattern command - key address [, address, ... ] + key address [, address, ... ] - [ * | key ... ] + [ * | key ... ] - regexp [ regexp ... ] + regexp [ regexp ... ] - [ * | regexp ... ] + [ * | regexp ... ] - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - regexp command + regexp command - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - map key function + map key function - alias charset + alias charset - regexp command + regexp command - object foreground background [ regexp ] + object foreground background [ regexp ] - index pattern [ pattern ... ] + index pattern [ pattern ... ] - function [ function ... ] + function [ function ... ] - pattern mailbox + pattern mailbox - pattern mailbox + pattern mailbox - pattern command + pattern command - header [ header ... ] + header [ header ... ] - header [ header ... ] + header [ header ... ] - charset local-charset + charset local-charset - pattern [ pattern ... ] + pattern [ pattern ... ] - pattern [ pattern ... ] + pattern [ pattern ... ] - regexp [ regexp ... ] + regexp [ regexp ... ] - regexp [ regexp ... ] + regexp [ regexp ... ] - menu key sequence [ description ] + menu key sequence [ description ] - filename [ filename ... ] + filename [ filename ... ] - pattern mailbox + pattern mailbox - pattern command + pattern command - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - mimetype [ mimetype ... ] + mimetype [ mimetype ... ] - object attribute [ regexp ] + object attribute [ regexp ] - index pattern [ pattern ... ] + index pattern [ pattern ... ] - string + string - field [ field ... ] + field [ field ... ] - regexp command + regexp command - pattern key-id + pattern key-id - string + string - variable [ variable ... ] + variable [ variable ... ] - regexp filename + regexp filename - pattern value + pattern value - pattern [ pattern ... ] + pattern [ pattern ... ] - regexp command + regexp command - regexp command + regexp command - [no|inv]variable[ =value ] [ variable ... ] + [no|inv]variable[ =value ] [ variable ... ] - variable [ variable ... ] + variable [ variable ... ] - filename + filename - pattern format + pattern format - pattern + pattern - regexp [ regexp ... ] + regexp [ regexp ... ] - regexp [ regexp ... ] + regexp [ regexp ... ] - variable [ variable ... ] + variable [ variable ... ] - hook-type + hook-type @@ -10485,171 +10485,171 @@ mailto:joe@host?Attach=~/.gnupg/secring.gpg edit_hdrs - + forw_decode - + forw_format - + forw_quote - + hdr_format - + indent_str - + mime_fwd - + msg_format - + pgp_autosign - + pgp_autoencrypt - + pgp_replyencrypt - + pgp_replysign - + pgp_replysignencrypted - + pgp_verify_sig - + pgp_create_traditional - + pgp_auto_traditional - + forw_decrypt - + smime_sign_as - + post_indent_str - + print_cmd - + shorten_hierarchy - + ask_followup_to - + ask_x_comment_to - + catchup_newsgroup - + followup_to_poster - + group_index_format - + inews - + mime_subject - + news_cache_dir - + news_server - + newsrc - + nntp_poll - + pop_checkinterval - + post_moderated - + save_unsubscribed - + show_new_news - + show_only_unread - + x_comment_to - + smtp_auth_username - + smtp_auth_password - + envelope_from_address - + user_agent - + diff --git a/doc/manual.xml.tail b/doc/manual.xml.tail index bbe9d18..6f600f4 100644 --- a/doc/manual.xml.tail +++ b/doc/manual.xml.tail @@ -40,162 +40,162 @@ - - L + + L move to the bottom of the page - + move current entry to bottom of page - + move current entry to middle of page - + move current entry to top of page - - : - enter a muttngrc command + + : + enter a madmuttrc command - - q + + q exit this menu - - = + + = move to the first entry - - ] + + ] scroll down 1/2 page - - [ + + [ scroll up 1/2 page - - ? + + ? this screen - - number + + number jump to an index number - - * + + * move to the last entry - - M + + M move to the middle of the page - - j + + j move to the next entry - - > + + > scroll down one line - - z + + z move to the next page - - k + + k move to the previous entry - - > + + > scroll up one line - - Z + + Z move to the previous page - + cycle through all defined mailboxes to rebuild all header caches - - L + + L clear and redraw the screen - - / + + / search for a regular expression - - n + + n search for next match - + search for next match in opposite direction - - / + + / search backwards for a regular expression - - Return + + Return select the current entry - - ! + + ! run a program in a subshell - - t + + t toggle the tag on the current entry - - ; + + ; apply next command to tagged entries - + apply next function ONLY to tagged messages - - H + + H move to the top of the page - + display the keycode for a key press @@ -225,348 +225,348 @@ - - b + + b remail a message to another user - - c + + c open a different folder - - c + + c open a different folder in read only mode - - P + + P check for classic pgp - - W + + W clear a status flag from a message - - C + + C copy a message to a file/mailbox - - a + + a create an alias from a message sender - - C + + C decode a message and copy it to a file/mailbox - - s + + s decode a message and save it to a file/mailbox - - d + + d delete the current entry - - D + + D delete messages matching a pattern - - d + + d delete all messages in subthread - - D + + D delete all messages in thread - - @ + + @ display full address of sender - - h + + h display message and toggle header weeding - - Return + + Return display a message - - e + + e edit the current message - - E + + E edit the current message's Content-Type - - x + + x exit without saving changes - - K + + K extract PGP public keys - - G + + G retrieve mail from POP server - - F + + F toggle a message's 'important' flag - - F + + F wipe PGP passphrase from memory - - f + + f forward a message with comments - - g + + g reply to all recipients - - l + + l show only messages matching a pattern - - L + + L reply to specified mailing list - - m + + m compose a new mail message - - k + + k mail a PGP public key - + jump to the next new message - - Tab + + Tab jump to the next new or unread message - - n + + n jump to the next subthread - - N + + N jump to the next thread - - j + + j move to the next undeleted message - + jump to the next unread message - - P + + P jump to parent message in thread - - | + + | pipe message/attachment to a shell command - + jump to the previous new message - - Tab + + Tab jump to the previous new or unread message - - Z + + Z move to the previous page - - p + + p jump to previous subthread - - P + + P jump to previous thread - - k + + k move to the last undelete message - + jump to the previous unread message - - p + + p print the current entry - - Q + + Q query external program for addresses - - q + + q save changes to mailbox and quit - - r + + r mark the current subthread as read - - R + + R mark the current thread as read - - R + + R recall a postponed message - - r + + r reply to a message - - e + + e resend message and preserve MIME structure - - s + + s save message/attachment to a file - - w + + w set a status flag on a message - - V - show the Mutt-ng version number and date + + V + show the Madmutt version number and date - - l + + l show currently active limit pattern, if any - - o + + o sort messages - - O + + O sort messages in reverse order - - $ + + $ save changes to mailbox - - T + + T tag messages matching a pattern - - t + + t tag/untag all messages in the current thread - - N + + N toggle a message's 'new' flag - - % + + % toggle whether the mailbox will be rewritten - - u + + u undelete the current entry - - U + + U undelete messages matching a pattern - - u + + u undelete all messages in subthread - - U + + U undelete all messages in thread - - T + + T untag messages matching a pattern - - v + + v show MIME attachments @@ -595,373 +595,373 @@ - + jump to the bottom of the message - - b + + b remail a message to another user - - c + + c open a different folder - - c + + c open a different folder in read only mode - - P + + P check for classic pgp - - C + + C copy a message to a file/mailbox - - a + + a create an alias from a message - - C + + C decode a message and copy it to a file/mailbox - - s + + s decode a message and save it to a file/mailbox - - d + + d delete the current entry - - d + + d delete all messages in subthread - - D + + D delete all messages in thread - - @ + + @ display full address of sender - - h + + h display message and toggle header weeding - - e + + e edit the current message - - E + + E edit the current message's Content-Type - - : - enter a muttngrc command + + : + enter a madmuttrc command - - i + + i return to the main-menu - - K + + K extract PGP public keys - - F + + F toggle a message's 'important' flag - - F + + F wipe PGP passphrase from memory - - f + + f forward a message with comments - - g + + g reply to all recipients - + move up one-half page - + move down one-half page - - ? + + ? this screen - - L + + L reply to specified mailing list - - m + + m compose a new mail message - - k + + k mail a PGP public key - - N + + N toggle a message's 'new' flag - - Return + + Return scroll down one line - - J + + J move to the next entry - + jump to the next new message - - Tab + + Tab jump to the next new or unread message - + move to the next page - - n + + n jump to the next subthread - - N + + N jump to the next thread - - j + + j move to the next undeleted message - + jump to the next unread message - - P + + P jump to parent message in thread - - | + + | pipe message/attachment to a shell command - - BackSpace + + BackSpace scroll up one line - - K + + K move to the previous entry - + jump to the previous new message - + jump to the previous new or unread message - - - + + - move to the previous page - - p + + p jump to previous subthread - - P + + P jump to previous thread - - k + + k move to the last undelete message - + jump to the previous unread message - - p + + p print the current entry - - Q + + Q save changes to mailbox and quit - - r + + r mark the current subthread as read - - R + + R mark the current thread as read - - R + + R recall a postponed message - - L + + L clear and redraw the screen - - r + + r reply to a message - - s + + s save message/attachment to a file - - / + + / search for a regular expression - - n + + n search for next match - + search for next match in opposite direction - - / + + / search backwards for a regular expression - - \ + + \ toggle search pattern coloring - - ! + + ! invoke a command in a subshell - - V - show the Mutt-ng version number and date + + V + show the Madmutt version number and date - - S + + S skip beyond quoted text - - $ + + $ save changes to mailbox - - t + + t tag a message - - T + + T toggle display of quoted text - - ^ + + ^ jump to the top of the message - - u + + u undelete the current entry - - u + + u undelete all messages in subthread - - U + + U undelete all messages in thread - - v + + v show MIME attachments @@ -990,18 +990,18 @@ - - / + + / search for a regular expression - - n + + n search for next match - - / + + / search backwards for a regular expression @@ -1030,43 +1030,43 @@ - - a + + a create an alias from a message sender - - m + + m compose a new mail message - - Q + + Q query external program for addresses - - A + + A append new query results to current results - - / + + / search for a regular expression - - n + + n search for next match - + search for next match in opposite direction - - / + + / search backwards for a regular expression @@ -1095,93 +1095,93 @@ - - b + + b remail a message to another user - - v + + v toggle display of subparts - - d + + d delete the current entry - - h + + h display message and toggle header weeding - - E + + E edit the current entry's Content-Type - - K + + K extract PGP public keys - - f + + f forward a message with comments - - g + + g reply to all recipients - - L + + L reply to specified mailing list - - | + + | pipe message/attachment to a shell command - - p + + p print the current entry - - r + + r reply to a message - - e + + e resend message and preserve MIME structure - - s + + s save message/attachment to a file - - u + + u undelete the current entry - - Return + + Return view attachment using mailcap entry if necessary - - m + + m force viewing of attachment using mailcap - - T + + T view attachment as text @@ -1210,168 +1210,168 @@ - - a + + a attach a file(s) to this message - - A + + A attach message(s) to this message - - k + + k attach a PGP public key - - C + + C save message/attachment to a file - - D + + D delete the current entry - - h + + h display message and toggle header weeding - - b + + b edit the BCC list - - c + + c edit the CC list - - d + + d edit attachment description - - E + + E edit attachment transfer-encoding - - f + + f enter a file to save a copy of this message in - - f + + f edit the from: field - - X e + + X e edit the file to be attached - - E + + E edit the message with headers - - e + + e edit the message - - m + + m edit attachment using mailcap entry - - r + + r edit the Reply-To field - - s + + s edit the subject of this message - - t + + t edit the TO list - - T + + T edit attachment type - - F + + F filter attachment through a shell command - - F + + F wipe PGP passphrase from memory - - i + + i run ispell on the message - - n + + n compose new attachment using mailcap entry - - p + + p show PGP options - - | + + | pipe message/attachment to a shell command - - P + + P save this message to send later - - l + + l print the current entry - - R + + R rename/move an attached file - - y + + y send the message - - u + + u toggle whether to delete file after sending it - - Return + + Return view attachment using mailcap entry if necessary - - w + + w write the message to a folder @@ -1400,13 +1400,13 @@ - - d + + d delete the current entry - - u + + u undelete the current entry @@ -1435,73 +1435,73 @@ - - c + + c change directories - - Tab + + Tab check mailboxes for new mail - - m + + m enter a file mask - - / + + / search for a regular expression - - n + + n search for next match - - / + + / search backwards for a regular expression - - N + + N select a new file in this directory - - o + + o sort messages - - O + + O sort messages in reverse order - - Tab + + Tab toggle whether to browse mailboxes or all files - - Space + + Space view file - - s + + s subscribe to current mailbox (IMAP Only) - - u + + u unsubscribe to current mailbox (IMAP Only) - - T + + T toggle view all/subscribed mailboxes (IMAP Only) @@ -1530,13 +1530,13 @@ - - % + + % view the key's user id - - c + + c verify a PGP public key @@ -1565,113 +1565,113 @@ - - BackSpace + + BackSpace delete the char in front of the cursor - - B + + B move the cursor one character to the left - - b + + b move the cursor to the previous word - - A + + A jump to the beginning of the line - - Space + + Space cycle among incoming mailboxes - - c + + c uppercase the first character in the word - - Tab + + Tab complete filename or alias - - T + + T complete address with query - - D + + D delete the char under the cursor - - l + + l lowercase all characters in current word - - E + + E jump to the end of the line - - F + + F move the cursor one character to the right - - f + + f move the cursor to the next word - + scroll down through the history list - + scroll up through the history list - - K + + K delete chars from cursor to end of line - - d + + d delete chars from cursor to end of word - - U + + U delete all chars on the line - - W + + W delete the word in front of the cursor - - V + + V quote the next typed key - + transpose character under cursor with previous - - u + + u uppercase all characters in current word @@ -1700,32 +1700,32 @@ - + Scrolls the mailbox list up 1 page - + Scrolls the mailbox list down 1 page - + Highlights the next mailbox - + Highlights the next mailbox with new mail - + Highlights the previous mailbox - + Opens the currently highlighted mailbox @@ -1883,7 +1883,7 @@ - Mutt-ng is developed by the following people: + Madmutt is developed by the following people: @@ -1902,7 +1902,7 @@ The following people have been very helpful to the - development of Mutt-ng (sorted by surnames): + development of Madmutt (sorted by surnames): @@ -1935,7 +1935,7 @@ This manual is written in XML and transformed via a XSLT - stylesheet into valid DocBook/XML and/or to be again transformed via a XSLT stylesheet into the final formats. @@ -1948,8 +1948,8 @@ To achieve the latter, the sources come with a file called - muttng-manual.xsl introducing the - muttng-doc namespace which offers the following + madmutt-manual.xsl introducing the + madmutt-doc namespace which offers the following tags to be used (note: this is far from being complete, any help towards consistency is highly appreciated). @@ -1958,7 +1958,7 @@ - <muttng-doc:man name="" [sect=""]/> + <madmutt-doc:man name="" [sect=""]/> References to manual pages. If the sect parameter is omitted, it'll @@ -1966,7 +1966,7 @@ - <muttng-doc:envvar name=""/> + <madmutt-doc:envvar name=""/> References to environment variables. The name @@ -1976,7 +1976,7 @@ - <muttng-doc:hook name=""/> + <madmutt-doc:hook name=""/> References to hooks. The string -hook will be added automatically to @@ -1985,7 +1985,7 @@ - <muttng-doc:pattern name="" [full="1"]/> + <madmutt-doc:pattern name="" [full="1"]/> References to patterns. The name parameter must only contain the @@ -1996,11 +1996,11 @@ - <muttng-doc:key [mod="C|E"]>key</muttng-doc:key> + <madmutt-doc:key [mod="C|E"]>key</madmutt-doc:key> Referencing a key.. Because it's somewhat untrivial to always get the right escaping for - , + , there's a tag for it. The optional modifiers C or E stand for Control and Escape respectively. To still allow @@ -2009,13 +2009,13 @@ - <muttng-doc:funcdef name=""/> + <madmutt-doc:funcdef name=""/> Defining a command.. It's used to define a command with the name given in the name parameter. The default key binding must be given via - <muttng-doc:key/> (see above). The string + <madmutt-doc:key/> (see above). The string will be automatically enclosed in <>. Auto-indexing is done. Also an anchor with id @@ -2025,7 +2025,7 @@ - <muttng-doc:funcref name=""/> + <madmutt-doc:funcref name=""/> References to functions.. This is practically the same as the above except that there's no @@ -2033,7 +2033,7 @@ - <muttng-doc:vardef name=""/> + <madmutt-doc:vardef name=""/> Defining a variable. This is to be used by makedoc only to define a @@ -2045,7 +2045,7 @@ - <muttng-doc:varref name=""/> + <madmutt-doc:varref name=""/> References to variables. This practically is the same as above except that the text @@ -2056,7 +2056,7 @@ - <muttng-doc:web url""/> + <madmutt-doc:web url""/> Pretty print a linked URL. As for E-Mail addresses where the text (mostly) equals the @@ -2066,18 +2066,18 @@ - <muttng-doc:rfc num=""/> + <madmutt-doc:rfc num=""/> References to RfC documents. Use this to produce links to RfC document with number given as the num parameter. A link to - will be + will be made. Auto-indexing is done under RfC. - <muttng-doc:cmddef name="" [noanchor="1"]/> + <madmutt-doc:cmddef name="" [noanchor="1"]/> Defining a configuration command. The name of the command is given as the @@ -2089,7 +2089,7 @@ - <muttng-doc:cmdref name=""/> + <madmutt-doc:cmdref name=""/> References to configuration commands. Use this to refer to commands as it builds the proper @@ -2097,9 +2097,9 @@ - <muttng-doc:lstconf/>, - <muttng-doc:lstmail/>, - <muttng-doc:lstshell/> + <madmutt-doc:lstconf/>, + <madmutt-doc:lstmail/>, + <madmutt-doc:lstshell/> Screen layout by context. These are @@ -2114,10 +2114,10 @@ - <muttng-doc:special [docbook=""] [latex=""]/> + <madmutt-doc:special [docbook=""] [latex=""]/> This is intended for specifying special strings for - either DocBook/XML or . @@ -2133,7 +2133,7 @@ To not fully bloat the XSL stylesheet - procuding the code, all tables must have an attribute called texstr which is directly passed to longtable. diff --git a/doc/mbox.man b/doc/mbox.man index faf0969..13bbb87 100644 --- a/doc/mbox.man +++ b/doc/mbox.man @@ -69,7 +69,7 @@ into before storing it. Besides \fBMBOXO\fP and \fBMBOXRD\fP there is also \fBMBOXCL\fP which is \fBMBOXO\fP with a "Content-Length:"-field with the number of bytes in the message body; some MUAs (like -.BR muttng (1)) +.BR madmutt (1)) do automatically transform \fBMBOXO\fP mailboxes into \fBMBOXCL\fP ones when ever they write them back as \fBMBOXCL\fP can be read by any \fBMBOXO\fP-MUA without any problems. @@ -163,7 +163,7 @@ format folders. .PP .\" .SH "SEE ALSO" -.BR muttng (1), +.BR madmutt (1), .BR fcntl (2), .BR flock (2), .BR link (2), diff --git a/doc/mutt.man b/doc/mutt.man index 0b88add..1811708 100644 --- a/doc/mutt.man +++ b/doc/mutt.man @@ -17,16 +17,16 @@ .\" along with this program; if not, write to the Free Software .\" Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111, USA. .\" -.TH mutt-ng 1 Unix "User Manuals" +.TH Madmutt 1 Unix "User Manuals" .SH NAME -mutt-ng \- The Mutt-ng Mail User Agent +Madmutt \- The Madmutt Mail User Agent .SH SYNOPSIS .PP -.B muttng +.B madmutt [-GnRyzZ] [-e \fIcmd\fP] [-F \fIfile\fP] [-g \fIserver\fP] [-m \fItype\fP] [-f \fIfile\fP] .PP -.B muttng +.B madmutt [-nx] [-e \fIcmd\fP] [-a \fIfile\fP] @@ -37,23 +37,23 @@ mutt-ng \- The Mutt-ng Mail User Agent [-b \fIaddr\fP] [-c \fIaddr\fP] \fIaddr\fP [...] .PP -.B muttng +.B madmutt [-n] [-e \fIcmd\fP] [-F \fIfile\fP] [-t | -T] .PP -.B muttng +.B madmutt [-n] [-e \fIcmd\fP] [-F \fIfile\fP] -p .PP -.B muttng +.B madmutt [-n] [-e \fIcmd\fP] [-F \fIfile\fP] -Q \fIquery\fP .PP -.B muttng +.B madmutt [-n] [-e \fIcmd\fP] [-F \fIfile\fP] -A \fIalias\fP .PP -.B muttng +.B madmutt -v[v] .SH DESCRIPTION .PP -Mutt-ng is a small but very powerful text based program for reading electronic +Madmutt is a small but very powerful text based program for reading electronic mail under unix operating systems, including support color terminals, MIME, and a threaded sorting mode. .SH OPTIONS @@ -75,14 +75,14 @@ Specify a configuration command to be run after processing of initialization files. .IP "-f \fImailbox\fP" Specify which mailbox to load. -.IP "-F \fImuttngrc\fP" -Specify an initialization file to read instead of ~/.muttngrc +.IP "-F \fImadmuttrc\fP" +Specify an initialization file to read instead of ~/.madmuttrc .IP "-g \fIserver\fP" -Start Mutt-ng with a listing of subscribed newsgroups at specified newsserver. +Start Madmutt with a listing of subscribed newsgroups at specified newsserver. .IP "-G" -Start Mutt-ng with a listing of subscribed newsgroups. +Start Madmutt with a listing of subscribed newsgroups. .IP "-d" -Specify a debugging level. This will cause muttng to create .muttngdebug files which include +Specify a debugging level. This will cause madmutt to create .madmuttdebug files which include debugging information. .IP "-h" Display help. @@ -94,7 +94,7 @@ Specify a file to include into the body of a message. .IP "-m \fItype\fP " specify a default mailbox type .IP "-n" -Causes Mutt-ng to bypass the system configuration file. +Causes Madmutt to bypass the system configuration file. .IP "-p" Resume a postponed message. .IP "-Q \fIquery\fP" @@ -106,17 +106,17 @@ Open a mailbox in \fIread-only\fP mode. .IP "-s \fIsubject\fP" Specify the subject of the message. .IP "-v" -Display the Mutt-ng version number and compile-time definitions. +Display the Madmutt version number and compile-time definitions. .IP "-x" Emulate the mailx compose mode. .IP "-y" -Start Mutt-ng with a listing of all mailboxes specified by the \fImailboxes\fP +Start Madmutt with a listing of all mailboxes specified by the \fImailboxes\fP command. .IP "-z" -When used with -f, causes Mutt-ng not to start if there are no messages in the +When used with -f, causes Madmutt not to start if there are no messages in the mailbox. .IP "-Z" -Causes Mutt-ng to open the first mailbox specified by the \fImailboxes\fP +Causes Madmutt to open the first mailbox specified by the \fImailboxes\fP command which contains new mail. .SH ENVIRONMENT .PP @@ -147,12 +147,12 @@ Default Reply-To address. Specifies the editor to use when composing messages. .SH FILES .PP -.IP "~/.muttngrc or ~/.muttng/muttngrc" +.IP "~/.madmuttrc or ~/.madmutt/madmuttrc" User configuration file. -.IP "@sysconfdir@/Muttngrc" +.IP "@sysconfdir@/madmuttrc" System-wide configuration file. .IP "/tmp/muttXXXXXX" -Temporary files created by Mutt-ng. +Temporary files created by Madmutt. .IP "~/.mailcap" User definition for handling non-text MIME types. .IP "@sysconfdir@/mailcap" @@ -161,10 +161,10 @@ System definition for handling non-text MIME types. User's personal mapping between MIME types and file extensions. .IP "@sysconfdir@/mime.types" System mapping between MIME types and file extensions. -.IP "@bindir@/muttng_dotlock" +.IP "@bindir@/madmutt_dotlock" The privileged dotlocking program. .IP "@docdir@/manual.txt" -The Mutt-ng manual. +The Madmutt manual. .SH BUGS .PP None. Mutts have fleas, not bugs. @@ -174,16 +174,16 @@ Suspend/resume while editing a file with an external editor does not work under SunOS 4.x if you use the curses lib in /usr/5lib. It \fIdoes\fP work with the S-Lang library, however. .PP -Resizing the screen while using an external pager causes Mutt-ng to go haywire +Resizing the screen while using an external pager causes Madmutt to go haywire on some systems. .PP suspend/resume does not work under Ultrix. .PP The help line for the index menu is not updated if you change the bindings -for one of the functions listed while Mutt-ng is running. +for one of the functions listed while Madmutt is running. .PP For a more up-to-date list of bugs, errm, fleas, please visit the -mutt-ng project's bug tracking system under http://developer.berlios.de/projects/mutt-ng/. To +Madmutt project's bug tracking system under http://developer.berlios.de/projects/Madmutt/. To report a bug, please use the .BR fleang (1) program. @@ -199,21 +199,21 @@ GNU General Public License for more details. .BR mailcap (5), .BR maildir (5), .BR mbox (5), -.BR muttng_dotlock (1), -.BR muttngrc (5), +.BR madmutt_dotlock (1), +.BR madmuttrc (5), .BR ncurses (3), .BR sendmail (1), .BR smail (1) .PP -Mutt-ng Home Page: http://www.muttng.org +Madmutt Home Page: http://www.madmutt.org .PP -The Mutt-ng manual: http://www.muttng.org/manual +The Madmutt manual: http://www.madmutt.org/manual .PP The GNU General Public License. .SH AUTHOR .PP Original mutt was/is written Michael Elkins, and others. .PP -Mutt-ng is written by Andreas Krennmair and others. +Madmutt is written by Andreas Krennmair and others. .PP -Use to contact the developers. +Use to contact the developers. diff --git a/doc/muttbug.man b/doc/muttbug.man index 18683ff..ef6fef8 100644 --- a/doc/muttbug.man +++ b/doc/muttbug.man @@ -19,12 +19,12 @@ .\" .TH fleang 1 "January 2005" Unix "User Manuals" .SH NAME -fleang \- Report a bug (or rather a flea) in Mutt-ng. (OBSOLETE) +fleang \- Report a bug (or rather a flea) in Madmutt. (OBSOLETE) .SH DESCRIPTION .PP .B fleang used to be a shell script which helped you to submit a bug report against the -.BR muttng (1) +.BR madmutt (1) mail user agent. .PP If you want to submit bugs with a web interface use: diff --git a/doc/muttrc.man.head b/doc/muttrc.man.head index faf4403..7f474e5 100644 --- a/doc/muttrc.man.head +++ b/doc/muttrc.man.head @@ -18,12 +18,12 @@ .\" along with this program; if not, write to the Free Software .\" Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA. .\" -.TH muttngrc 5 "September 2002" Unix "User Manuals" +.TH madmuttrc 5 "September 2002" Unix "User Manuals" .SH NAME -muttngrc \- Configuration file for the Mutt-ng Mail User Agent +madmuttrc \- Configuration file for the Madmutt Mail User Agent .SH DESCRIPTION .PP -A Mutt-ng configuration file consists of a series of \(lqcommands\(rq. +A Madmutt configuration file consists of a series of \(lqcommands\(rq. Each line of the file may contain one or more commands. When multiple commands are used, they must be separated by a semicolon (\(lq\fB;\fP\(rq). @@ -80,9 +80,9 @@ all aliases when \(lq\fB*\fP\(rq is used as an argument. \fBunalternates\fP [\fB * \fP | \fIregexp\fP [ \fB,\fP \fIregexp\fP [ ... ]] ] .fi .IP -\fBalternates\fP is used to inform Mutt-ng about alternate addresses +\fBalternates\fP is used to inform Madmutt about alternate addresses where you receive mail; you can use regular expressions to specify -alternate addresses. This affects Mutt-ng's idea about messages +alternate addresses. This affects Madmutt's idea about messages from you, and messages addressed to you. \fBunalternates\fP removes a regular expression from the list of known alternates. .PP @@ -92,7 +92,7 @@ a regular expression from the list of known alternates. .fi .IP \fBalternative_order\fP command permits you to define an order of preference which is -used by Mutt-ng to determine which part of a +used by Madmutt to determine which part of a \fBmultipart/alternative\fP body to display. A subtype of \(lq\fB*\fP\(rq matches any subtype, as does an empty subtype. \fBunalternative_order\fP removes entries from the @@ -104,7 +104,7 @@ as an argument. \fBunauto_view\fP \fItype\fP[\fB/\fP\fIsubtype\fP] [ ... ] .fi .IP -This commands permits you to specify that Mutt-ng should automatically +This commands permits you to specify that Madmutt should automatically convert the given MIME types to text/plain when displaying messages. For this to work, there must be a .BR mailcap (5) @@ -119,7 +119,7 @@ matches any subtype, as does an empty subtype. .fi .IP This command permits you to define a list of "data" MIME content -types for which Mutt-ng will try to determine the actual file type from +types for which Madmutt will try to determine the actual file type from the file name, and not use a .BR mailcap (5) entry given for the original MIME type. For instance, you may add @@ -137,7 +137,7 @@ Valid maps are: .BR pager ", " pgp ", " postpone ", " .BR mix . .IP -For more information on keys and functions, please consult the Mutt-ng +For more information on keys and functions, please consult the Madmutt Manual. .TP \fBaccount-hook\fP [\fB!\fP]\fIregexp\fP \fIcommand\fP @@ -147,7 +147,7 @@ to adjust configuration settings to different IMAP or POP servers. \fBcharset-hook\fP \fIalias\fP \fIcharset\fP This 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-ng. +name not known to Madmutt. .TP \fBiconv-hook\fP \fIcharset\fP \fIlocal-charset\fP This command defines a system-specific name for a character set. @@ -163,7 +163,7 @@ In this specific case, you'd put this into your configuration file: .B "iconv-hook iso-8859-1 8859-1" .TP \fBmessage-hook\fP [\fB!\fP]\fIpattern\fP \fIcommand\fP -Before Mutt-ng displays (or formats for replying or forwarding) a +Before Madmutt displays (or formats for replying or forwarding) a message which matches the given \fIpattern\fP (or, when it is preceded by an exclamation mark, does not match the \fIpattern\fP), the given \fIcommand\fP is executed. When multiple @@ -171,7 +171,7 @@ the given \fIcommand\fP is executed. When multiple which they occur in the configuration file. .TP \fBfolder-hook\fP [\fB!\fP]\fIregexp\fP \fIcommand\fP -When Mutt-ng enters a folder which matches \fIregexp\fP (or, when +When Madmutt enters a folder which matches \fIregexp\fP (or, when \fIregexp\fP is preceded by an exclamation mark, does not match \fIregexp\fP), the given \fIcommand\fP is executed. .IP @@ -232,7 +232,7 @@ the above mentioned list of ignored headers. \fBunsubscribe\fP \fIregexp\fP [ \fIregexp\fP ... ] .fi .IP -Mutt-ng maintains two lists of mailing list address patterns, a list of +Madmutt maintains two lists of mailing list address patterns, a list of subscribed mailing lists, and a list of known mailing lists. All subscribed mailing lists are known. Patterns use regular expressions. .IP @@ -244,7 +244,7 @@ and subscribed mailing lists. The \fBunsubscribe\fP command removes it from the list of subscribed mailing lists. .TP \fBmbox-hook\fP [\fB!\fP]\fIpattern\fP \fImailbox\fP -When Mutt-ng changes to a mail folder which matches \fIpattern\fP, +When Madmutt changes to a mail folder which matches \fIpattern\fP, \fImailbox\fP will be used as the \(lqmbox\(rq folder, i.e., read messages will be moved to that folder when the mail folder is left. .IP @@ -272,7 +272,7 @@ the messages you compose. \fBunmy_hdr\fP will remove the given user-defined headers. .TP \fBhdr_order\fP \fIheader1\fP \fIheader2\fP [ ... ] -With this command, you can specify an order in which Mutt-ng will +With this command, you can specify an order in which Madmutt will attempt to present headers to you when viewing messages. .TP \fBsave-hook\fP [\fB!\fP]\fIpattern\fP \fIfilename\fP @@ -325,7 +325,7 @@ or even just an arbitrary search string. .IP These commands provide a way to handle compressed folders. The given \fBregexp\fP specifies which folders are taken as compressed (e.g. -"\fI\\\\.gz$\fP"). The commands tell Mutt-ng how to uncompress a folder +"\fI\\\\.gz$\fP"). The commands tell Madmutt how to uncompress a folder (\fBopen-hook\fP), compress a folder (\fBclose-hook\fP) or append a compressed mail to a compressed folder (\fBappend-hook\fP). The \fIcommand\fP string is the @@ -348,7 +348,7 @@ This command adds the named \fIstring\fP to the keyboard buffer. These commands are used to set and manipulate configuration varibles. .IP -Mutt-ng knows four basic types of variables: boolean, number, string +Madmutt knows four basic types of variables: boolean, number, string and quadoption. Boolean variables can be \fBset\fP (true), \fBunset\fP (false), or \fBtoggle\fPd. Number variables can be assigned a positive integer value. @@ -379,9 +379,9 @@ The given file will be evaluated as a configuration file. \fBnospam\fP \fIpattern\fP .fi These commands define spam-detection patterns from external spam -filters, so that Mutt-ng can sort, limit, and search on +filters, so that Madmutt can sort, limit, and search on ``spam tags'' or ``spam attributes'', or display them -in the index. See the Mutt-ng manual for details. +in the index. See the Madmutt manual for details. .TP \fBunhook\fP [\fB * \fP | \fIhook-type\fP ] This command will remove all hooks of a given type, or all hooks @@ -389,13 +389,13 @@ when \(lq\fB*\fP\(rq is used as an argument. \fIhook-type\fP can be any of the \fB-hook\fP commands documented above. .SH PATTERNS .PP -In various places with Mutt-ng, including some of the abovementioned +In various places with Madmutt, including some of the abovementioned \fBhook\fP commands, you can specify patterns to match messages. .SS Constructing Patterns .PP A simple pattern consists of an operator of the form \(lq\fB~\fP\fIcharacter\fP\(rq, possibly followed by a parameter -against which Mutt-ng is supposed to match the object specified by +against which Madmutt is supposed to match the object specified by this operator. (For a list of operators, see below.) .PP With some of these operators, the object to be matched consists of @@ -406,15 +406,15 @@ hat (\(lq\fB^\fP\(rq) character to such a pattern to indicate that .PP You can construct complex patterns by combining simple patterns with logical operators. Logical AND is specified by simply concatenating -two simple patterns, for instance \(lq~C mutt-ng-dev ~s bug\(rq. +two simple patterns, for instance \(lq~C Madmutt-dev ~s bug\(rq. Logical OR is specified by inserting a vertical bar (\(lq\fB|\fP\(rq) between two patterns, for instance \(lq~C mutti-ng-dev | ~s bug\(rq. Additionally, you can negate a pattern by prepending a bang (\(lq\fB!\fP\(rq) character. For logical grouping, use braces -(\(lq()\(rq). Example: \(lq!(~t Mutt-ng|~c Mutt-ng) ~f elkins\(rq. +(\(lq()\(rq). Example: \(lq!(~t Madmutt|~c Madmutt) ~f elkins\(rq. .SS Simple Patterns .PP -Mutt-ng understands the following simple patterns: +Madmutt understands the following simple patterns: .PP .TS l l. @@ -476,13 +476,13 @@ two-digit date, optionally followed by a two-digit month, optionally followed by a year specifications. Omitted fields default to the current month and year. .PP -Mutt-ng understands either two or four digit year specifications. When -given a two-digit year, Mutt-ng will interpret values less than 70 as +Madmutt understands either two or four digit year specifications. When +given a two-digit year, Madmutt will interpret values less than 70 as lying in the 21st century (i.e., \(lq38\(rq means 2038 and not 1938, and \(lq00\(rq is interpreted as 2000), and values greater than or equal to 70 as lying in the 20th century. .PP -Note that this behaviour \fIis\fP Y2K compliant, but that Mutt-ng +Note that this behaviour \fIis\fP Y2K compliant, but that Madmutt \fIdoes\fP have a Y2.07K problem. .PP If a date range consists of a single date, the operator in question diff --git a/doc/muttrc.man.tail b/doc/muttrc.man.tail index 38bd4c7..2f0b895 100644 --- a/doc/muttrc.man.tail +++ b/doc/muttrc.man.tail @@ -6,15 +6,15 @@ .BR mailcap (5), .BR maildir (5), .BR mbox (5), -.BR muttng (1), +.BR madmutt (1), .BR printf (3), .BR regex (7), .BR strftime (3) .PP -The Mutt-ng Manual +The Madmutt Manual .PP -The Mutt-ng home page: http://www.muttng.org +The Madmutt home page: http://www.muttng.org .SH AUTHOR .PP -Michael Elkins, and others. Use to contact +Michael Elkins, and others. Use to contact the developers. diff --git a/doc/patch-notes.txt b/doc/patch-notes.txt index 9ed2597..370d18d 100644 --- a/doc/patch-notes.txt +++ b/doc/patch-notes.txt @@ -1,8 +1,8 @@ This document descibes what to do after allplying a patch -If you want to add patches to Mutt-ng just add the name +If you want to add patches to Madmutt just add the name of the patch to the PATCHES file after applying the patch. -Mutt-ng recognizes this patch automatically and shows it +Madmutt recognizes this patch automatically and shows it in --help e.g. Every patch name should have the format: diff --git a/dotlock.c b/dotlock.c index f89fb1f..e196464 100644 --- a/dotlock.c +++ b/dotlock.c @@ -273,7 +273,7 @@ static void END_PRIVILEGED (void) static void usage (const char *av0) { - fprintf (stderr, "dotlock [Mutt-ng %s]\n", VERSION); + fprintf (stderr, "dotlock [Madmutt %s]\n", VERSION); fprintf (stderr, "usage: %s [-t|-f|-u|-d] [-p] [-r ] file\n", av0); fputs ("\noptions:" diff --git a/init.c b/init.c index 7de40b8..69de16b 100644 --- a/init.c +++ b/init.c @@ -2791,15 +2791,15 @@ void mutt_init (int skip_sys_rc, LIST * commands) /* Process the global rc file if it exists and the user hasn't explicity requested not to via "-n". */ if (!skip_sys_rc) { - snprintf (buffer, sizeof(buffer), "%s/Muttngrc-%s", SYSCONFDIR, + snprintf (buffer, sizeof(buffer), "%s/Madmuttrc-%s", SYSCONFDIR, MUTT_VERSION); if (access (buffer, F_OK) == -1) - snprintf (buffer, sizeof(buffer), "%s/Muttngrc", SYSCONFDIR); + snprintf (buffer, sizeof(buffer), "%s/Madmuttrc", SYSCONFDIR); if (access (buffer, F_OK) == -1) - snprintf (buffer, sizeof(buffer), "%s/Muttngrc-%s", PKGDATADIR, + snprintf (buffer, sizeof(buffer), "%s/Madmuttrc-%s", PKGDATADIR, MUTT_VERSION); if (access (buffer, F_OK) == -1) - snprintf (buffer, sizeof(buffer), "%s/Muttngrc", PKGDATADIR); + snprintf (buffer, sizeof(buffer), "%s/Madmuttrc", PKGDATADIR); if (access (buffer, F_OK) != -1) { if (source_rc (buffer, &err) != 0) { fputs (err.data, stderr); diff --git a/init.h b/init.h index 65d5e1f..82fab85 100644 --- a/init.h +++ b/init.h @@ -152,7 +152,7 @@ struct option_t MuttVars[] = { ** The default file in which to save aliases created by the ** ``$create-alias'' function. ** .pp - ** \fBNote:\fP Mutt-ng will not automatically source this file; you must + ** \fBNote:\fP Madmutt will not automatically source this file; you must ** explicitly use the ``$source'' command for it to be executed. */ {"alias_format", DT_STR, R_NONE, UL &AliasFmt, "%4n %2f %t %-10a %r"}, @@ -198,19 +198,19 @@ struct option_t MuttVars[] = { {"ascii_chars", DT_BOOL, R_BOTH, OPTASCIICHARS, "no" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will use plain ASCII characters when displaying thread + ** If \fIset\fP, Madmutt will use plain ASCII characters when displaying thread ** and attachment trees, instead of the default \fTACS\fP characters. */ {"askbcc", DT_BOOL, R_NONE, OPTASKBCC, "no" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will prompt you for blind-carbon-copy (Bcc) recipients + ** If \fIset\fP, Madmutt will prompt you for blind-carbon-copy (Bcc) recipients ** before editing an outgoing message. */ {"askcc", DT_BOOL, R_NONE, OPTASKCC, "no" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will prompt you for carbon-copy (Cc) recipients before + ** If \fIset\fP, Madmutt will prompt you for carbon-copy (Cc) recipients before ** editing the body of an outgoing message. */ {"assumed_charset", DT_STR, R_NONE, UL &AssumedCharset, "us-ascii"}, @@ -237,7 +237,7 @@ struct option_t MuttVars[] = { ** Availability: NNTP ** ** .pp - ** If \fIset\fP, Mutt-ng will prompt you for the \fTFollowup-To:\fP header + ** If \fIset\fP, Madmutt will prompt you for the \fTFollowup-To:\fP header ** field before editing the body of an outgoing news article. */ {"nntp_ask_x_comment_to", DT_BOOL, R_NONE, OPTASKXCOMMENTTO, "no" }, @@ -246,7 +246,7 @@ struct option_t MuttVars[] = { ** Availability: NNTP ** ** .pp - ** If \fIset\fP, Mutt-ng will prompt you for the \fTX-Comment-To:\fP header + ** If \fIset\fP, Madmutt will prompt you for the \fTX-Comment-To:\fP header ** field before editing the body of an outgoing news article. */ #endif @@ -297,10 +297,10 @@ struct option_t MuttVars[] = { /* ** .pp ** If this variable is \fIunset\fP, when operating (saving, printing, piping, - ** etc) on a list of tagged attachments, Mutt-ng will concatenate the + ** etc) on a list of tagged attachments, Madmutt will concatenate the ** attachments and will operate on them as a single attachment. The ** ``$$attach_sep'' separator is added after each attachment. When \fIset\fP, - ** Mutt-ng will operate on the attachments one by one. + ** Madmutt will operate on the attachments one by one. */ {"attribution", DT_STR, R_NONE, UL &Attribution, "On %d, %n wrote:"}, /* @@ -312,7 +312,7 @@ struct option_t MuttVars[] = { {"autoedit", DT_BOOL, R_NONE, OPTAUTOEDIT, "no" }, /* ** .pp - ** When \fIset\fP along with ``$$edit_headers'', Mutt-ng will skip the initial + ** When \fIset\fP along with ``$$edit_headers'', Madmutt will skip the initial ** send-menu and allow you to immediately begin editing the body of your ** message. The send-menu may still be accessed once you have finished ** editing the body of your message. @@ -330,12 +330,12 @@ struct option_t MuttVars[] = { {"beep", DT_BOOL, R_NONE, OPTBEEP, "yes" }, /* ** .pp - ** When this variable is \fIset\fP, Mutt-ng will beep when an error occurs. + ** When this variable is \fIset\fP, Madmutt will beep when an error occurs. */ {"beep_new", DT_BOOL, R_NONE, OPTBEEPNEW, "no" }, /* ** .pp - ** When this variable is \fIset\fP, Mutt-ng will beep whenever it prints a message + ** When this variable is \fIset\fP, Madmutt will beep whenever it prints a message ** notifying you of new mail. This is independent of the setting of the ** ``$$beep'' variable. */ @@ -350,7 +350,7 @@ struct option_t MuttVars[] = { {"bounce_delivered", DT_BOOL, R_NONE, OPTBOUNCEDELIVERED, "yes" }, /* ** .pp - ** When this variable is \fIset\fP, Mutt-ng will include + ** When this variable is \fIset\fP, Madmutt will include ** \fTDelivered-To:\fP header fields when bouncing messages. ** Postfix users may wish to \fIunset\fP this variable. */ @@ -370,7 +370,7 @@ struct option_t MuttVars[] = { ** Availability: NNTP ** ** .pp - ** If this variable is \fIset\fP, Mutt-ng will mark all articles in a newsgroup + ** If this variable is \fIset\fP, Madmutt will mark all articles in a newsgroup ** as read when you leaving it. */ #endif @@ -385,7 +385,7 @@ struct option_t MuttVars[] = { ** \fBNote:\fP this option only affects \fImaildir\fP and \fIMH\fP style ** mailboxes. ** .pp - ** When \fIset\fP, Mutt-ng will check for new mail delivered while the + ** When \fIset\fP, Madmutt will check for new mail delivered while the ** mailbox is open. Especially with MH mailboxes, this operation can ** take quite some time since it involves scanning the directory and ** checking each file to see if it has already been looked at. If it's @@ -394,7 +394,7 @@ struct option_t MuttVars[] = { {"collapse_unread", DT_BOOL, R_NONE, OPTCOLLAPSEUNREAD, "yes" }, /* ** .pp - ** When \fIunset\fP, Mutt-ng will not collapse a thread if it contains any + ** When \fIunset\fP, Madmutt will not collapse a thread if it contains any ** unread messages. */ {"count_attachments", DT_BOOL, R_NONE, OPTCOUNTATTACH, "yes"}, @@ -412,10 +412,10 @@ struct option_t MuttVars[] = { {"uncollapse_jump", DT_BOOL, R_NONE, OPTUNCOLLAPSEJUMP, "no" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will jump to the next unread message, if any, + ** When \fIset\fP, Madmutt will jump to the next unread message, if any, ** when the current thread is \fIun\fPcollapsed. */ - {"compose_format", DT_STR, R_BOTH, UL &ComposeFormat, "-- Mutt-ng: Compose [Approx. msg size: %l Atts: %a]%>-"}, + {"compose_format", DT_STR, R_BOTH, UL &ComposeFormat, "-- Madmutt: Compose [Approx. msg size: %l Atts: %a]%>-"}, /* ** .pp ** Controls the format of the status line displayed in the ``compose'' @@ -426,7 +426,7 @@ struct option_t MuttVars[] = { ** .dt %a .dd total number of attachments ** .dt %h .dd local hostname ** .dt %l .dd approximate size (in bytes) of the current message - ** .dt %v .dd Mutt-ng version string + ** .dt %v .dd Madmutt version string ** .de ** .pp ** See the text describing the ``$$status_format'' option for more @@ -435,27 +435,27 @@ struct option_t MuttVars[] = { {"config_charset", DT_STR, R_NONE, UL &ConfigCharset, "" }, /* ** .pp - ** When defined, Mutt-ng will recode commands in rc files from this + ** When defined, Madmutt will recode commands in rc files from this ** encoding. */ {"confirmappend", DT_BOOL, R_NONE, OPTCONFIRMAPPEND, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will prompt for confirmation when appending messages to + ** When \fIset\fP, Madmutt will prompt for confirmation when appending messages to ** an existing mailbox. */ {"confirmcreate", DT_BOOL, R_NONE, OPTCONFIRMCREATE, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will prompt for confirmation when saving messages to a + ** When \fIset\fP, Madmutt will prompt for confirmation when saving messages to a ** mailbox which does not yet exist before creating it. */ {"connect_timeout", DT_NUM, R_NONE, UL &ConnectTimeout, "30" }, /* ** .pp - ** Causes Mutt-ng to timeout a network connection (for IMAP or POP) after this + ** Causes Madmutt to timeout a network connection (for IMAP or POP) after this ** many seconds if the connection is not able to be established. A negative - ** value causes Mutt-ng to wait indefinitely for the connection to succeed. + ** value causes Madmutt to wait indefinitely for the connection to succeed. */ {"content_type", DT_STR, R_NONE, UL &ContentType, "text/plain"}, /* @@ -475,7 +475,7 @@ struct option_t MuttVars[] = { /* ** .pp ** This variable controls the use the GPGME enabled crypto backends. - ** If it is \fIset\fP and Mutt-ng was build with gpgme support, the gpgme code for + ** If it is \fIset\fP and Madmutt was build with gpgme support, the gpgme code for ** S/MIME and PGP will be used instead of the classic code. ** .pp ** \fBNote\fP: You need to use this option in your \fT.madmuttrc\fP configuration @@ -485,7 +485,7 @@ struct option_t MuttVars[] = { {"crypt_autopgp", DT_BOOL, R_NONE, OPTCRYPTAUTOPGP, "yes" }, /* ** .pp - ** This variable controls whether or not Mutt-ng may automatically enable + ** This variable controls whether or not Madmutt may automatically enable ** PGP encryption/signing for messages. See also ``$$crypt_autoencrypt'', ** ``$$crypt_replyencrypt'', ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''. @@ -493,7 +493,7 @@ struct option_t MuttVars[] = { {"crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, "yes" }, /* ** .pp - ** This variable controls whether or not Mutt-ng may automatically enable + ** This variable controls whether or not Madmutt may automatically enable ** S/MIME encryption/signing for messages. See also ``$$crypt_autoencrypt'', ** ``$$crypt_replyencrypt'', ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''. @@ -568,14 +568,14 @@ struct option_t MuttVars[] = { {"delete_untag", DT_BOOL, R_NONE, OPTDELETEUNTAG, "yes" }, /* ** .pp - ** If this option is \fIset\fP, Mutt-ng will untag messages when marking them + ** If this option is \fIset\fP, Madmutt will untag messages when marking them ** for deletion. This applies when you either explicitly delete a message, ** or when you save it to another folder. */ {"digest_collapse", DT_BOOL, R_NONE, OPTDIGESTCOLLAPSE, "yes" }, /* ** .pp - ** If this option is \fIset\fP, Mutt-ng's received-attachments menu will not show the subparts of + ** If this option is \fIset\fP, Madmutt's received-attachments menu will not show the subparts of ** individual messages in a multipart/digest. To see these subparts, press 'v' on that menu. */ {"display_filter", DT_PATH, R_PAGER, UL &DisplayFilter, ""}, @@ -593,7 +593,7 @@ struct option_t MuttVars[] = { ** ** .pp ** Contains the path of the \fTmadmutt_dotlock(1)\fP binary to be used by - ** Mutt-ng. + ** Madmutt. */ #endif {"dsn_notify", DT_STR, R_NONE, UL &DsnNotify, ""}, @@ -626,7 +626,7 @@ struct option_t MuttVars[] = { {"duplicate_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTDUPTHREADS, "yes" }, /* ** .pp - ** This variable controls whether Mutt-ng, when sorting by threads, threads + ** This variable controls whether Madmutt, when sorting by threads, threads ** messages with the same \fTMessage-ID:\fP header field together. ** If it is \fIset\fP, it will indicate that it thinks they are duplicates ** of each other with an equals sign in the thread diagram. @@ -659,20 +659,20 @@ struct option_t MuttVars[] = { {"editor", DT_PATH, R_NONE, UL &Editor, "" }, /* ** .pp - ** This variable specifies which editor is used by Mutt-ng. + ** This variable specifies which editor is used by Madmutt. ** It defaults to the value of the \fT$$$VISUAL\fP, or \fT$$$EDITOR\fP, environment ** variable, or to the string "\fTvi\fP" if neither of those are set. */ {"encode_from", DT_BOOL, R_NONE, OPTENCODEFROM, "no" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will \fTquoted-printable\fP encode messages when + ** When \fIset\fP, Madmutt will \fTquoted-printable\fP encode messages when ** they contain the string ``\fTFrom \fP'' (note the trailing space) ** in the beginning of a line. Useful to avoid the tampering certain mail ** delivery and transport agents tend to do with messages. ** ** .pp - ** \fBNote:\fP as Mutt-ng currently violates RfC3676 defining + ** \fBNote:\fP as Madmutt currently violates RfC3676 defining ** \fTformat=flowed\fP, it's '\fP - ** when replying to the Mutt-ng developer's mailing list and Mutt-ng takes this email address. + ** \fTsend-hook Madmutt-devel@lists.berlios.de 'my_hdr From: Foo Bar '\fP + ** when replying to the Madmutt developer's mailing list and Madmutt takes this email address. ** .pp ** Defaults to the contents of the environment variable \fT$$$EMAIL\fP. */ {"gecos_mask", DT_RX, R_NONE, UL &GecosMask, "^[^,]*"}, /* ** .pp - ** A regular expression used by Mutt-ng to parse the GECOS field of a password + ** A regular expression used by Madmutt to parse the GECOS field of a password ** entry when expanding the alias. By default the regular expression is set ** to ``\fT^[^,]*\fP'' which will return the string up to the first ``\fT,\fP'' encountered. ** If the GECOS field contains a string like "lastname, firstname" then you ** should do: \fTset gecos_mask=".*"\fP. ** .pp ** This can be useful if you see the following behavior: you address a e-mail - ** to user ID stevef whose full name is Steve Franklin. If Mutt-ng expands + ** to user ID stevef whose full name is Steve Franklin. If Madmutt expands ** stevef to ``Franklin'' stevef@foo.bar then you should set the gecos_mask to - ** a regular expression that will match the whole name so Mutt-ng will expand + ** a regular expression that will match the whole name so Madmutt will expand ** ``Franklin'' to ``Franklin, Steve''. */ #ifdef USE_NNTP @@ -911,7 +911,7 @@ struct option_t MuttVars[] = { {"header", DT_BOOL, R_NONE, OPTHEADER, "no" }, /* ** .pp - ** When \fIset\fP, this variable causes Mutt-ng to include the header + ** When \fIset\fP, this variable causes Madmutt to include the header ** of the message you are replying to into the edit buffer. ** The ``$$weed'' setting applies. */ @@ -923,14 +923,14 @@ struct option_t MuttVars[] = { ** .pp ** \fBNote:\fP The binding will not be displayed correctly if the ** function is bound to a sequence rather than a single keystroke. Also, - ** the help line may not be updated if a binding is changed while Mutt-ng is + ** the help line may not be updated if a binding is changed while Madmutt is ** running. Since this variable is primarily aimed at new users, neither ** of these should present a major problem. */ {"hidden_host", DT_BOOL, R_NONE, OPTHIDDENHOST, "no" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will skip the host name part of ``$$hostname'' variable + ** When \fIset\fP, Madmutt will skip the host name part of ``$$hostname'' variable ** when adding the domain part to addresses. This variable does not ** affect the generation of \fTMessage-ID:\fP header fields, and it will not lead to the ** cut-off of first-level domains. @@ -938,33 +938,33 @@ struct option_t MuttVars[] = { {"hide_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDELIMITED, "no" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden + ** When \fIset\fP, Madmutt will not show the presence of messages that are hidden ** by limiting, in the thread tree. */ {"hide_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDEMISSING, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will not show the presence of missing messages in the + ** When \fIset\fP, Madmutt will not show the presence of missing messages in the ** thread tree. */ {"hide_thread_subject", DT_BOOL, R_TREE|R_INDEX, OPTHIDETHREADSUBJECT, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will not show the subject of messages in the thread + ** When \fIset\fP, Madmutt will not show the subject of messages in the thread ** tree that have the same subject as their parent or closest previously ** displayed sibling. */ {"hide_top_limited", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPLIMITED, "no" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will not show the presence of messages that are hidden + ** When \fIset\fP, Madmutt will not show the presence of messages that are hidden ** by limiting, at the top of threads in the thread tree. Note that when ** $$hide_missing is \fIset\fP, this option will have no effect. */ {"hide_top_missing", DT_BOOL, R_TREE|R_INDEX, OPTHIDETOPMISSING, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will not show the presence of missing messages at the + ** When \fIset\fP, Madmutt will not show the presence of missing messages at the ** top of threads in the thread tree. Note that when $$hide_limited is ** \fIset\fP, this option will have no effect. */ @@ -995,7 +995,7 @@ struct option_t MuttVars[] = { ** .pp ** Affects the behaviour of the \fIreply\fP function when replying to ** messages from mailing lists. When \fIset\fP, if the ``\fTReply-To:\fP'' header field is - ** set to the same value as the ``\fTTo:\fP'' header field, Mutt-ng assumes that the + ** set to the same value as the ``\fTTo:\fP'' header field, Madmutt assumes that the ** ``\fTReply-To:\fP'' header field was set by the mailing list to automate responses ** to the list, and will ignore this field. To direct a response to the ** mailing list when this option is set, use the \fIlist-reply\fP @@ -1007,21 +1007,21 @@ struct option_t MuttVars[] = { {"imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, "" }, /* ** .pp - ** This is a colon-delimited list of authentication methods Mutt-ng may - ** attempt to use to log in to an IMAP server, in the order Mutt-ng should + ** This is a colon-delimited list of authentication methods Madmutt may + ** attempt to use to log in to an IMAP server, in the order Madmutt should ** try them. Authentication methods are either ``\fTlogin\fP'' or the right ** side of an IMAP ``\fTAUTH=\fP'' capability string, e.g. ``\fTdigest-md5\fP'', ** ``\fTgssapi\fP'' or ``\fTcram-md5\fP''. This parameter is case-insensitive. ** .pp ** If this - ** parameter is \fIunset\fP (the default) Mutt-ng will try all available methods, + ** parameter is \fIunset\fP (the default) Madmutt will try all available methods, ** in order from most-secure to least-secure. ** .pp ** Example: \fTset imap_authenticators="gssapi:cram-md5:login"\fP ** .pp - ** \fBNote:\fP Mutt-ng will only fall back to other authentication methods if + ** \fBNote:\fP Madmutt will only fall back to other authentication methods if ** the previous methods are unavailable. If a method is available but - ** authentication fails, Mutt-ng will not connect to the IMAP server. + ** authentication fails, Madmutt will not connect to the IMAP server. */ { "imap_check_subscribed", DT_BOOL, R_NONE, OPTIMAPCHECKSUBSCRIBED, "no" }, /* @@ -1040,7 +1040,7 @@ struct option_t MuttVars[] = { {"imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, "" }, /* ** .pp - ** Mutt-ng requests these header fields in addition to the default headers + ** Madmutt requests these header fields in addition to the default headers ** (``DATE FROM SUBJECT TO CC MESSAGE-ID REFERENCES CONTENT-TYPE ** CONTENT-DESCRIPTION IN-REPLY-TO REPLY-TO LINES X-LABEL'') from IMAP ** servers before displaying the ``index'' menu. You may want to add more @@ -1058,9 +1058,9 @@ struct option_t MuttVars[] = { {"imap_keepalive", DT_NUM, R_NONE, UL &ImapKeepalive, "900" }, /* ** .pp - ** This variable specifies the maximum amount of time in seconds that Mutt-ng + ** This variable specifies the maximum amount of time in seconds that Madmutt ** will wait before polling open IMAP connections, to prevent the server - ** from closing them before Mutt-ng has finished with them. + ** from closing them before Madmutt has finished with them. ** .pp ** The default is ** well within the RFC-specified minimum amount of time (30 minutes) before @@ -1087,14 +1087,14 @@ struct option_t MuttVars[] = { {"imap_mail_check", DT_NUM, R_NONE, UL &ImapBuffyTimeout, "300" }, /* ** .pp - ** This variable configures how often (in seconds) Mutt-ng should look for + ** This variable configures how often (in seconds) Madmutt should look for ** new mail in IMAP folders. This is split from the ``$mail_check'' variable ** to generate less traffic and get more accurate information for local folders. */ {"imap_pass", DT_STR, R_NONE, UL &ImapPass, "" }, /* ** .pp - ** Specifies the password for your IMAP account. If \fIunset\fP, Mutt-ng will + ** Specifies the password for your IMAP account. If \fIunset\fP, Madmutt will ** prompt you for your password when you invoke the fetch-mail function. ** .pp ** \fBWarning\fP: you should only use this option when you are on a @@ -1104,16 +1104,16 @@ struct option_t MuttVars[] = { {"imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will not open new IMAP connections to check for new - ** mail. Mutt-ng will only check for new mail over existing IMAP + ** When \fIset\fP, Madmutt will not open new IMAP connections to check for new + ** mail. Madmutt will only check for new mail over existing IMAP ** connections. This is useful if you don't want to be prompted to - ** user/password pairs on Mutt-ng invocation, or if opening the connection + ** user/password pairs on Madmutt invocation, or if opening the connection ** is slow. */ {"imap_peek", DT_BOOL, R_NONE, OPTIMAPPEEK, "yes" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will avoid implicitly marking your mail as read whenever + ** If \fIset\fP, Madmutt will avoid implicitly marking your mail as read whenever ** you fetch a message from the server. This is generally a good thing, ** but can make closing an IMAP folder somewhat slower. This option ** exists to appease speed freaks. @@ -1121,13 +1121,13 @@ struct option_t MuttVars[] = { {"imap_reconnect", DT_QUAD, R_NONE, OPT_IMAPRECONNECT, "ask-yes" }, /* ** .pp - ** Controls whether or not Mutt-ng will try to reconnect to IMAP server when + ** Controls whether or not Madmutt will try to reconnect to IMAP server when ** the connection is lost. */ {"imap_servernoise", DT_BOOL, R_NONE, OPTIMAPSERVERNOISE, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will display warning messages from the IMAP + ** When \fIset\fP, Madmutt will display warning messages from the IMAP ** server as error messages. Since these messages are often ** harmless, or generated due to configuration problems on the ** server which are out of the users' hands, you may wish to suppress @@ -1144,9 +1144,9 @@ struct option_t MuttVars[] = { {"implicit_autoview", DT_BOOL, R_NONE, OPTIMPLICITAUTOVIEW, "no" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will look for a mailcap entry with the + ** If \fIset\fP, Madmutt will look for a mailcap entry with the ** ``\fTcopiousoutput\fP'' flag set for \fIevery\fP MIME attachment it doesn't have - ** an internal viewer defined for. If such an entry is found, Mutt-ng will + ** an internal viewer defined for. If such an entry is found, Madmutt will ** use the viewer defined in that entry to convert the body part to text ** form. */ @@ -1159,7 +1159,7 @@ struct option_t MuttVars[] = { {"include_onlyfirst", DT_BOOL, R_NONE, OPTINCLUDEONLYFIRST, "no" }, /* ** .pp - ** Controls whether or not Mutt-ng includes only the first attachment + ** Controls whether or not Madmutt includes only the first attachment ** of the message you are replying. */ {"indent_string", DT_STR, R_NONE, UL &Prefix, "> "}, @@ -1177,7 +1177,7 @@ struct option_t MuttVars[] = { ** .pp ** ``Format strings'' are similar to the strings used in the ``C'' ** function \fTprintf(3)\fP to format output (see the man page for more detail). - ** The following sequences are defined in Mutt-ng: + ** The following sequences are defined in Madmutt: ** .pp ** .dl ** .dt %a .dd address of the author @@ -1206,7 +1206,7 @@ struct option_t MuttVars[] = { ** .dt %M .dd number of hidden messages if the thread is collapsed. ** .dt %N .dd message score ** .dt %n .dd author's real name (or address if missing) - ** .dt %O .dd (_O_riginal save folder) Where Mutt-ng would formerly have + ** .dt %O .dd (_O_riginal save folder) Where Madmutt would formerly have ** stashed the message: list name or recipient name if no list ** .dt %s .dd subject of the message ** .dt %S .dd status of the message (N/D/d/!/r/\(as) @@ -1246,7 +1246,7 @@ struct option_t MuttVars[] = { ** ** .pp ** If \fIset\fP, specifies the program and arguments used to deliver news posted - ** by Mutt-ng. Otherwise, Mutt-ng posts article using current connection. + ** by Madmutt. Otherwise, Madmutt posts article using current connection. ** The following \fTprintf(3)\fP-style sequence is understood: ** .pp ** .ts @@ -1299,7 +1299,7 @@ struct option_t MuttVars[] = { {"mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, "5" }, /* ** .pp - ** This variable configures how often (in seconds) Mutt-ng should look for + ** This variable configures how often (in seconds) Madmutt should look for ** new mail. ** .pp ** \fBNote:\fP This does not apply to IMAP mailboxes, see $$imap_mail_check. @@ -1308,12 +1308,12 @@ struct option_t MuttVars[] = { /* ** .pp ** This variable specifies which files to consult when attempting to - ** display MIME bodies not directly supported by Mutt-ng. + ** display MIME bodies not directly supported by Madmutt. */ {"mailcap_sanitize", DT_BOOL, R_NONE, OPTMAILCAPSANITIZE, "yes" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will restrict possible characters in mailcap \fT%\fP expandos + ** If \fIset\fP, Madmutt will restrict possible characters in mailcap \fT%\fP expandos ** to a well-defined set of safe characters. This is the safe setting, ** but we are not sure it doesn't break some more advanced MIME stuff. ** .pp @@ -1341,7 +1341,7 @@ struct option_t MuttVars[] = { ** Availability: Header Cache ** ** .pp - ** Check for Maildir unaware programs other than Mutt-ng having modified maildir + ** Check for Maildir unaware programs other than Madmutt having modified maildir ** files when the header cache is in use. This incurs one \fTstat(2)\fP per ** message every time the folder is opened. */ @@ -1386,10 +1386,10 @@ struct option_t MuttVars[] = { {"mark_old", DT_BOOL, R_BOTH, OPTMARKOLD, "yes" }, /* ** .pp - ** Controls whether or not Mutt-ng marks \fInew\fP \fBunread\fP + ** Controls whether or not Madmutt marks \fInew\fP \fBunread\fP ** messages as \fIold\fP if you exit a mailbox without reading them. ** .pp - ** With this option \fIset\fP, the next time you start Mutt-ng, the messages + ** With this option \fIset\fP, the next time you start Madmutt, the messages ** will show up with an "O" next to them in the ``index'' menu, ** indicating that they are old. */ @@ -1535,7 +1535,7 @@ struct option_t MuttVars[] = { ** .pp ** This variable controls how message counts are printed when the sidebar ** is enabled. If this variable is \fIempty\fP (\fIand only if\fP), no numbers - ** will be printed \fIand\fP Mutt-ng won't frequently count mail (which + ** will be printed \fIand\fP Madmutt won't frequently count mail (which ** may be a great speedup esp. with mbox-style mailboxes.) ** .pp ** The following \fTprintf(3)\fP-like sequences are supported all of which @@ -1576,7 +1576,7 @@ struct option_t MuttVars[] = { {"metoo", DT_BOOL, R_NONE, OPTMETOO, "no" }, /* ** .pp - ** If \fIunset\fP, Mutt-ng will remove your address (see the ``alternates'' + ** If \fIunset\fP, Madmutt will remove your address (see the ``alternates'' ** command) from the list of recipients when replying to a message. */ {"menu_context", DT_NUM, R_NONE, UL &MenuContext, "0" }, @@ -1603,7 +1603,7 @@ struct option_t MuttVars[] = { {"meta_key", DT_BOOL, R_NONE, OPTMETAKEY, "no" }, /* ** .pp - ** If \fIset\fP, forces Mutt-ng to interpret keystrokes with the high bit (bit 8) + ** If \fIset\fP, forces Madmutt to interpret keystrokes with the high bit (bit 8) ** set as if the user had pressed the \fTESC\fP key and whatever key remains ** after having the high bit removed. For example, if the key pressed ** has an ASCII value of \fT0xf8\fP, then this is treated as if the user had @@ -1614,7 +1614,7 @@ struct option_t MuttVars[] = { {"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, "no" }, /* ** .pp - ** When \fIunset\fP, Mutt-ng will mimic mh's behaviour and rename deleted messages + ** When \fIunset\fP, Madmutt will mimic mh's behaviour and rename deleted messages ** to \fI,\fP in mh folders instead of really deleting ** them. If the variable is set, the message files will simply be ** deleted. @@ -1710,7 +1710,7 @@ struct option_t MuttVars[] = { {"move", DT_QUAD, R_NONE, OPT_MOVE, "ask-no" }, /* ** .pp - ** Controls whether or not Mutt-ng will move read messages + ** Controls whether or not Madmutt will move read messages ** from your spool mailbox to your ``$$mbox'' mailbox, or as a result of ** a ``$mbox-hook'' command. */ @@ -1725,7 +1725,7 @@ struct option_t MuttVars[] = { /* ** .pp ** This is the format for the ``local part'' of the \fTMessage-ID:\fP header - ** field generated by Mutt-ng. If this variable is empty, no \fTMessage-ID:\fP + ** field generated by Madmutt. If this variable is empty, no \fTMessage-ID:\fP ** headers will be generated. The '%' ** character marks that certain data will be added to the string, similar to ** \fTprintf(3)\fP. The following characters are allowed: @@ -1764,7 +1764,7 @@ struct option_t MuttVars[] = { ** Availability: NNTP ** ** .pp - ** This variable points to directory where Mutt-ng will cache news + ** This variable points to directory where Madmutt will cache news ** article headers. If \fIunset\fP, headers will not be saved at all ** and will be reloaded each time when you enter a newsgroup. ** .pp @@ -1837,7 +1837,7 @@ struct option_t MuttVars[] = { ** ** .pp ** Your login name on the NNTP server. If \fIunset\fP and the server requires - ** authentification, Mutt-ng will prompt you for your account name. + ** authentification, Madmutt will prompt you for your account name. */ {"nntp_pass", DT_STR, R_NONE, UL &NntpPass, ""}, /* @@ -1858,7 +1858,7 @@ struct option_t MuttVars[] = { ** ** .pp ** The time in seconds until any operations on a newsgroup except posting a new - ** article will cause a recheck for new news. If set to 0, Mutt-ng will + ** article will cause a recheck for new news. If set to 0, Madmutt will ** recheck on each operation in index (stepping, read article, etc.). */ {"nntp_reconnect", DT_QUAD, R_NONE, OPT_NNTPRECONNECT, "ask-yes" }, @@ -1867,7 +1867,7 @@ struct option_t MuttVars[] = { ** Availability: NNTP ** ** .pp - ** Controls whether or not Mutt-ng will try to reconnect to a newsserver when the + ** Controls whether or not Madmutt will try to reconnect to a newsserver when the ** was connection lost. */ #endif @@ -1889,7 +1889,7 @@ struct option_t MuttVars[] = { ** like to use. ** .pp ** Using an external pager may have some disadvantages: Additional - ** keystrokes are necessary because you can't call Mutt-ng functions + ** keystrokes are necessary because you can't call Madmutt functions ** directly from the pager, and screen resizes cause lines longer than ** the screen width to be badly formatted in the help menu. */ @@ -1898,7 +1898,7 @@ struct option_t MuttVars[] = { ** .pp ** This variable controls the number of lines of context that are given ** when displaying the next or previous page in the internal pager. By - ** default, Mutt-ng will display the line after the last one on the screen + ** default, Madmutt will display the line after the last one on the screen ** at the top of the next page (0 lines of context). */ {"pager_format", DT_STR, R_PAGER, UL &PagerFmt, "-%Z- %C/%m: %-20.20n %s"}, @@ -1934,7 +1934,7 @@ struct option_t MuttVars[] = { {"crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, "no" }, /* ** .pp - ** Setting this variable will cause Mutt-ng to always attempt to + ** Setting this variable will cause Madmutt to always attempt to ** cryptographically sign outgoing messages. This can be overridden ** by use of the \fIpgp-menu\fP, when signing is not required or ** encryption is requested as well. If ``$$smime_is_default'' is \fIset\fP, @@ -1945,7 +1945,7 @@ struct option_t MuttVars[] = { {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, "no" }, /* ** .pp - ** Setting this variable will cause Mutt-ng to always attempt to PGP + ** Setting this variable will cause Madmutt to always attempt to PGP ** encrypt outgoing messages. This is probably only useful in ** connection to the \fIsend-hook\fP command. It can be overridden ** by use of the \fIpgp-menu\fP, when encryption is not required or @@ -1957,7 +1957,7 @@ struct option_t MuttVars[] = { {"pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, "yes" }, /* ** .pp - ** Setting this variable will cause Mutt-ng to ignore OpenPGP subkeys. Instead, + ** Setting this variable will cause Madmutt to ignore OpenPGP subkeys. Instead, ** the principal key will inherit the subkeys' capabilities. \fIUnset\fP this ** if you want to play interesting key selection games. ** (PGP only) @@ -1985,14 +1985,14 @@ struct option_t MuttVars[] = { ** which are encrypted. This makes sense in combination with ** ``$$crypt_replyencrypt'', because it allows you to sign all ** messages which are automatically encrypted. This works around - ** the problem noted in ``$$crypt_replysign'', that Mutt-ng is not able + ** the problem noted in ``$$crypt_replysign'', that Madmutt is not able ** to find out whether an encrypted message is also signed. ** (Crypto only) */ {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, "yes" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will include a time stamp in the lines surrounding + ** If \fIset\fP, Madmutt will include a time stamp in the lines surrounding ** PGP or S/MIME output, so spoofing such lines is more difficult. ** If you are using colors to mark these lines, and rely on these, ** you may \fIunset\fP this setting. @@ -2001,7 +2001,7 @@ struct option_t MuttVars[] = { {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, "no" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will use a possibly-running gpg-agent process. + ** If \fIset\fP, Madmutt will use a possibly-running gpg-agent process. ** (PGP only) */ {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, "yes" }, @@ -2015,10 +2015,10 @@ struct option_t MuttVars[] = { {"smime_is_default", DT_BOOL, R_NONE, OPTSMIMEISDEFAULT, "no" }, /* ** .pp - ** The default behaviour of Mutt-ng is to use PGP on all auto-sign/encryption + ** The default behaviour of Madmutt is to use PGP on all auto-sign/encryption ** operations. To override and to use OpenSSL instead this must be \fIset\fP. ** .pp - ** However, this has no effect while replying, since Mutt-ng will automatically + ** However, this has no effect while replying, since Madmutt will automatically ** select the same application that was used to sign/encrypt the original ** message. ** .pp @@ -2036,8 +2036,8 @@ struct option_t MuttVars[] = { {"smime_decrypt_use_default_key", DT_BOOL, R_NONE, OPTSDEFAULTDECRYPTKEY, "yes" }, /* ** .pp - ** If \fIset\fP (default) this tells Mutt-ng to use the default key for decryption. Otherwise, - ** if manage multiple certificate-key-pairs, Mutt-ng will try to use the mailbox-address + ** If \fIset\fP (default) this tells Madmutt to use the default key for decryption. Otherwise, + ** if manage multiple certificate-key-pairs, Madmutt will try to use the mailbox-address ** to determine the key to use. It will ask you to supply a key, if it can't find one. ** (S/MIME only) */ @@ -2074,7 +2074,7 @@ struct option_t MuttVars[] = { {"pgp_check_exit", DT_BOOL, R_NONE, OPTPGPCHECKEXIT, "yes" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will check the exit code of the PGP subprocess when + ** If \fIset\fP, Madmutt will check the exit code of the PGP subprocess when ** signing or encrypting. A non-zero exit code means that the ** subprocess failed. ** (PGP only) @@ -2099,13 +2099,13 @@ struct option_t MuttVars[] = { {"pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, "no" }, /* ** .pp - ** This option controls whether Mutt-ng generates old-style inline + ** This option controls whether Madmutt generates old-style inline ** (traditional) PGP encrypted or signed messages under certain ** circumstances. This can be overridden by use of the \fIpgp-menu\fP, ** when inline is not required. ** .pp - ** Note that Mutt-ng might automatically use PGP/MIME for messages - ** which consist of more than a single MIME part. Mutt-ng can be + ** Note that Madmutt might automatically use PGP/MIME for messages + ** which consist of more than a single MIME part. Madmutt can be ** configured to ask before sending PGP/MIME messages when inline ** (traditional) would not work. ** See also: ``$$pgp_mime_auto''. @@ -2117,16 +2117,16 @@ struct option_t MuttVars[] = { {"pgp_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, "no" }, /* ** .pp - ** Setting this variable will cause Mutt-ng to always attempt to + ** Setting this variable will cause Madmutt to always attempt to ** create an inline (traditional) message when replying to a ** message which is PGP encrypted/signed inline. This can be ** overridden by use of the \fIpgp-menu\fP, when inline is not ** required. This option does not automatically detect if the - ** (replied-to) message is inline; instead it relies on Mutt-ng + ** (replied-to) message is inline; instead it relies on Madmutt ** internals for previously checked/flagged messages. ** .pp - ** Note that Mutt-ng might automatically use PGP/MIME for messages - ** which consist of more than a single MIME part. Mutt-ng can be + ** Note that Madmutt might automatically use PGP/MIME for messages + ** which consist of more than a single MIME part. Madmutt can be ** configured to ask before sending PGP/MIME messages when inline ** (traditional) would not work. ** See also: ``$$pgp_mime_auto''. @@ -2139,7 +2139,7 @@ struct option_t MuttVars[] = { {"pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, "yes" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will display non-usable keys on the PGP key selection + ** If \fIset\fP, Madmutt will display non-usable keys on the PGP key selection ** menu. This includes keys which have been revoked, have expired, or ** have been marked as ``disabled'' by the user. ** (PGP only) @@ -2155,7 +2155,7 @@ struct option_t MuttVars[] = { {"pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, "yes" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will automatically encode PGP/MIME signed messages as + ** If \fIset\fP, Madmutt will automatically encode PGP/MIME signed messages as ** \fTquoted-printable\fP. Please note that unsetting this variable may ** lead to problems with non-verifyable PGP signatures, so only change ** this if you know what you are doing. @@ -2188,7 +2188,7 @@ struct option_t MuttVars[] = { {"pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, "ask-yes" }, /* ** .pp - ** This option controls whether Mutt-ng will prompt you for + ** This option controls whether Madmutt will prompt you for ** automatically sending a (signed/encrypted) message using ** PGP/MIME when inline (traditional) fails (for any reason). ** .pp @@ -2199,11 +2199,11 @@ struct option_t MuttVars[] = { {"pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, "no" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will automatically attempt to decrypt traditional PGP + ** If \fIset\fP, Madmutt will automatically attempt to decrypt traditional PGP ** messages whenever the user performs an operation which ordinarily would ** result in the contents of the message being operated on. For example, ** if the user displays a pgp-traditional message which has not been manually - ** checked with the check-traditional-pgp function, Mutt-ng will automatically + ** checked with the check-traditional-pgp function, Madmutt will automatically ** check the message for traditional pgp. */ @@ -2236,7 +2236,7 @@ struct option_t MuttVars[] = { {"pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, "" }, /* ** .pp - ** This command is invoked whenever Mutt-ng will need public key information. + ** This command is invoked whenever Madmutt will need public key information. ** \fT%r\fP is the only \fTprintf(3)\fP-like sequence used with this format. ** (PGP only) */ @@ -2308,7 +2308,7 @@ struct option_t MuttVars[] = { ** \fTgpg --list-keys --with-colons\fP. ** .pp ** This format is also generated by the \fTpgpring\fP utility which comes - ** with Mutt-ng. + ** with Madmutt. ** (PGP only) */ {"pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, "" }, @@ -2319,7 +2319,7 @@ struct option_t MuttVars[] = { ** \fTgpg --list-keys --with-colons\fP. ** .pp ** This format is also generated by the \fTpgpring\fP utility which comes - ** with Mutt-ng. + ** with Madmutt. ** (PGP only) */ {"forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, "yes" }, @@ -2351,7 +2351,7 @@ struct option_t MuttVars[] = { {"smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, "" }, /* ** .pp - ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle + ** Since there is no pubring/secring as with PGP, Madmutt has to handle ** storage ad retrieval of keys/certs by itself. This is very basic right now, ** and stores keys and certificates in two different directories, both ** named as the hash-value retrieved from OpenSSL. There is an index file @@ -2369,7 +2369,7 @@ struct option_t MuttVars[] = { {"smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, "" }, /* ** .pp - ** Since there is no pubring/secring as with PGP, Mutt-ng has to handle + ** Since there is no pubring/secring as with PGP, Madmutt has to handle ** storage and retrieval of keys by itself. This is very basic right ** now, and keys and certificates are stored in two different ** directories, both named as the hash-value retrieved from @@ -2489,7 +2489,7 @@ struct option_t MuttVars[] = { ** ** .pp ** Defines the username to use with SMTP AUTH. Setting this variable will - ** cause Mutt-ng to attempt to use SMTP AUTH when sending. + ** cause Madmutt to attempt to use SMTP AUTH when sending. */ {"smtp_auth_password", DT_SYN, R_NONE, UL "smtp_pass", 0}, {"smtp_pass", DT_STR, R_NONE, UL &SmtpAuthPass, "" }, @@ -2542,7 +2542,7 @@ struct option_t MuttVars[] = { ** will try to start TLS and continue without TLS in case of an error. ** **.pp - ** Muttng still needs to have SSL support enabled in order to use it. + ** Madmutt still needs to have SSL support enabled in order to use it. */ #endif #if defined(USE_SSL) || defined(USE_GNUTLS) @@ -2560,7 +2560,7 @@ struct option_t MuttVars[] = { {"ssl_force_tls", DT_BOOL, R_NONE, OPTSSLFORCETLS, "no" }, /* ** .pp - ** If this variable is \fIset\fP, Mutt-ng will require that all connections + ** If this variable is \fIset\fP, Madmutt will require that all connections ** to remote servers be encrypted. Furthermore it will attempt to ** negotiate TLS even if the server does not advertise the capability, ** since it would otherwise have to abort the connection anyway. This @@ -2572,8 +2572,8 @@ struct option_t MuttVars[] = { ** Availability: SSL or GNUTLS ** ** .pp - ** If \fIset\fP (the default), Mutt-ng will attempt to use STARTTLS on servers - ** advertising the capability. When \fIunset\fP, Mutt-ng will not attempt to + ** If \fIset\fP (the default), Madmutt will attempt to use STARTTLS on servers + ** advertising the capability. When \fIunset\fP, Madmutt will not attempt to ** use STARTTLS regardless of the server's capabilities. */ {"certificate_file", DT_PATH, R_NONE, UL &SslCertFile, "~/.mutt_certificates"}, @@ -2601,7 +2601,7 @@ struct option_t MuttVars[] = { ** Availability: SSL ** ** .pp - ** If set to \fIyes\fP, Mutt-ng will use CA certificates in the + ** If set to \fIyes\fP, Madmutt will use CA certificates in the ** system-wide certificate store when checking if server certificate ** is signed by a trusted CA. */ @@ -2670,8 +2670,8 @@ struct option_t MuttVars[] = { ** Used in connection with the \fIpipe-message\fP command and the ``tag- ** prefix'' or ``tag-prefix-cond'' operators. ** If this variable is \fIunset\fP, when piping a list of - ** tagged messages Mutt-ng will concatenate the messages and will pipe them - ** as a single folder. When \fIset\fP, Mutt-ng will pipe the messages one by one. + ** tagged messages Madmutt will concatenate the messages and will pipe them + ** as a single folder. When \fIset\fP, Madmutt will pipe the messages one by one. ** In both cases the messages are piped in the current sorted order, ** and the ``$$pipe_sep'' separator is added after each message. */ @@ -2679,7 +2679,7 @@ struct option_t MuttVars[] = { /* ** .pp ** Used in connection with the \fIpipe-message\fP command. When \fIunset\fP, - ** Mutt-ng will pipe the messages without any preprocessing. When \fIset\fP, Mutt-ng + ** Madmutt will pipe the messages without any preprocessing. When \fIset\fP, Madmutt ** will weed headers and will attempt to PGP/MIME decode the messages ** first. */ @@ -2692,13 +2692,13 @@ struct option_t MuttVars[] = { {"pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, "" }, /* ** .pp - ** This is a colon-delimited list of authentication methods Mutt-ng may - ** attempt to use to log in to an POP server, in the order Mutt-ng should + ** This is a colon-delimited list of authentication methods Madmutt may + ** attempt to use to log in to an POP server, in the order Madmutt should ** try them. Authentication methods are either ``\fTuser\fP'', ``\fTapop\fP'' ** or any SASL mechanism, eg ``\fTdigest-md5\fP'', ``\fTgssapi\fP'' or ``\fTcram-md5\fP''. ** .pp ** This parameter is case-insensitive. If this parameter is \fIunset\fP - ** (the default) Mutt-ng will try all available methods, in order from + ** (the default) Madmutt will try all available methods, in order from ** most-secure to least-secure. ** .pp ** Example: \fTset pop_authenticators="digest-md5:apop:user"\fP @@ -2706,23 +2706,23 @@ struct option_t MuttVars[] = { {"pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, "yes" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will try all available methods. When \fIunset\fP, Mutt-ng will + ** If \fIset\fP, Madmutt will try all available methods. When \fIunset\fP, Madmutt will ** only fall back to other authentication methods if the previous ** methods are unavailable. If a method is available but authentication - ** fails, Mutt-ng will not connect to the POP server. + ** fails, Madmutt will not connect to the POP server. */ {"pop_checkinterval", DT_SYN, R_NONE, UL "pop_mail_check", 0}, {"pop_mail_check", DT_NUM, R_NONE, UL &PopCheckTimeout, "60" }, /* ** .pp - ** This variable configures how often (in seconds) Mutt-ng should look for + ** This variable configures how often (in seconds) Madmutt should look for ** new mail. */ {"pop_delete", DT_QUAD, R_NONE, OPT_POPDELETE, "ask-no" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will delete successfully downloaded messages from the POP - ** server when using the ``fetch-mail'' function. When \fIunset\fP, Mutt-ng will + ** If \fIset\fP, Madmutt will delete successfully downloaded messages from the POP + ** server when using the ``fetch-mail'' function. When \fIunset\fP, Madmutt will ** download messages but also leave them on the POP server. */ {"pop_host", DT_STR, R_NONE, UL &PopHost, ""}, @@ -2740,14 +2740,14 @@ struct option_t MuttVars[] = { {"pop_last", DT_BOOL, R_NONE, OPTPOPLAST, "no" }, /* ** .pp - ** If this variable is \fIset\fP, Mutt-ng will try to use the ``\fTLAST\fP'' POP command + ** If this variable is \fIset\fP, Madmutt will try to use the ``\fTLAST\fP'' POP command ** for retrieving only unread messages from the POP server when using ** the ``fetch-mail'' function. */ {"pop_reconnect", DT_QUAD, R_NONE, OPT_POPRECONNECT, "ask-yes" }, /* ** .pp - ** Controls whether or not Mutt-ng will try to reconnect to a POP server if the + ** Controls whether or not Madmutt will try to reconnect to a POP server if the ** connection is lost. */ {"pop_user", DT_STR, R_NONE, UL &PopUser, "" }, @@ -2760,7 +2760,7 @@ struct option_t MuttVars[] = { {"pop_pass", DT_STR, R_NONE, UL &PopPass, ""}, /* ** .pp - ** Specifies the password for your POP account. If \fIunset\fP, Mutt-ng will + ** Specifies the password for your POP account. If \fIunset\fP, Madmutt will ** prompt you for your password when you open POP mailbox. ** .pp ** \fBNote:\fP Storing passwords in a configuration file @@ -2770,7 +2770,7 @@ struct option_t MuttVars[] = { {"post_indent_string", DT_STR, R_NONE, UL &PostIndentString, ""}, /* ** .pp - ** Similar to the ``$$attribution'' variable, Mutt-ng will append this + ** Similar to the ``$$attribution'' variable, Madmutt will append this ** string after the inclusion of a message which is being replied to. */ #ifdef USE_NNTP @@ -2780,7 +2780,7 @@ struct option_t MuttVars[] = { ** Availability: NNTP ** ** .pp - ** If set to \fIyes\fP, Mutt-ng will post articles to newsgroup that have + ** If set to \fIyes\fP, Madmutt will post articles to newsgroup that have ** not permissions to post (e.g. moderated). ** .pp ** \fBNote:\fP if the newsserver @@ -2797,18 +2797,18 @@ struct option_t MuttVars[] = { {"postponed", DT_PATH, R_NONE, UL &Postponed, "~/postponed"}, /* ** .pp - ** Mutt-ng allows you to indefinitely ``$postpone sending a message'' which - ** you are editing. When you choose to postpone a message, Mutt-ng saves it + ** Madmutt allows you to indefinitely ``$postpone sending a message'' which + ** you are editing. When you choose to postpone a message, Madmutt saves it ** in the mailbox specified by this variable. Also see the ``$$postpone'' ** variable. */ {"preconnect", DT_STR, R_NONE, UL &Preconnect, "" }, /* ** .pp - ** If \fIset\fP, a shell command to be executed if Mutt-ng fails to establish + ** If \fIset\fP, a shell command to be executed if Madmutt fails to establish ** a connection to the server. This is useful for setting up secure ** connections, e.g. with \fTssh(1)\fP. If the command returns a nonzero - ** status, Mutt-ng gives up opening the server. Example: + ** status, Madmutt gives up opening the server. Example: ** .pp ** \fTpreconnect="ssh -f -q -L 1234:mailhost.net:143 mailhost.net ** sleep 20 < /dev/null > /dev/null"\fP @@ -2822,7 +2822,7 @@ struct option_t MuttVars[] = { {"print", DT_QUAD, R_NONE, OPT_PRINT, "ask-no" }, /* ** .pp - ** Controls whether or not Mutt-ng really prints messages. + ** Controls whether or not Madmutt really prints messages. ** This is set to \fIask-no\fP by default, because some people ** accidentally hit ``p'' often. */ @@ -2859,14 +2859,14 @@ struct option_t MuttVars[] = { /* ** .pp ** If you use an \fIexternal\fP ``$$pager'', setting this variable will - ** cause Mutt-ng to prompt you for a command when the pager exits rather - ** than returning to the index menu. If \fIunset\fP, Mutt-ng will return to the + ** cause Madmutt to prompt you for a command when the pager exits rather + ** than returning to the index menu. If \fIunset\fP, Madmutt will return to the ** index menu when the external pager exits. */ {"query_command", DT_PATH, R_NONE, UL &QueryCmd, ""}, /* ** .pp - ** This specifies the command that Mutt-ng will use to make external address + ** This specifies the command that Madmutt will use to make external address ** queries. The string should contain a \fT%s\fP, which will be substituted ** with the query string the user types. See ``$query'' for more ** information. @@ -2875,7 +2875,7 @@ struct option_t MuttVars[] = { /* ** .pp ** This variable controls whether ``quit'' and ``exit'' actually quit - ** from Mutt-ng. If it set to \fIyes\fP, they do quit, if it is set to \fIno\fP, they + ** from Madmutt. If it set to \fIyes\fP, they do quit, if it is set to \fIno\fP, they ** have no effect, and if it is set to \fIask-yes\fP or \fIask-no\fP, you are ** prompted for confirmation when you try to quit. */ @@ -2906,9 +2906,9 @@ struct option_t MuttVars[] = { {"read_inc", DT_NUM, R_NONE, UL &ReadInc, "10" }, /* ** .pp - ** If set to a value greater than 0, Mutt-ng will display which message it + ** If set to a value greater than 0, Madmutt will display which message it ** is currently on when reading a mailbox. The message is printed after - ** \fIread_inc\fP messages have been read (e.g., if set to 25, Mutt-ng will + ** \fIread_inc\fP messages have been read (e.g., if set to 25, Madmutt will ** print a message when it reads message 25, and then again when it gets ** to message 50). This variable is meant to indicate progress when ** reading large mailboxes which may take some time. @@ -2937,7 +2937,7 @@ struct option_t MuttVars[] = { {"recall", DT_QUAD, R_NONE, OPT_RECALL, "ask-yes" }, /* ** .pp - ** Controls whether or not Mutt-ng recalls postponed messages + ** Controls whether or not Madmutt recalls postponed messages ** when composing a new message. Also see ``$$postponed''. ** .pp ** Setting this variable to \fIyes\fP is not generally useful, and thus not @@ -2964,14 +2964,14 @@ struct option_t MuttVars[] = { {"reply_self", DT_BOOL, R_NONE, OPTREPLYSELF, "no" }, /* ** .pp - ** If \fIunset\fP and you are replying to a message sent by you, Mutt-ng will + ** If \fIunset\fP and you are replying to a message sent by you, Madmutt will ** assume that you want to reply to the recipients of that message rather ** than to yourself. */ {"reply_to", DT_QUAD, R_NONE, OPT_REPLYTO, "ask-yes" }, /* ** .pp - ** If \fIset\fP, when replying to a message, Mutt-ng will use the address listed + ** If \fIset\fP, when replying to a message, Madmutt will use the address listed ** in the ``\fTReply-To:\fP'' header field as the recipient of the reply. If \fIunset\fP, ** it will use the address in the ``\fTFrom:\fP'' header field instead. ** .pp @@ -2990,7 +2990,7 @@ struct option_t MuttVars[] = { {"reverse_alias", DT_BOOL, R_BOTH, OPTREVALIAS, "no" }, /* ** .pp - ** This variable controls whether or not Mutt-ng will display the ``personal'' + ** This variable controls whether or not Madmutt will display the ``personal'' ** name from your aliases in the index menu if it finds an alias that ** matches the message's sender. For example, if you have the following ** alias: @@ -3021,15 +3021,15 @@ struct option_t MuttVars[] = { /* ** .pp ** This variable fine-tunes the behaviour of the $reverse_name feature. - ** When it is \fIset\fP, Mutt-ng will use the address from incoming messages as-is, - ** possibly including eventual real names. When it is \fIunset\fP, Mutt-ng will + ** When it is \fIset\fP, Madmutt will use the address from incoming messages as-is, + ** possibly including eventual real names. When it is \fIunset\fP, Madmutt will ** override any such real names with the setting of the $realname variable. */ {"rfc2047_parameters", DT_BOOL, R_NONE, OPTRFC2047PARAMS, "no" }, /* ** .pp - ** When this variable is \fIset\fP, Mutt-ng will decode RFC-2047-encoded MIME - ** parameters. You want to set this variable when Mutt-ng suggests you + ** When this variable is \fIset\fP, Madmutt will decode RFC-2047-encoded MIME + ** parameters. You want to set this variable when Madmutt suggests you ** to save attachments to files named like this: ** .pp ** \fT=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=\fP @@ -3042,13 +3042,13 @@ struct option_t MuttVars[] = { ** wild. ** .pp ** Also note that setting this parameter will \fInot\fP have the effect - ** that Mutt-ng \fIgenerates\fP this kind of encoding. Instead, Mutt-ng will + ** that Madmutt \fIgenerates\fP this kind of encoding. Instead, Madmutt will ** unconditionally use the encoding specified in RFC 2231. */ {"save_address", DT_BOOL, R_NONE, OPTSAVEADDRESS, "no" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will take the sender's full address when choosing a + ** If \fIset\fP, Madmutt will take the sender's full address when choosing a ** default folder for saving a mail. If ``$$save_name'' or ``$$force_name'' ** is \fIset\fP too, the selection of the fcc folder will be changed as well. */ @@ -3059,7 +3059,7 @@ struct option_t MuttVars[] = { ** when closed (the exception is ``$$spoolfile'' which is never removed). ** If \fIset\fP, mailboxes are never removed. ** .pp - ** \fBNote:\fP This only applies to mbox and MMDF folders, Mutt-ng does not + ** \fBNote:\fP This only applies to mbox and MMDF folders, Madmutt does not ** delete MH and Maildir directories. */ {"save_name", DT_BOOL, R_NONE, OPTSAVENAME, "no" }, @@ -3087,8 +3087,8 @@ struct option_t MuttVars[] = { /* ** .pp ** Messages which have been assigned a score equal to or lower than the value - ** of this variable are automatically marked for deletion by Mutt-ng. Since - ** Mutt-ng scores are always greater than or equal to zero, the default setting + ** of this variable are automatically marked for deletion by Madmutt. Since + ** Madmutt scores are always greater than or equal to zero, the default setting ** of this variable will never mark a message for deletion. */ {"score_threshold_flag", DT_NUM, R_NONE, UL &ScoreThresholdFlag, "9999" }, @@ -3101,14 +3101,14 @@ struct option_t MuttVars[] = { /* ** .pp ** Messages which have been assigned a score equal to or lower than the value - ** of this variable are automatically marked as read by Mutt-ng. Since - ** Mutt-ng scores are always greater than or equal to zero, the default setting + ** of this variable are automatically marked as read by Madmutt. Since + ** Madmutt scores are always greater than or equal to zero, the default setting ** of this variable will never mark a message read. */ {"send_charset", DT_STR, R_NONE, UL &SendCharset, "us-ascii:iso-8859-1:utf-8"}, /* ** .pp - ** A list of character sets for outgoing messages. Mutt-ng will use the + ** A list of character sets for outgoing messages. Madmutt will use the ** first character set into which the text can be converted exactly. ** If your ``$$charset'' is not \fTiso-8859-1\fP and recipients may not ** understand \fTUTF-8\fP, it is advisable to include in the list an @@ -3119,8 +3119,8 @@ struct option_t MuttVars[] = { {"sendmail", DT_PATH, R_NONE, UL &Sendmail, SENDMAIL " -oem -oi"}, /* ** .pp - ** Specifies the program and arguments used to deliver mail sent by Mutt-ng. - ** Mutt-ng expects that the specified program interprets additional + ** Specifies the program and arguments used to deliver mail sent by Madmutt. + ** Madmutt expects that the specified program interprets additional ** arguments as recipient addresses. */ {"sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, "0" }, @@ -3129,7 +3129,7 @@ struct option_t MuttVars[] = { ** Specifies the number of seconds to wait for the ``$$sendmail'' process ** to finish before giving up and putting delivery in the background. ** .pp - ** Mutt-ng interprets the value of this variable as follows: + ** Madmutt interprets the value of this variable as follows: ** .dl ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing ** .dt 0 .dd wait forever for sendmail to finish @@ -3188,7 +3188,7 @@ struct option_t MuttVars[] = { ** contains just your name. The reason for this is because many software ** packages use ``\fT-- \n\fP'' to detect your signature. ** .pp - ** For example, Mutt-ng has the ability to highlight + ** For example, Madmutt has the ability to highlight ** the signature in a different color in the builtin pager. */ {"sig_on_top", DT_BOOL, R_NONE, OPTSIGONTOP, "no" }, @@ -3220,11 +3220,11 @@ struct option_t MuttVars[] = { {"simple_search", DT_STR, R_NONE, UL &SimpleSearch, "~f %s | ~s %s"}, /* ** .pp - ** Specifies how Mutt-ng should expand a simple search into a real search + ** Specifies how Madmutt should expand a simple search into a real search ** pattern. A simple search is one that does not contain any of the ~ ** operators. See ``$patterns'' for more information on search patterns. ** .pp - ** For example, if you simply type ``joe'' at a search or limit prompt, Mutt-ng + ** For example, if you simply type ``joe'' at a search or limit prompt, Madmutt ** will automatically expand it to the value specified by this variable. ** For the default value it would be: ** .pp @@ -3293,7 +3293,7 @@ struct option_t MuttVars[] = { ** When sorting by threads, this variable controls how threads are sorted ** in relation to other threads, and how the branches of the thread trees ** are sorted. This can be set to any value that ``$$sort'' can, except - ** threads (in that case, Mutt-ng will just use date-sent). You can also + ** threads (in that case, Madmutt will just use date-sent). You can also ** specify the ``last-'' prefix in addition to ``reverse-'' prefix, but last- ** must come after reverse-. The last- prefix causes messages to be ** sorted against its siblings by which has the last descendant, using @@ -3328,11 +3328,11 @@ struct option_t MuttVars[] = { ** .pp ** This variable is only useful when sorting by threads with ** ``$$strict_threads'' \fIunset\fP. In that case, it changes the heuristic - ** Mutt-ng uses to thread messages by subject. With $$sort_re \fIset\fP, - ** Mutt-ng will only attach a message as the child of another message by + ** Madmutt uses to thread messages by subject. With $$sort_re \fIset\fP, + ** Madmutt will only attach a message as the child of another message by ** subject if the subject of the child message starts with a substring ** matching the setting of ``$$reply_regexp''. With $$sort_re \fIunset\fP, - ** Mutt-ng will attach the message whether or not this is the case, + ** Madmutt will attach the message whether or not this is the case, ** as long as the non-``$$reply_regexp'' parts of both messages are identical. */ {"spam_separator", DT_STR, R_NONE, UL &SpamSep, ","}, @@ -3347,8 +3347,8 @@ struct option_t MuttVars[] = { {"spoolfile", DT_PATH, R_NONE, UL &Spoolfile, "" }, /* ** .pp - ** If your spool mailbox is in a non-default place where Mutt-ng cannot find - ** it, you can specify its location with this variable. Mutt-ng will + ** If your spool mailbox is in a non-default place where Madmutt cannot find + ** it, you can specify its location with this variable. Madmutt will ** automatically set this variable to the value of the environment ** variable $$$MAIL if it is not set. */ @@ -3366,7 +3366,7 @@ struct option_t MuttVars[] = { ** opened in attach-message mode (Certain operations like composing ** a new mail, replying, forwarding, etc. are not permitted in this mode). */ - {"status_format", DT_STR, R_BOTH, UL &Status, "-%r-Mutt-ng: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---"}, + {"status_format", DT_STR, R_BOTH, UL &Status, "-%r-Madmutt: %f [Msgs:%?M?%M/?%m%?n? New:%n?%?o? Old:%o?%?d? Del:%d?%?F? Flag:%F?%?t? Tag:%t?%?p? Post:%p?%?b? Inc:%b?%?l? %l?]---(%s/%S)-%>-(%P)---"}, /* ** .pp ** Controls the format of the status line displayed in the \fIindex\fP @@ -3395,7 +3395,7 @@ struct option_t MuttVars[] = { ** .dt %S .dd current aux sorting method ($$sort_aux) ** .dt %t .dd number of tagged messages * ** .dt %u .dd number of unread messages * - ** .dt %v .dd Mutt-ng version string + ** .dt %v .dd Madmutt version string ** .dt %V .dd currently active limit pattern, if any * ** .dt %>X .dd right justify the rest of the string and pad with "X" ** .dt %|X .dd pad to the end of the line with "X" @@ -3435,7 +3435,7 @@ struct option_t MuttVars[] = { ** .pp ** \fT%_h\fP ** .pp - ** If you prefix the sequence character with a colon (\fT:\fP) character, Mutt-ng + ** If you prefix the sequence character with a colon (\fT:\fP) character, Madmutt ** will replace any dots in the expansion by underscores. This might be helpful ** with IMAP folders that don't like dots in folder names. */ @@ -3454,7 +3454,7 @@ struct option_t MuttVars[] = { ** if ``$$edit_headers'' is unset. ** ** .pp - ** If this variable is \fIset\fP, Mutt-ng is strict and allows anything to be + ** If this variable is \fIset\fP, Madmutt is strict and allows anything to be ** changed. If it's \fIunset\fP, all headers given will be prefixed with ** ``X-Mailto-'' and the message including headers will be shown in the editor ** regardless of what ``$$edit_headers'' is set to. @@ -3487,14 +3487,14 @@ struct option_t MuttVars[] = { {"strip_was", DT_BOOL, R_NONE, OPTSTRIPWAS, "no" }, /** ** .pp - ** When \fIset\fP, Mutt-ng will remove the trailing part of the ``\fTSubject:\fP'' + ** When \fIset\fP, Madmutt will remove the trailing part of the ``\fTSubject:\fP'' ** line which matches $$strip_was_regex when replying. This is useful to ** properly react on subject changes and reduce ``subject noise.'' (esp. in Usenet) **/ {"strip_was_regex", DT_RX, R_NONE, UL &StripWasRegexp, "\\([Ww][Aa][RrSs]: .*\\)[ ]*$"}, /** ** .pp - ** When non-empty and $$strip_was is \fIset\fP, Mutt-ng will remove this + ** When non-empty and $$strip_was is \fIset\fP, Madmutt will remove this ** trailing part of the ``Subject'' line when replying if it won't be empty ** afterwards. **/ @@ -3508,14 +3508,14 @@ struct option_t MuttVars[] = { {"suspend", DT_BOOL, R_NONE, OPTSUSPEND, "yes" }, /* ** .pp - ** When \fIunset\fP, Mutt-ng won't stop when the user presses the terminal's - ** \fIsusp\fP key, usually \fTCTRL+Z\fP. This is useful if you run Mutt-ng + ** When \fIunset\fP, Madmutt won't stop when the user presses the terminal's + ** \fIsusp\fP key, usually \fTCTRL+Z\fP. This is useful if you run Madmutt ** inside an xterm using a command like ``\fTxterm -e madmutt\fP.'' */ {"text_flowed", DT_BOOL, R_NONE, OPTTEXTFLOWED, "no" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will generate \fTtext/plain; format=flowed\fP attachments. + ** When \fIset\fP, Madmutt will generate \fTtext/plain; format=flowed\fP attachments. ** This format is easier to handle for some mailing software, and generally ** just looks like ordinary text. To actually make use of this format's ** features, you'll need support in your editor. @@ -3525,7 +3525,7 @@ struct option_t MuttVars[] = { {"thread_received", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTTHREADRECEIVED, "no" }, /* ** .pp - ** When \fIset\fP, Mutt-ng uses the date received rather than the date sent + ** When \fIset\fP, Madmutt uses the date received rather than the date sent ** to thread messages by subject. */ {"thorough_search", DT_BOOL, R_NONE, OPTTHOROUGHSRC, "no" }, @@ -3545,15 +3545,15 @@ struct option_t MuttVars[] = { {"timeout", DT_NUM, R_NONE, UL &Timeout, "600" }, /* ** .pp - ** This variable controls the \fInumber of seconds\fP Mutt-ng will wait + ** This variable controls the \fInumber of seconds\fP Madmutt will wait ** for a key to be pressed in the main menu before timing out and - ** checking for new mail. A value of zero or less will cause Mutt-ng + ** checking for new mail. A value of zero or less will cause Madmutt ** to never time out. */ {"tmpdir", DT_PATH, R_NONE, UL &Tempdir, "" }, /* ** .pp - ** This variable allows you to specify where Mutt-ng will place its + ** This variable allows you to specify where Madmutt will place its ** temporary files needed for displaying and composing messages. If ** this variable is not set, the environment variable \fT$$$TMPDIR\fP is ** used. If \fT$$$TMPDIR\fP is not set then "\fT/tmp\fP" is used. @@ -3585,7 +3585,7 @@ struct option_t MuttVars[] = { {"tunnel", DT_STR, R_NONE, UL &Tunnel, "" }, /* ** .pp - ** Setting this variable will cause Mutt-ng to open a pipe to a command + ** Setting this variable will cause Madmutt to open a pipe to a command ** instead of a raw socket. You may be able to use this to set up ** preauthenticated connections to your IMAP/POP3 server. Example: ** .pp @@ -3597,7 +3597,7 @@ struct option_t MuttVars[] = { {"umask", DT_NUM, R_NONE, UL &Umask, "0077" }, /* ** .pp - ** This sets the umask that will be used by Mutt-ng when creating all + ** This sets the umask that will be used by Madmutt when creating all ** kinds of files. If \fIunset\fP, the default value is \fT077\fP. */ {"use_8bitmime", DT_BOOL, R_NONE, OPTUSE8BITMIME, "no" }, @@ -3608,21 +3608,21 @@ struct option_t MuttVars[] = { ** 8.8.x) or in connection with the SMTP support via libESMTP. ** Otherwise you may not be able to send mail. ** .pp - ** When \fIset\fP, Mutt-ng will either invoke ``$$sendmail'' with the \fT-B8BITMIME\fP + ** When \fIset\fP, Madmutt will either invoke ``$$sendmail'' with the \fT-B8BITMIME\fP ** flag when sending 8-bit messages to enable ESMTP negotiation or tell ** libESMTP to do so. */ {"use_domain", DT_BOOL, R_NONE, OPTUSEDOMAIN, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will qualify all local addresses (ones without the + ** When \fIset\fP, Madmutt will qualify all local addresses (ones without the ** @host portion) with the value of ``$$hostname''. If \fIunset\fP, no ** addresses will be qualified. */ {"use_from", DT_BOOL, R_NONE, OPTUSEFROM, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will generate the ``\fTFrom:\fP'' header field when + ** When \fIset\fP, Madmutt will generate the ``\fTFrom:\fP'' header field when ** sending messages. If \fIunset\fP, no ``\fTFrom:\fP'' header field will be ** generated unless the user explicitly sets one using the ``$my_hdr'' ** command. @@ -3634,7 +3634,7 @@ struct option_t MuttVars[] = { ** Availability: IDN ** ** .pp - ** When \fIset\fP, Mutt-ng will show you international domain names decoded. + ** When \fIset\fP, Madmutt will show you international domain names decoded. ** .pp ** \fBNote:\fP You can use IDNs for addresses even if this is \fIunset\fP. ** This variable only affects decoding. @@ -3644,8 +3644,8 @@ struct option_t MuttVars[] = { {"use_ipv6", DT_BOOL, R_NONE, OPTUSEIPV6, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will look for IPv6 addresses of hosts it tries to - ** contact. If this option is \fIunset\fP, Mutt-ng will restrict itself to IPv4 addresses. + ** When \fIset\fP, Madmutt will look for IPv6 addresses of hosts it tries to + ** contact. If this option is \fIunset\fP, Madmutt will restrict itself to IPv4 addresses. ** Normally, the default should work. */ #endif /* HAVE_GETADDRINFO */ @@ -3653,14 +3653,14 @@ struct option_t MuttVars[] = { {"agent_string", DT_BOOL, R_NONE, OPTXMAILER, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will add a ``\fTUser-Agent:\fP'' header to outgoing - ** messages, indicating which version of Mutt-ng was used for composing + ** When \fIset\fP, Madmutt will add a ``\fTUser-Agent:\fP'' header to outgoing + ** messages, indicating which version of Madmutt was used for composing ** them. */ {"wait_key", DT_BOOL, R_NONE, OPTWAITKEY, "yes" }, /* ** .pp - ** Controls whether Mutt-ng will ask you to press a key after \fIshell- + ** Controls whether Madmutt will ask you to press a key after \fIshell- ** escape\fP, \fIpipe-message\fP, \fIpipe-entry\fP, \fIprint-message\fP, ** and \fIprint-entry\fP commands. ** .pp @@ -3668,13 +3668,13 @@ struct option_t MuttVars[] = { ** that the corresponding mailcap entry has a \fTneedsterminal\fP flag, ** and the external program is interactive. ** .pp - ** When \fIset\fP, Mutt-ng will always ask for a key. When \fIunset\fP, Mutt-ng will wait + ** When \fIset\fP, Madmutt will always ask for a key. When \fIunset\fP, Madmutt will wait ** for a key only if the external command returned a non-zero status. */ {"weed", DT_BOOL, R_NONE, OPTWEED, "yes" }, /* ** .pp - ** When \fIset\fP, Mutt-ng will weed headers when displaying, forwarding, + ** When \fIset\fP, Madmutt will weed headers when displaying, forwarding, ** printing, or replying to messages. */ {"wrap_search", DT_BOOL, R_NONE, OPTWRAPSEARCH, "yes" }, @@ -3689,7 +3689,7 @@ struct option_t MuttVars[] = { /* ** .pp ** Controls the size of the margin remaining at the right side of - ** the terminal when Mutt-ng's pager does smart wrapping. + ** the terminal when Madmutt's pager does smart wrapping. */ {"write_inc", DT_NUM, R_NONE, UL &WriteInc, "10" }, /* @@ -3703,7 +3703,7 @@ struct option_t MuttVars[] = { {"write_bcc", DT_BOOL, R_NONE, OPTWRITEBCC, "yes" }, /* ** .pp - ** Controls whether Mutt-ng writes out the Bcc header when preparing + ** Controls whether Madmutt writes out the Bcc header when preparing ** messages to be sent. Exim users may wish to \fIunset\fP this. */ {"xterm_icon", DT_STR, R_BOTH, UL &XtermIcon, "M%?n?AIL&ail?"}, @@ -3716,7 +3716,7 @@ struct option_t MuttVars[] = { {"xterm_set_titles", DT_BOOL, R_BOTH, OPTXTERMSETTITLES, "no" }, /* ** .pp - ** Controls whether Mutt-ng sets the xterm title bar and icon name + ** Controls whether Madmutt sets the xterm title bar and icon name ** (as long as you're in an appropriate terminal). The default must ** be \fIunset\fP to force in the validity checking. */ @@ -3724,8 +3724,8 @@ struct option_t MuttVars[] = { /* ** .pp ** If $$xterm_set_titles is \fIset\fP, this string will be used to - ** set the title when leaving Mutt-ng. For terminal-based programs, - ** there's no easy and portable way to read the current title so Mutt-ng + ** set the title when leaving Madmutt. For terminal-based programs, + ** there's no easy and portable way to read the current title so Madmutt ** cannot read it upon startup and restore it when exiting. ** ** .pp @@ -3734,7 +3734,7 @@ struct option_t MuttVars[] = { ** .pp ** \fTset xterm_leave = "`test x$$$DISPLAY != x && xprop -id $$$WINDOWID | grep WM_NAME | cut -d '"' -f 2`"\fP */ - {"xterm_title", DT_STR, R_BOTH, UL &XtermTitle, "Mutt-ng with %?m?%m messages&no messages?%?n? [%n New]?"}, + {"xterm_title", DT_STR, R_BOTH, UL &XtermTitle, "Madmutt with %?m?%m messages&no messages?%?n? [%n New]?"}, /* ** .pp ** Controls the format of the title bar of the xterm provided that @@ -3748,7 +3748,7 @@ struct option_t MuttVars[] = { ** Availability: NNTP ** ** .pp - ** If \fIset\fP, Mutt-ng will add a ``\fTX-Comment-To:\fP'' header field + ** If \fIset\fP, Madmutt will add a ``\fTX-Comment-To:\fP'' header field ** (that contains full name of the original article author) to articles that ** you followup to. */ diff --git a/lib/debug.c b/lib/debug.c index 6034ef9..4d4d393 100644 --- a/lib/debug.c +++ b/lib/debug.c @@ -49,7 +49,7 @@ void debug_start (const char* basedir) { t = time (NULL); setbuf (DebugFile, NULL); /* don't buffer the debugging output! */ fprintf (DebugFile, - "Mutt-ng %s started at %s\nDebugging at level %d\n\n", + "Madmutt %s started at %s\nDebugging at level %d\n\n", MUTT_VERSION, asctime (localtime (&t)), DebugLevel); } } diff --git a/main.c b/main.c index 30148f0..5b1c674 100644 --- a/main.c +++ b/main.c @@ -88,12 +88,12 @@ extern int optind; static const char *ReachingUs = N_("\ To contact the developers, please mail to .\n\ -To visit the Mutt-ng homepage go to http://www.muttng.org.\n\ +To visit the Madmutt homepage go to http://www.muttng.org.\n\ To report a bug, please use the fleang(1) utility.\n"); static const char *Notice = N_("\ Copyright (C) 1996-2002 Michael R. Elkins and others.\n\ -Mutt-ng comes with ABSOLUTELY NO WARRANTY; for details type `madmutt -vv'.\n\ +Madmutt comes with ABSOLUTELY NO WARRANTY; for details type `madmutt -vv'.\n\ Mutt is free software, and you are welcome to redistribute it\n\ under certain conditions; type `madmutt -vv' for details.\n"); @@ -172,11 +172,11 @@ options:\n\ -g \tspecify a newsserver (if compiled with NNTP)\n\ -G\t\tselect a newsgroup (if compiled with NNTP)\n\ -H \tspecify a draft file to read header and body from\n\ - -i \tspecify a file which Mutt-ng should include in the body"); + -i \tspecify a file which Madmutt should include in the body"); puts _("\ - -d \t specify debugging level of Mutt-ng\n\ + -d \t specify debugging level of Madmutt\n\ -m \tspecify a default mailbox type\n\ - -n\t\tcauses Mutt-ng not to read the system Muttngrc\n\ + -n\t\tcauses Madmutt not to read the system Madmuttrc\n\ -p\t\trecall a postponed message\n\ -Q \tquery a configuration variable\n\ -R\t\topen mailbox in read-only mode\n\ @@ -461,7 +461,7 @@ static void show_version (void) puts (_(ReachingUs)); - puts (_("MadMutt is based on Mutt-ng wich was based on Mutt before\n")); + puts (_("MadMutt is based on Madmutt wich was based on Mutt before\n")); exit (0); } diff --git a/mutt_menu.h b/mutt_menu.h index b6d00fe..96c2c53 100644 --- a/mutt_menu.h +++ b/mutt_menu.h @@ -26,7 +26,7 @@ #define REDRAW_SIGWINCH (1<<7) #define REDRAW_SIDEBAR (1<<8) -#define M_MODEFMT "-- Mutt-ng: %s" +#define M_MODEFMT "-- Madmutt: %s" typedef struct menu_t { char *title; /* the title of this menu */ diff --git a/muttlib.c b/muttlib.c index f4654df..7803776 100644 --- a/muttlib.c +++ b/muttlib.c @@ -1219,7 +1219,7 @@ const char *mutt_make_version (int full) if (full) snprintf (vstring, sizeof (vstring), - "Mutt-ng %s-r%s (based on Mutt 1.5.11)", + "Madmutt %s-r%s (based on Mutt 1.5.11)", MUTT_VERSION, MUTT_REVISION); else snprintf (vstring, sizeof (vstring), "mutt-ng/%s-r%s", diff --git a/status.c b/status.c index 6c613eb..51f22d6 100644 --- a/status.c +++ b/status.c @@ -55,7 +55,7 @@ static char *get_sort_str (char *buf, size_t buflen, int method) * %s = current sorting method ($sort) * %S = current aux sorting method ($sort_aux) * %t = # of tagged messages [option] - * %v = Mutt-ng version + * %v = Madmutt version * %V = currently active limit pattern [option] */ static const char *status_format_str (char *buf, size_t buflen, char op, const char *src, const char *prefix, -- 2.20.1