X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=init.h;h=ae59a4f69d2764fea76612c880f4d360324a70d2;hp=839675ca666b04652d46c0f157516ec5160926bb;hb=3a6261dd05abe2c2c3da12f6c337a397f612ceac;hpb=1d841e66b08bc422c8bfacd7a5db08e54e8c7dfe diff --git a/init.h b/init.h index 839675c..ae59a4f 100644 --- a/init.h +++ b/init.h @@ -11,16 +11,8 @@ * please see the file GPL in the top level source directory. */ -#ifdef _MAKEDOC -# include "config.h" -#else -# include "sort.h" -#endif - -#include "buffy.h" +#include "sort.h" #include "mutt.h" -#include "version.h" -#include "lib/debug.h" #ifndef _MAKEDOC #define DT_MASK 0x0f @@ -32,10 +24,6 @@ #define DT_SORT 6 /* sorting methods */ #define DT_RX 7 /* regular expressions */ #define DT_MAGIC 8 /* mailbox type */ -#define DT_SYN 9 /* synonym for another variable */ -#define DT_ADDR 10 /* e-mail address */ -#define DT_USER 11 /* user defined via $user_ */ -#define DT_SYS 12 /* pre-defined via $muttng_ */ #define DTYPE(x) ((x) & DT_MASK) @@ -55,71 +43,42 @@ #define R_NONE 0 #define R_INDEX (1<<0) #define R_PAGER (1<<1) +#define R_BOTH (R_INDEX|R_PAGER) + +/* TODO:MC: will go in the the thread module */ #define R_RESORT (1<<2) /* resort the mailbox */ #define R_RESORT_SUB (1<<3) /* resort subthreads */ #define R_RESORT_INIT (1<<4) /* resort from scratch */ #define R_TREE (1<<5) /* redraw the thread tree */ -#define R_BOTH (R_INDEX|R_PAGER) #define R_RESORT_BOTH (R_RESORT|R_RESORT_SUB) struct option_t { - char *option; + const char *option; short type; short flags; unsigned long data; - char* init; + const char *init; }; #define UL (unsigned long) #endif /* _MAKEDOC */ -#ifndef ISPELL -#define ISPELL "ispell" -#endif - /* build complete documentation */ #ifdef _MAKEDOC -# ifndef USE_IMAP -# define USE_IMAP -# endif -# ifndef MIXMASTER -# define MIXMASTER "mixmaster" -# endif -# ifndef USE_POP -# define USE_POP -# endif -# ifndef USE_SSL -# define USE_SSL -# endif -# ifndef USE_SOCKET -# define USE_SOCKET -# endif # ifndef USE_LIBESMTP # define USE_LIBESMTP # endif # ifndef USE_NNTP # define USE_NNTP # endif -# ifndef USE_GNUTLS -# define USE_GNUTLS -# endif -# ifndef USE_DOTLOCK -# define USE_DOTLOCK -# endif -# ifndef DL_STANDALONE -# define DL_STANDALONE -# endif # ifndef USE_HCACHE # define USE_HCACHE # endif # ifndef HAVE_LIBIDN # define HAVE_LIBIDN # endif -# ifndef HAVE_GETADDRINFO -# define HAVE_GETADDRINFO -# endif #endif struct option_t MuttVars[] = { @@ -158,29 +117,6 @@ struct option_t MuttVars[] = { ** check only happens after the \fIfirst\fP edit of the file). When set ** to \fIno\fP, composition will never be aborted. */ - {"alias_file", DT_PATH, R_NONE, UL &AliasFile, "~/.muttngrc"}, - /* - ** .pp - ** 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 - ** explicitly use the ``$source'' command for it to be executed. - */ - {"alias_format", DT_STR, R_NONE, UL &AliasFmt, "%4n %2f %t %-10a %r"}, - /* - ** .pp - ** Specifies the format of the data displayed for the ``alias'' menu. The - ** following \fTprintf(3)\fP-style sequences are available: - ** .pp - ** .dl - ** .dt %a .dd alias name - ** .dt %f .dd flags - currently, a "d" for an alias marked for deletion - ** .dt %n .dd index number - ** .dt %r .dd address which alias expands to - ** .dt %t .dd character which indicates if the alias is tagged for inclusion - ** .de - */ {"allow_8bit", DT_BOOL, R_NONE, OPTALLOW8BIT, "yes" }, /* ** .pp @@ -190,7 +126,7 @@ struct option_t MuttVars[] = { {"allow_ansi", DT_BOOL, R_NONE, OPTALLOWANSI, "no" }, /* ** .pp - ** Controls whether ANSI color codes in messages (and color tags in + ** Controls whether ANSI color codes in messages (and color tags in ** rich text messages) are to be interpreted. ** Messages containing these codes are rare, but if this option is set, ** their text will be colored accordingly. Note that this may override @@ -210,38 +146,21 @@ 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"}, - /* - ** .pp - ** This variable is a colon-separated list of character encoding - ** schemes for messages without character encoding indication. - ** Header field values and message body content without character encoding - ** indication would be assumed that they are written in one of this list. - ** By default, all the header fields and message body without any charset - ** indication are assumed to be in \fTus-ascii\fP. - ** .pp - ** For example, Japanese users might prefer this: - ** .pp - ** \fTset assumed_charset="iso-2022-jp:euc-jp:shift_jis:utf-8"\fP - ** .pp - ** However, only the first content is valid for the message body. - ** This variable is valid only if $$strict_mime is unset. - */ #ifdef USE_NNTP {"nntp_ask_followup_to", DT_BOOL, R_NONE, OPTASKFOLLOWUP, "no" }, /* @@ -249,7 +168,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" }, @@ -258,7 +177,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 @@ -279,10 +198,12 @@ struct option_t MuttVars[] = { ** .dt %m .dd major MIME type ** .dt %M .dd MIME subtype ** .dt %n .dd attachment number + ** .dt %Q .dd "Q", if MIME part qualifies for attachment counting ** .dt %s .dd size ** .dt %t .dd tagged flag ** .dt %T .dd graphic tree characters ** .dt %u .dd unlink (=to delete) flag + ** .dt %X .dd number of qualifying MIME parts in this part and its children ** .dt %>X .dd right justify the rest of the string and pad with character "X" ** .dt %|X .dd pad to the end of the line with character "X" ** .de @@ -290,7 +211,7 @@ struct option_t MuttVars[] = { {"attach_remind_regexp", DT_RX, R_NONE, UL &AttachRemindRegexp, "attach"}, /* ** .pp - ** If this variable is non-empty, muttng will scan a message's contents + ** If this variable is non-empty, madmutt will scan a message's contents ** before sending for this regular expression. If it is found, it will ** ask for what to do depending on the setting of $$abort_noattach. ** .pp @@ -307,10 +228,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:"}, /* @@ -322,7 +243,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. @@ -337,18 +258,6 @@ struct option_t MuttVars[] = { ** unset, you must first use the ``tag-prefix'' function (default: "\fT;\fP") to ** make the next function apply to all tagged messages. */ - {"beep", DT_BOOL, R_NONE, OPTBEEP, "yes" }, - /* - ** .pp - ** When this variable is \fIset\fP, Mutt-ng 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 - ** notifying you of new mail. This is independent of the setting of the - ** ``$$beep'' variable. - */ {"bounce", DT_QUAD, R_NONE, OPT_BOUNCE, "ask-yes" }, /* ** .pp @@ -360,7 +269,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. */ @@ -369,8 +278,8 @@ struct option_t MuttVars[] = { ** .pp ** When this variable is set, mutt will place the cursor at the beginning ** of the current line in menus, even when the arrow_cursor variable - ** is unset, making it easier for blind persons using Braille displays to - ** follow these menus. The option is disabled by default because many + ** is unset, making it easier for blind persons using Braille displays to + ** follow these menus. The option is disabled by default because many ** visual terminals don't permit making the cursor invisible. */ #ifdef USE_NNTP @@ -380,22 +289,17 @@ 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 - {"charset", DT_STR, R_NONE, UL &Charset, "" }, - /* - ** .pp - ** Character set your terminal uses to display and enter textual data. - */ {"check_new", DT_BOOL, R_NONE, OPTCHECKNEW, "yes" }, /* ** .pp ** \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 @@ -404,16 +308,16 @@ 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. */ {"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'' @@ -421,39 +325,39 @@ struct option_t MuttVars[] = { ** set of \fTprintf(3)\fP-like sequences: ** .pp ** .dl - ** .dt %a .dd total number of attachments + ** .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 + ** See the text describing the ``$$status_format'' option for more ** information on how to set ``$$compose_format''. */ {"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"}, /* @@ -466,35 +370,7 @@ struct option_t MuttVars[] = { ** .pp ** This variable controls whether or not copies of your outgoing messages ** will be saved for later references. Also see ``$$record'', - ** ``$$save_name'', ``$$force_name'' and ``$fcc-hook''. - */ - - {"crypt_use_gpgme", DT_BOOL, R_NONE, OPTCRYPTUSEGPGME, "no" }, - /* - ** .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 - ** S/MIME and PGP will be used instead of the classic code. - ** .pp - ** \fBNote\fP: You need to use this option in your \fT.muttngrc\fP configuration - ** file as it won't have any effect when used interactively. - */ - - {"crypt_autopgp", DT_BOOL, R_NONE, OPTCRYPTAUTOPGP, "yes" }, - /* - ** .pp - ** This variable controls whether or not Mutt-ng may automatically enable - ** PGP encryption/signing for messages. See also ``$$crypt_autoencrypt'', - ** ``$$crypt_replyencrypt'', - ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''. - */ - {"crypt_autosmime", DT_BOOL, R_NONE, OPTCRYPTAUTOSMIME, "yes" }, - /* - ** .pp - ** This variable controls whether or not Mutt-ng may automatically enable - ** S/MIME encryption/signing for messages. See also ``$$crypt_autoencrypt'', - ** ``$$crypt_replyencrypt'', - ** ``$$crypt_autosign'', ``$$crypt_replysign'' and ``$$smime_is_default''. + ** and ``$fcc-hook''. */ {"date_format", DT_STR, R_BOTH, UL &DateFmt, "!%a, %b %d, %Y at %I:%M:%S%p %Z"}, /* @@ -510,24 +386,6 @@ struct option_t MuttVars[] = { ** rest of the string are expanded in the \fIC\fP locale (that is in US ** English). */ -#ifdef DEBUG - {"debug_level", DT_NUM, R_NONE, UL &DebugLevel, "1" }, - /* - ** .pp - ** Availability: debug - ** - ** .pp - ** This variable specifies the current debug level and - ** may be used to increase or decrease the verbosity level - ** during runtime. It overrides the level given with the - ** \fT-d\fP command line option. - ** - ** .pp - ** Currently, this number must be >= 0 and <= 5 and muttng - ** must be started with \fT-d\fP to enable debugging at all; - ** enabling at runtime is not possible. - */ -#endif {"default_hook", DT_STR, R_NONE, UL &DefaultHook, "~f %s !~P | (~P ~C %s)"}, /* ** .pp @@ -566,14 +424,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, ""}, @@ -583,49 +441,11 @@ struct option_t MuttVars[] = { ** is viewed it is passed as standard input to $$display_filter, and the ** filtered message is read from the standard output. */ -#if defined(DL_STANDALONE) && defined(USE_DOTLOCK) - {"dotlock_program", DT_PATH, R_NONE, UL &MuttDotlock, "$muttng_bindir/muttng_dotlock"}, - /* - ** .pp - ** Availability: Standalone and Dotlock - ** - ** .pp - ** Contains the path of the \fTmuttng_dotlock(1)\fP binary to be used by - ** Mutt-ng. - */ -#endif - {"dsn_notify", DT_STR, R_NONE, UL &DsnNotify, ""}, - /* - ** .pp - ** \fBNote:\fP you should not enable this unless you are using Sendmail - ** 8.8.x or greater or in connection with the SMTP support via libESMTP. - ** .pp - ** This variable sets the request for when notification is returned. The - ** string consists of a comma separated list (no spaces!) of one or more - ** of the following: \fInever\fP, to never request notification, - ** \fIfailure\fP, to request notification on transmission failure, - ** \fIdelay\fP, to be notified of message delays, \fIsuccess\fP, to be - ** notified of successful transmission. - ** .pp - ** Example: \fTset dsn_notify="failure,delay"\fP - */ - {"dsn_return", DT_STR, R_NONE, UL &DsnReturn, ""}, - /* - ** .pp - ** \fBNote:\fP you should not enable this unless you are using Sendmail - ** 8.8.x or greater or in connection with the SMTP support via libESMTP. - ** .pp - ** This variable controls how much of your message is returned in DSN - ** messages. It may be set to either \fIhdrs\fP to return just the - ** message header, or \fIfull\fP to return the full message. - ** .pp - ** Example: \fTset dsn_return=hdrs\fP - */ {"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 - ** messages with the same \fTMessage-Id:\fP header field together. + ** 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. */ @@ -654,52 +474,21 @@ struct option_t MuttVars[] = { ** Note: if $$edit_headers had to be turned on by force because ** $$strict_mailto is \fIunset\fP, this option has no effect. */ - {"editor", DT_PATH, R_NONE, UL &Editor, "" }, - /* - ** .pp - ** This variable specifies which editor is used by Mutt-ng. - ** 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. - ** .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 - ** 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 - ** 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 - ** ``Franklin'' to ``Franklin, Steve''. - */ #ifdef USE_NNTP {"nntp_group_index_format", DT_STR, R_BOTH, UL &GroupFormat, "%4C %M%N %5s %-45.45f %d"}, /* @@ -914,7 +651,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. */ @@ -926,48 +663,48 @@ 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 + ** affect the generation of \fTMessage-ID:\fP header fields, and it will not lead to the ** cut-off of first-level domains. */ {"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. */ @@ -984,51 +721,38 @@ struct option_t MuttVars[] = { ** This variable controls whether or not a \fTMail-Followup-To:\fP header field is ** honored when group-replying to a message. */ - {"hostname", DT_STR, R_NONE, UL &Fqdn, "" }, - /* - ** .pp - ** Specifies the hostname to use after the ``\fT@\fP'' in local e-mail - ** addresses and during generation of \fTMessage-Id:\fP headers. - ** .pp - ** Please be sure to really know what you are doing when changing this variable - ** to configure a custom domain part of Message-IDs. - */ {"ignore_list_reply_to", DT_BOOL, R_NONE, OPTIGNORELISTREPLYTO, "no" }, /* ** .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 ** function; \fIgroup-reply\fP will reply to both the sender and the ** list. - ** Remember: This option works only for mailing lists which are explicitly set in your muttngrc + ** Remember: This option works only for mailing lists which are explicitly set in your madmuttrc ** configuration file. */ -#ifdef USE_IMAP {"imap_authenticators", DT_STR, R_NONE, UL &ImapAuthenticators, "" }, /* ** .pp - ** Availability: IMAP - ** - ** .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" }, /* @@ -1037,12 +761,8 @@ struct option_t MuttVars[] = { ** your server on connection, and add them to the set of mailboxes ** it polls for new mail. See also the ``$mailboxes'' command. */ - {"imap_delim_chars", DT_STR, R_NONE, UL &ImapDelimChars, "/."}, /* - ** .pp - ** Availability: IMAP - ** ** .pp ** This contains the list of characters which you would like to treat ** as folder separators for displaying IMAP paths. In particular it @@ -1051,10 +771,7 @@ struct option_t MuttVars[] = { {"imap_headers", DT_STR, R_INDEX, UL &ImapHeaders, "" }, /* ** .pp - ** Availability: IMAP - ** - ** .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 @@ -1064,9 +781,6 @@ struct option_t MuttVars[] = { */ {"imap_home_namespace", DT_STR, R_NONE, UL &ImapHomeNamespace, "" }, /* - ** .pp - ** Availability: IMAP - ** ** .pp ** You normally want to see your personal folders alongside ** your \fTINBOX\fP in the IMAP browser. If you see something else, you may set @@ -1075,12 +789,9 @@ struct option_t MuttVars[] = { {"imap_keepalive", DT_NUM, R_NONE, UL &ImapKeepalive, "900" }, /* ** .pp - ** Availability: IMAP - ** - ** .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 @@ -1092,9 +803,6 @@ struct option_t MuttVars[] = { */ {"imap_login", DT_STR, R_NONE, UL &ImapLogin, "" }, /* - ** .pp - ** Availability: IMAP - ** ** .pp ** Your login name on the IMAP server. ** .pp @@ -1102,9 +810,6 @@ struct option_t MuttVars[] = { */ {"imap_list_subscribed", DT_BOOL, R_NONE, OPTIMAPLSUB, "no" }, /* - ** .pp - ** Availability: IMAP - ** ** .pp ** This variable configures whether IMAP folder browsing will look for ** only subscribed folders or all folders. This can be toggled in the @@ -1113,17 +818,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 - ** Availability: IMAP - ** - ** .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 @@ -1133,22 +835,16 @@ struct option_t MuttVars[] = { {"imap_passive", DT_BOOL, R_NONE, OPTIMAPPASSIVE, "yes" }, /* ** .pp - ** Availability: IMAP - ** - ** .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 - ** Availability: IMAP - ** - ** .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. @@ -1156,19 +852,13 @@ struct option_t MuttVars[] = { {"imap_reconnect", DT_QUAD, R_NONE, OPT_IMAPRECONNECT, "ask-yes" }, /* ** .pp - ** Availability: IMAP - ** - ** .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 - ** Availability: IMAP - ** - ** .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 @@ -1176,22 +866,18 @@ struct option_t MuttVars[] = { */ {"imap_user", DT_STR, R_NONE, UL &ImapUser, "" }, /* - ** .pp - ** Availability: IMAP - ** ** .pp ** The name of the user whose mail you intend to access on the IMAP ** server. ** .pp ** This variable defaults to your user name on the local machine. */ -#endif {"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. */ @@ -1204,7 +890,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, "> "}, @@ -1222,7 +908,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 @@ -1251,7 +937,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) @@ -1260,6 +946,7 @@ struct option_t MuttVars[] = { ** .dt %u .dd user (login) name of the author ** .dt %v .dd first name of the author, or the recipient if the message is from you ** .dt %W .dd name of organization of author (`organization:' field) + ** .dt %X .dd number of attachments ** .dt %y .dd `x-label:' field, if present ** .dt %Y .dd `x-label' field, if present, and (1) not at part of a thread tree, ** (2) at the top of a thread, or (3) `x-label' is different from @@ -1290,7 +977,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 @@ -1300,11 +987,6 @@ struct option_t MuttVars[] = { ** Example: \fTset inews="/usr/local/bin/inews -hS"\fP */ #endif - {"ispell", DT_PATH, R_NONE, UL &Ispell, ISPELL}, - /* - ** .pp - ** How to invoke ispell (GNU's spell-checking software). - */ {"keep_flagged", DT_BOOL, R_NONE, OPTKEEPFLAGGED, "no" }, /* ** .pp @@ -1318,12 +1000,12 @@ struct option_t MuttVars[] = { ** The locale used by \fTstrftime(3)\fP to format dates. Legal values are ** the strings your system accepts for the locale variable \fTLC_TIME\fP. */ - {"list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, "no" }, + {"force_list_reply", DT_QUAD, R_NONE, OPT_LISTREPLY, "ask-no" }, /* ** .pp - ** When \fIset\fP, address replies to the mailing list the original message came - ** from (instead to the author only). Setting this option to ``\fIask-yes\fP'' or - ** ``\fIask-no\fP'' will ask if you really intended to reply to the author only. + ** This variable controls what effect ordinary replies have on mailing list + ** messages: if \fIset\fP, a normal reply will be interpreted as list-reply + ** while if it's \fIunset\fP the reply functions work as usual. */ {"max_display_recips", DT_NUM, R_PAGER, UL &MaxDispRecips, "0" }, /* @@ -1340,33 +1022,8 @@ struct option_t MuttVars[] = { ** to this length. A value of 0 (which is also the default) means that the ** maximum line length is determined by the terminal width and $$wrapmargin. */ - {"mail_check", DT_NUM, R_NONE, UL &BuffyTimeout, "5" }, - /* - ** .pp - ** This variable configures how often (in seconds) Mutt-ng should look for - ** new mail. - ** .pp - ** \fBNote:\fP This does not apply to IMAP mailboxes, see $$imap_mail_check. - */ - {"mailcap_path", DT_STR, R_NONE, UL &MailcapPath, "" }, - /* - ** .pp - ** This variable specifies which files to consult when attempting to - ** display MIME bodies not directly supported by Mutt-ng. - */ - {"mailcap_sanitize", DT_BOOL, R_NONE, OPTMAILCAPSANITIZE, "yes" }, - /* - ** .pp - ** If \fIset\fP, Mutt-ng 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 - ** \fBDON'T CHANGE THIS SETTING UNLESS YOU ARE REALLY SURE WHAT YOU ARE - ** DOING!\fP - */ #ifdef USE_HCACHE - - {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, "" }, + {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, "~/.cache/madmutt/" }, /* ** .pp ** Availability: Header Cache @@ -1379,17 +1036,7 @@ struct option_t MuttVars[] = { ** be a single global header cache. By default it is \fIunset\fP so no ** header caching will be used. */ - {"maildir_header_cache_verify", DT_BOOL, R_NONE, OPTHCACHEVERIFY, "yes" }, - /* - ** .pp - ** Availability: Header Cache - ** - ** .pp - ** Check for Maildir unaware programs other than Mutt-ng 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. - */ -#if HAVE_GDBM || HAVE_DB4 +#if defined(HAVE_GDBM) {"header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, "16384"}, /* ** .pp @@ -1404,8 +1051,8 @@ struct option_t MuttVars[] = { ** less the best you can get. For details google for mutt header ** cache (first hit). */ -#endif /* HAVE_GDBM || HAVE_DB 4 */ -#if HAVE_QDBM +#endif /* HAVE_GDBM */ +#ifdef HAVE_QDBM { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, "no" }, /* ** .pp @@ -1430,10 +1077,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. */ @@ -1457,83 +1104,6 @@ struct option_t MuttVars[] = { ** This specifies the folder into which read mail in your ``$$spoolfile'' ** folder will be appended. */ - {"muttng_version", DT_SYS, R_NONE, 0, VERSION }, - /* - ** .pp - ** \fIThis is a read-only system property and specifies muttng's - ** version string.\fP - */ - {"muttng_revision", DT_SYS, R_NONE, 0, MUTT_REVISION }, - /* - ** .pp - ** \fIThis is a read-only system property and specifies muttng's - ** subversion revision string.\fP - */ - {"muttng_sysconfdir", DT_SYS, R_NONE, 0, SYSCONFDIR }, - /* - ** .pp - ** \fIThis is a read-only system property and specifies the - ** directory containing the muttng system-wide configuration.\fP - */ - {"muttng_bindir", DT_SYS, R_NONE, 0, BINDIR }, - /* - ** .pp - ** \fIThis is a read-only system property and specifies the - ** directory containing the muttng binary.\fP - */ - {"muttng_docdir", DT_SYS, R_NONE, 0, PKGDOCDIR }, - /* - ** .pp - ** \fIThis is a read-only system property and specifies the - ** directory containing the muttng documentation.\fP - */ -#ifdef USE_HCACHE -#if HAVE_QDBM - {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "qdbm" }, -#elif HAVE_GDBM - {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "gdbm" }, -#elif HAVE_DB4 - {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "db4" }, -#else - {"muttng_hcache_backend", DT_SYS, R_NONE, 0, "unknown" }, -#endif - /* - ** .pp - ** \fIThis is a read-only system property and specifies the - ** header chaching's database backend.\fP - */ -#endif - {"muttng_folder_path", DT_SYS, R_NONE, 0, "" }, - /* - ** .pp - ** \fIThis is a read-only system property and, at runtime, - ** specifies the full path or URI of the folder currently - ** open (if any).\fP - */ - {"muttng_folder_name", DT_SYS, R_NONE, 0, "" }, - /* - ** .pp - ** \fIThis is a read-only system property and, at runtime, - ** specifies the last part of the full path or URI of the - ** folder currently open (if any), i.e. everything after - ** the last ``/''.\fP - */ - {"muttng_pwd", DT_SYS, R_NONE, 0, "" }, - /* - ** .pp - ** \fIThis is a read-only system property and, at runtime, - ** specifies the current working directory of the muttng - ** binary.\fP - */ - {"operating_system", DT_STR, R_NONE, UL &OperatingSystem, "" }, - /* - ** .pp - ** This specifies the operating system name for the \fTUser-Agent:\fP header field. If - ** this is \fIunset\fP, it will be set to the operating system name that \fTuname(2)\fP - ** returns. If \fTuname(2)\fP fails, ``UNIX'' will be used. - ** .pp - ** It may, for example, look as: ``\fTmutt-ng 1.5.9i (Linux)\fP''. - */ {"sidebar_boundary", DT_STR, R_BOTH, UL &SidebarBoundary, "." }, /* ** .pp @@ -1544,7 +1114,7 @@ struct option_t MuttVars[] = { {"sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, "|"}, /* ** .pp - ** This specifies the delimiter between the sidebar (if visible) and + ** This specifies the delimiter between the sidebar (if visible) and ** other screens. */ {"sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, "no" }, @@ -1568,7 +1138,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 @@ -1581,6 +1151,7 @@ struct option_t MuttVars[] = { ** .dt %M .dd Total number of messages shown, i.e. not hidden by a limit. 1) ** .dt %n .dd Number of new messages. ** .dt %t .dd Number of tagged messages. 1) + ** .dt %u .dd Number of unread messages. ** .de ** .pp ** 1) These expandos only have a non-zero value for the current mailbox and @@ -1591,9 +1162,9 @@ struct option_t MuttVars[] = { ** .pp ** When \fIset\fP, the ``hierarchy'' of the sidebar entries will be shortened ** only if they cannot be printed in full length (because ``$$sidebar_width'' - ** is set to a too low value). For example, if the newsgroup name + ** is set to a too low value). For example, if the newsgroup name ** ``de.alt.sysadmin.recovery'' doesn't fit on the screen, it'll get shortened - ** ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not get + ** ``d.a.s.recovery'' while ``de.alt.d0'' still would and thus will not get ** shortened. ** .pp ** At which characters this compression is done is controled via the @@ -1603,12 +1174,12 @@ struct option_t MuttVars[] = { /* ** .pp ** The default mailbox type used when creating new folders. May be any of - ** \fTmbox\fP, \fTMMDF\fP, \fTMH\fP and \fTMaildir\fP. + ** \fTmbox\fP, \fTMH\fP and \fTMaildir\fP. */ {"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" }, @@ -1635,18 +1206,18 @@ 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 \fT0xf4\fP, then this is treated as if the user had + ** has an ASCII value of \fT0xf8\fP, then this is treated as if the user had ** pressed \fTESC\fP then ``\fTx\fP''. This is because the result of removing the - ** high bit from ``\fT0xf4\fP'' is ``\fT0x74\fP'', which is the ASCII character + ** high bit from ``\fT0xf8\fP'' is ``\fT0x78\fP'', which is the ASCII character ** ``\fTx\fP''. */ {"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. @@ -1694,30 +1265,11 @@ struct option_t MuttVars[] = { ** menu, attachments which cannot be decoded in a reasonable manner will ** be attached to the newly composed message if this option is set. */ - -#ifdef USE_NNTP - {"nntp_mime_subject", DT_BOOL, R_NONE, OPTMIMESUBJECT, "yes" }, - /* - ** .pp - ** Availability: NNTP - ** - ** .pp - ** If \fIunset\fP, an 8-bit ``\fTSubject:\fP'' header field in a news article - ** will not be encoded according to RFC2047. - ** .pp - ** \fBNote:\fP Only change this setting if you know what you are doing. - */ -#endif - -#ifdef MIXMASTER {"mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, "%4n %c %-16s %a"}, /* - ** .pp - ** Availability: Mixmaster - ** ** .pp ** This variable describes the format of a remailer line on the mixmaster - ** chain selection screen. The following \fTprintf(3)\fP-like sequences are + ** chain selection screen. The following \fTprintf(3)\fP-like sequences are ** supported: ** .pp ** .dl @@ -1729,20 +1281,16 @@ struct option_t MuttVars[] = { */ {"mixmaster", DT_PATH, R_NONE, UL &Mixmaster, MIXMASTER}, /* - ** .pp - ** Availability: Mixmaster - ** ** .pp ** This variable contains the path to the Mixmaster binary on your ** system. It is used with various sets of parameters to gather the ** list of known remailers, and to finally send a message through the ** mixmaster chain. */ -#endif {"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. */ @@ -1756,8 +1304,8 @@ struct option_t MuttVars[] = { {"msgid_format", DT_STR, R_NONE, UL &MsgIdFormat, "%Y%m%d%h%M%s.G%P%p"}, /* ** .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 + ** This is the format for the ``local part'' of the \fTMessage-ID:\fP header + ** 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: @@ -1769,7 +1317,7 @@ struct option_t MuttVars[] = { ** .dt %M .dd the current minute ** .dt %O .dd the current UNIX timestamp (octal) ** .dt %p .dd the process ID - ** .dt %P .dd the current Message-ID prefix (a character rotating with + ** .dt %P .dd the current Message-ID prefix (a character rotating with ** every Message-ID being generated) ** .dt %r .dd a random integer value (decimal) ** .dt %R .dd a random integer value (hexadecimal) @@ -1790,13 +1338,13 @@ struct option_t MuttVars[] = { ** deeper threads to fit on the screen. */ #ifdef USE_NNTP - {"nntp_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, "~/.muttng"}, + {"nntp_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, "~/.madmutt"}, /* ** .pp ** 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 @@ -1869,7 +1417,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, ""}, /* @@ -1890,7 +1438,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" }, @@ -1899,11 +1447,10 @@ 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 -#ifdef USE_SOCKET { "net_inc", DT_NUM, R_NONE, UL &NetInc, "10" }, /* ** .pp @@ -1913,26 +1460,12 @@ struct option_t MuttVars[] = { ** .pp ** See also ``$$read_inc'' and ``$$write_inc''. */ -#endif - {"pager", DT_PATH, R_NONE, UL &Pager, "builtin"}, - /* - ** .pp - ** This variable specifies which pager you would like to use to view - ** messages. ``builtin'' means to use the builtin pager, otherwise this - ** variable should specify the pathname of the external pager you would - ** like to use. - ** .pp - ** Using an external pager may have some disadvantages: Additional - ** keystrokes are necessary because you can't call Mutt-ng functions - ** directly from the pager, and screen resizes cause lines longer than - ** the screen width to be badly formatted in the help menu. - */ {"pager_context", DT_NUM, R_NONE, UL &PagerContext, "0" }, /* ** .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"}, @@ -1965,397 +1498,61 @@ struct option_t MuttVars[] = { ** when you are at the end of a message and invoke the \fInext-page\fP ** function. */ - {"crypt_autosign", DT_BOOL, R_NONE, OPTCRYPTAUTOSIGN, "no" }, + {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, "no" }, /* ** .pp - ** Setting this variable will cause Mutt-ng 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, - ** then OpenSSL is used instead to create S/MIME messages and settings can - ** be overridden by use of the \fIsmime-menu\fP. - ** (Crypto only) - */ - {"crypt_autoencrypt", DT_BOOL, R_NONE, OPTCRYPTAUTOENCRYPT, "no" }, - /* + ** If \fIset\fP, signed and encrypted messages will consist of nested + ** multipart/signed and multipart/encrypted body parts. ** .pp - ** Setting this variable will cause Mutt-ng 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 - ** signing is requested as well. If ``$$smime_is_default'' is \fIset\fP, - ** then OpenSSL is used instead to create S/MIME messages and - ** settings can be overridden by use of the \fIsmime-menu\fP. - ** (Crypto only) + ** This is useful for applications like encrypted and signed mailing + ** lists, where the outer layer (multipart/encrypted) can be easily + ** removed, while the inner multipart/signed part is retained. + ** (PGP only) */ - {"pgp_ignore_subkeys", DT_BOOL, R_NONE, OPTPGPIGNORESUB, "yes" }, + {"pgp_show_unusable", DT_BOOL, R_NONE, OPTPGPSHOWUNUSABLE, "yes" }, /* ** .pp - ** Setting this variable will cause Mutt-ng 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. + ** 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) */ - {"crypt_replyencrypt", DT_BOOL, R_NONE, OPTCRYPTREPLYENCRYPT, "yes" }, + {"pgp_sign_as", DT_STR, R_NONE, UL &PgpSignAs, "" }, /* ** .pp - ** If \fIset\fP, automatically PGP or OpenSSL encrypt replies to messages which are - ** encrypted. - ** (Crypto only) + ** If you have more than one key pair, this option allows you to specify + ** which of your private keys to use. It is recommended that you use the + ** keyid form to specify your key (e.g., ``\fT0x00112233\fP''). + ** (PGP only) */ - {"crypt_replysign", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGN, "no" }, + {"pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, "address" }, /* ** .pp - ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages which are - ** signed. - ** .pp - ** \fBNote:\fP this does not work on messages that are encrypted \fBand\fP signed! - ** (Crypto only) - */ - {"crypt_replysignencrypted", DT_BOOL, R_NONE, OPTCRYPTREPLYSIGNENCRYPTED, "no" }, - /* + ** Specifies how the entries in the ``pgp keys'' menu are sorted. The + ** following are legal values: ** .pp - ** If \fIset\fP, automatically PGP or OpenSSL sign replies to messages - ** 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 - ** to find out whether an encrypted message is also signed. - ** (Crypto only) - */ - {"crypt_timestamp", DT_BOOL, R_NONE, OPTCRYPTTIMESTAMP, "yes" }, - /* + ** .dl + ** .dt address .dd sort alphabetically by user id + ** .dt keyid .dd sort alphabetically by key id + ** .dt date .dd sort by key creation date + ** .dt trust .dd sort by the trust of the key + ** .de ** .pp - ** If \fIset\fP, Mutt-ng 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. - ** (Crypto only) + ** If you prefer reverse order of the above values, prefix it with + ** ``reverse-''. + ** (PGP only) */ - {"pgp_use_gpg_agent", DT_BOOL, R_NONE, OPTUSEGPGAGENT, "no" }, + {"pgp_auto_decode", DT_BOOL, R_NONE, OPTPGPAUTODEC, "no" }, /* ** .pp - ** If \fIset\fP, Mutt-ng will use a possibly-running gpg-agent process. - ** (PGP only) - */ - {"crypt_verify_sig", DT_QUAD, R_NONE, OPT_VERIFYSIG, "yes" }, - /* - ** .pp - ** If ``\fIyes\fP'', always attempt to verify PGP or S/MIME signatures. - ** If ``\fIask\fP'', ask whether or not to verify the signature. - ** If ``\fIno\fP'', never attempt to verify cryptographic signatures. - ** (Crypto only) - */ - {"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 - ** 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 - ** select the same application that was used to sign/encrypt the original - ** message. - ** .pp - ** (Note that this variable can be overridden by unsetting $$crypt_autosmime.) - ** (S/MIME only) - */ - {"smime_ask_cert_label", DT_BOOL, R_NONE, OPTASKCERTLABEL, "yes" }, - /* - ** .pp - ** This flag controls whether you want to be asked to enter a label - ** for a certificate about to be added to the database or not. It is - ** \fIset\fP by default. - ** (S/MIME only) - */ - {"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 - ** to determine the key to use. It will ask you to supply a key, if it can't find one. - ** (S/MIME only) - */ - {"pgp_entry_format", DT_STR, R_NONE, UL &PgpEntryFormat, "%4n %t%f %4l/0x%k %-4a %2c %u"}, - /* - ** .pp - ** This variable allows you to customize the PGP key selection menu to - ** your personal taste. This string is similar to ``$$index_format'', but - ** has its own set of \fTprintf(3)\fP-like sequences: - ** .pp - ** .dl - ** .dt %n .dd number - ** .dt %k .dd key id - ** .dt %u .dd user id - ** .dt %a .dd algorithm - ** .dt %l .dd key length - ** .dt %f .dd flags - ** .dt %c .dd capabilities - ** .dt %t .dd trust/validity of the key-uid association - ** .dt %[] .dd date of the key where is an \fTstrftime(3)\fP expression - ** .de - ** .pp - ** (PGP only) - */ - {"pgp_good_sign", DT_RX, R_NONE, UL &PgpGoodSign, "" }, - /* - ** .pp - ** If you assign a text to this variable, then a PGP signature is only - ** considered verified if the output from $$pgp_verify_command contains - ** the text. Use this variable if the exit code from the command is 0 - ** even for bad signatures. - ** (PGP only) - */ - {"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 - ** signing or encrypting. A non-zero exit code means that the - ** subprocess failed. - ** (PGP only) - */ - {"pgp_long_ids", DT_BOOL, R_NONE, OPTPGPLONGIDS, "no" }, - /* - ** .pp - ** If \fIset\fP, use 64 bit PGP key IDs. \fIUnset\fP uses the normal 32 bit Key IDs. - ** (PGP only) - */ - {"pgp_retainable_sigs", DT_BOOL, R_NONE, OPTPGPRETAINABLESIG, "no" }, - /* - ** .pp - ** If \fIset\fP, signed and encrypted messages will consist of nested - ** multipart/signed and multipart/encrypted body parts. - ** .pp - ** This is useful for applications like encrypted and signed mailing - ** lists, where the outer layer (multipart/encrypted) can be easily - ** removed, while the inner multipart/signed part is retained. - ** (PGP only) - */ - {"pgp_autoinline", DT_BOOL, R_NONE, OPTPGPAUTOINLINE, "no" }, - /* - ** .pp - ** This option controls whether Mutt-ng 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 - ** configured to ask before sending PGP/MIME messages when inline - ** (traditional) would not work. - ** See also: ``$$pgp_mime_auto''. - ** .pp - ** Also note that using the old-style PGP message format is \fBstrongly\fP - ** \fBdeprecated\fP. - ** (PGP only) - */ - {"pgp_replyinline", DT_BOOL, R_NONE, OPTPGPREPLYINLINE, "no" }, - /* - ** .pp - ** Setting this variable will cause Mutt-ng 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 - ** 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 - ** configured to ask before sending PGP/MIME messages when inline - ** (traditional) would not work. - ** See also: ``$$pgp_mime_auto''. - ** .pp - ** Also note that using the old-style PGP message format is \fBstrongly\fP - ** \fBdeprecated\fP. - ** (PGP only) - ** - */ - {"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 - ** menu. This includes keys which have been revoked, have expired, or - ** have been marked as ``disabled'' by the user. - ** (PGP only) - */ - {"pgp_sign_as", DT_STR, R_NONE, UL &PgpSignAs, "" }, - /* - ** .pp - ** If you have more than one key pair, this option allows you to specify - ** which of your private keys to use. It is recommended that you use the - ** keyid form to specify your key (e.g., ``\fT0x00112233\fP''). - ** (PGP only) - */ - {"pgp_strict_enc", DT_BOOL, R_NONE, OPTPGPSTRICTENC, "yes" }, - /* - ** .pp - ** If \fIset\fP, Mutt-ng 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. - ** (PGP only) - */ - {"pgp_timeout", DT_NUM, R_NONE, UL &PgpTimeout, "300" }, - /* - ** .pp - ** The number of seconds after which a cached passphrase will expire if - ** not used. Default: 300. - ** (PGP only) - */ - {"pgp_sort_keys", DT_SORT|DT_SORT_KEYS, R_NONE, UL &PgpSortKeys, "address" }, - /* - ** .pp - ** Specifies how the entries in the ``pgp keys'' menu are sorted. The - ** following are legal values: - ** .pp - ** .dl - ** .dt address .dd sort alphabetically by user id - ** .dt keyid .dd sort alphabetically by key id - ** .dt date .dd sort by key creation date - ** .dt trust .dd sort by the trust of the key - ** .de - ** .pp - ** If you prefer reverse order of the above values, prefix it with - ** ``reverse-''. - ** (PGP only) - */ - {"pgp_mime_auto", DT_QUAD, R_NONE, OPT_PGPMIMEAUTO, "ask-yes" }, - /* - ** .pp - ** This option controls whether Mutt-ng will prompt you for - ** automatically sending a (signed/encrypted) message using - ** PGP/MIME when inline (traditional) fails (for any reason). - ** .pp - ** Also note that using the old-style PGP message format is \fBstrongly\fP - ** \fBdeprecated\fP. - ** (PGP only) - */ - {"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. */ - /* XXX Default values! */ - - {"pgp_decode_command", DT_STR, R_NONE, UL &PgpDecodeCommand, "" }, - /* - ** .pp - ** This format strings specifies a command which is used to decode - ** application/pgp attachments. - ** .pp - ** The PGP command formats have their own set of \fTprintf(3)\fP-like sequences: - ** .pp - ** .dl - ** .dt %p .dd Expands to PGPPASSFD=0 when a pass phrase is needed, to an empty - ** string otherwise. Note: This may be used with a %? construct. - ** .dt %f .dd Expands to the name of a file containing a message. - ** .dt %s .dd Expands to the name of a file containing the signature part - ** . of a multipart/signed attachment when verifying it. - ** .dt %a .dd The value of $$pgp_sign_as. - ** .dt %r .dd One or more key IDs. - ** .de - ** .pp - ** For examples on how to configure these formats for the various versions - ** of PGP which are floating around, see the pgp*.rc and gpg.rc files in - ** the \fTsamples/\fP subdirectory which has been installed on your system - ** alongside the documentation. - ** (PGP only) - */ - {"pgp_getkeys_command", DT_STR, R_NONE, UL &PgpGetkeysCommand, "" }, - /* - ** .pp - ** This command is invoked whenever Mutt-ng will need public key information. - ** \fT%r\fP is the only \fTprintf(3)\fP-like sequence used with this format. - ** (PGP only) - */ - {"pgp_verify_command", DT_STR, R_NONE, UL &PgpVerifyCommand, "" }, - /* - ** .pp - ** This command is used to verify PGP signatures. - ** (PGP only) - */ - {"pgp_decrypt_command", DT_STR, R_NONE, UL &PgpDecryptCommand, "" }, - /* - ** .pp - ** This command is used to decrypt a PGP encrypted message. - ** (PGP only) - */ - {"pgp_clearsign_command", DT_STR, R_NONE, UL &PgpClearSignCommand, "" }, - /* - ** .pp - ** This format is used to create a old-style ``clearsigned'' PGP message. - ** .pp - ** Note that the use of this format is \fBstrongly\fP \fBdeprecated\fP. - ** (PGP only) - */ - {"pgp_sign_command", DT_STR, R_NONE, UL &PgpSignCommand, "" }, - /* - ** .pp - ** This command is used to create the detached PGP signature for a - ** multipart/signed PGP/MIME body part. - ** (PGP only) - */ - {"pgp_encrypt_sign_command", DT_STR, R_NONE, UL &PgpEncryptSignCommand, "" }, - /* - ** .pp - ** This command is used to both sign and encrypt a body part. - ** (PGP only) - */ - {"pgp_encrypt_only_command", DT_STR, R_NONE, UL &PgpEncryptOnlyCommand, "" }, - /* - ** .pp - ** This command is used to encrypt a body part without signing it. - ** (PGP only) - */ - {"pgp_import_command", DT_STR, R_NONE, UL &PgpImportCommand, "" }, - /* - ** .pp - ** This command is used to import a key from a message into - ** the user's public key ring. - ** (PGP only) - */ - {"pgp_export_command", DT_STR, R_NONE, UL &PgpExportCommand, "" }, - /* - ** .pp - ** This command is used to export a public key from the user's - ** key ring. - ** (PGP only) - */ - {"pgp_verify_key_command", DT_STR, R_NONE, UL &PgpVerifyKeyCommand, "" }, - /* - ** .pp - ** This command is used to verify key information from the key selection - ** menu. - ** (PGP only) - */ - {"pgp_list_secring_command", DT_STR, R_NONE, UL &PgpListSecringCommand, "" }, - /* - ** .pp - ** This command is used to list the secret key ring's contents. The - ** output format must be analogous to the one used by - ** \fTgpg --list-keys --with-colons\fP. - ** .pp - ** This format is also generated by the \fTpgpring\fP utility which comes - ** with Mutt-ng. - ** (PGP only) - */ - {"pgp_list_pubring_command", DT_STR, R_NONE, UL &PgpListPubringCommand, "" }, - /* - ** .pp - ** This command is used to list the public key ring's contents. The - ** output format must be analogous to the one used by - ** \fTgpg --list-keys --with-colons\fP. - ** .pp - ** This format is also generated by the \fTpgpring\fP utility which comes - ** with Mutt-ng. - ** (PGP only) - */ {"forward_decrypt", DT_BOOL, R_NONE, OPTFORWDECRYPT, "yes" }, /* ** .pp @@ -2365,13 +1562,6 @@ struct option_t MuttVars[] = { ** ``$$mime_forward_decode'' is \fIunset\fP. ** (PGP only) */ - {"smime_timeout", DT_NUM, R_NONE, UL &SmimeTimeout, "300" }, - /* - ** .pp - ** The number of seconds after which a cached passphrase will expire if - ** not used. - ** (S/MIME only) - */ {"smime_encrypt_with", DT_STR, R_NONE, UL &SmimeCryptAlg, "" }, /* ** .pp @@ -2382,131 +1572,6 @@ struct option_t MuttVars[] = { ** If \fIunset\fP ``\fI3des\fP'' (TripleDES) is used. ** (S/MIME only) */ - {"smime_keys", DT_PATH, R_NONE, UL &SmimeKeys, "" }, - /* - ** .pp - ** Since there is no pubring/secring as with PGP, Mutt-ng 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 - ** which contains mailbox-address keyid pair, and which can be manually - ** edited. This one points to the location of the private keys. - ** (S/MIME only) - */ - {"smime_ca_location", DT_PATH, R_NONE, UL &SmimeCALocation, "" }, - /* - ** .pp - ** This variable contains the name of either a directory, or a file which - ** contains trusted certificates for use with OpenSSL. - ** (S/MIME only) - */ - {"smime_certificates", DT_PATH, R_NONE, UL &SmimeCertificates, "" }, - /* - ** .pp - ** Since there is no pubring/secring as with PGP, Mutt-ng 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 - ** OpenSSL. There is an index file which contains mailbox-address - ** keyid pairs, and which can be manually edited. This one points to - ** the location of the certificates. - ** (S/MIME only) - */ - {"smime_decrypt_command", DT_STR, R_NONE, UL &SmimeDecryptCommand, "" }, - /* - ** .pp - ** This format string specifies a command which is used to decrypt - ** \fTapplication/x-pkcs7-mime\fP attachments. - ** .pp - ** The OpenSSL command formats have their own set of \fTprintf(3)\fP-like sequences - ** similar to PGP's: - ** .pp - ** .dl - ** .dt %f .dd Expands to the name of a file containing a message. - ** .dt %s .dd Expands to the name of a file containing the signature part - ** . of a multipart/signed attachment when verifying it. - ** .dt %k .dd The key-pair specified with $$smime_default_key - ** .dt %c .dd One or more certificate IDs. - ** .dt %a .dd The algorithm used for encryption. - ** .dt %C .dd CA location: Depending on whether $$smime_ca_location - ** . points to a directory or file, this expands to - ** . "-CApath $$smime_ca_location" or "-CAfile $$smime_ca_location". - ** .de - ** .pp - ** For examples on how to configure these formats, see the smime.rc in - ** the \fTsamples/\fP subdirectory which has been installed on your system - ** alongside the documentation. - ** (S/MIME only) - */ - {"smime_verify_command", DT_STR, R_NONE, UL &SmimeVerifyCommand, "" }, - /* - ** .pp - ** This command is used to verify S/MIME signatures of type \fTmultipart/signed\fP. - ** (S/MIME only) - */ - {"smime_verify_opaque_command", DT_STR, R_NONE, UL &SmimeVerifyOpaqueCommand, "" }, - /* - ** .pp - ** This command is used to verify S/MIME signatures of type - ** \fTapplication/x-pkcs7-mime\fP. - ** (S/MIME only) - */ - {"smime_sign_command", DT_STR, R_NONE, UL &SmimeSignCommand, "" }, - /* - ** .pp - ** This command is used to created S/MIME signatures of type - ** \fTmultipart/signed\fP, which can be read by all mail clients. - ** (S/MIME only) - */ - {"smime_sign_opaque_command", DT_STR, R_NONE, UL &SmimeSignOpaqueCommand, "" }, - /* - ** .pp - ** This command is used to created S/MIME signatures of type - ** \fTapplication/x-pkcs7-signature\fP, which can only be handled by mail - ** clients supporting the S/MIME extension. - ** (S/MIME only) - */ - {"smime_encrypt_command", DT_STR, R_NONE, UL &SmimeEncryptCommand, "" }, - /* - ** .pp - ** This command is used to create encrypted S/MIME messages. - ** (S/MIME only) - */ - {"smime_pk7out_command", DT_STR, R_NONE, UL &SmimePk7outCommand, "" }, - /* - ** .pp - ** This command is used to extract PKCS7 structures of S/MIME signatures, - ** in order to extract the public X509 certificate(s). - ** (S/MIME only) - */ - {"smime_get_cert_command", DT_STR, R_NONE, UL &SmimeGetCertCommand, "" }, - /* - ** .pp - ** This command is used to extract X509 certificates from a PKCS7 structure. - ** (S/MIME only) - */ - {"smime_get_signer_cert_command", DT_STR, R_NONE, UL &SmimeGetSignerCertCommand, "" }, - /* - ** .pp - ** This command is used to extract only the signers X509 certificate from a S/MIME - ** signature, so that the certificate's owner may get compared to the - ** email's ``\fTFrom:\fP'' header field. - ** (S/MIME only) - */ - {"smime_import_cert_command", DT_STR, R_NONE, UL &SmimeImportCertCommand, "" }, - /* - ** .pp - ** This command is used to import a certificate via \fTsmime_keysng\fP. - ** (S/MIME only) - */ - {"smime_get_cert_email_command", DT_STR, R_NONE, UL &SmimeGetCertEmailCommand, "" }, - /* - ** .pp - ** This command is used to extract the mail address(es) used for storing - ** X509 certificates, and for verification purposes (to check whether the - ** certificate was issued for the sender's mailbox). - ** (S/MIME only) - */ {"smime_default_key", DT_STR, R_NONE, UL &SmimeDefaultKey, "" }, /* ** .pp @@ -2515,7 +1580,6 @@ struct option_t MuttVars[] = { ** (S/MIME only) */ #if defined(USE_LIBESMTP) - {"smtp_auth_username", DT_SYN, R_NONE, UL "smtp_user", 0}, {"smtp_user", DT_STR, R_NONE, UL &SmtpAuthUser, "" }, /* ** .pp @@ -2523,9 +1587,8 @@ 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, "" }, /* ** .pp @@ -2538,10 +1601,8 @@ struct option_t MuttVars[] = { ** .pp ** \fBNote:\fP Storing passwords in a configuration file ** presents a security risk since the superuser of your machine may read it - ** regardless of the file's permissions. + ** regardless of the file's permissions. */ - {"smtp_envelope", DT_SYN, R_NONE, UL "envelope_from_address", 0 }, - {"smtp_host", DT_STR, R_NONE, UL &SmtpHost, "" }, /* ** .pp @@ -2567,145 +1628,23 @@ struct option_t MuttVars[] = { {"smtp_use_tls", DT_STR, R_NONE, UL &SmtpUseTLS, "" }, /* ** .pp - ** Availability: SMTP (and SSL) + ** Availability: SMTP ** ** .pp ** Defines wether to use STARTTLS. If this option is set to ``\fIrequired\fP'' ** and the server does not support STARTTLS or there is an error in the ** TLS Handshake, the connection will fail. Setting this to ``\fIenabled\fP'' ** 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. */ #endif -#if defined(USE_SSL) || defined(USE_GNUTLS) -#ifdef USE_SSL - {"ssl_client_cert", DT_PATH, R_NONE, UL &SslClientCert, "" }, - /* - ** .pp - ** Availability: SSL - ** - ** .pp - ** The file containing a client certificate and its associated private - ** key. - */ -#endif /* USE_SSL */ - {"ssl_force_tls", DT_BOOL, R_NONE, OPTSSLFORCETLS, "no" }, - /* - ** .pp - ** If this variable is \fIset\fP, Mutt-ng 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 - ** option supersedes ``$$ssl_starttls''. - */ - {"ssl_starttls", DT_QUAD, R_NONE, OPT_SSLSTARTTLS, "yes" }, - /* - ** .pp - ** 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 - ** use STARTTLS regardless of the server's capabilities. - */ - {"certificate_file", DT_PATH, R_NONE, UL &SslCertFile, "~/.mutt_certificates"}, - /* - ** .pp - ** Availability: SSL or GNUTLS - ** - ** .pp - ** This variable specifies the file where the certificates you trust - ** are saved. When an unknown certificate is encountered, you are asked - ** if you accept it or not. If you accept it, the certificate can also - ** be saved in this file and further connections are automatically - ** accepted. - ** .pp - ** You can also manually add CA certificates in this file. Any server - ** certificate that is signed with one of these CA certificates are - ** also automatically accepted. - ** .pp - ** Example: \fTset certificate_file=~/.muttng/certificates\fP - */ -# if defined(_MAKEDOC) || !defined (USE_GNUTLS) - {"ssl_usesystemcerts", DT_BOOL, R_NONE, OPTSSLSYSTEMCERTS, "yes" }, - /* - ** .pp - ** Availability: SSL - ** - ** .pp - ** If set to \fIyes\fP, Mutt-ng will use CA certificates in the - ** system-wide certificate store when checking if server certificate - ** is signed by a trusted CA. - */ - {"entropy_file", DT_PATH, R_NONE, UL &SslEntropyFile, "" }, - /* - ** .pp - ** Availability: SSL - ** - ** .pp - ** The file which includes random data that is used to initialize SSL - ** library functions. - */ - {"ssl_use_sslv2", DT_BOOL, R_NONE, OPTSSLV2, "yes" }, - /* - ** .pp - ** Availability: SSL - ** - ** .pp - ** This variables specifies whether to attempt to use SSLv2 in the - ** SSL authentication process. - */ -# endif /* _MAKEDOC || !USE_GNUTLS */ - {"ssl_use_sslv3", DT_BOOL, R_NONE, OPTSSLV3, "yes" }, - /* - ** .pp - ** Availability: SSL or GNUTLS - ** - ** .pp - ** This variables specifies whether to attempt to use SSLv3 in the - ** SSL authentication process. - */ - {"ssl_use_tlsv1", DT_BOOL, R_NONE, OPTTLSV1, "yes" }, - /* - ** .pp - ** Availability: SSL or GNUTLS - ** - ** .pp - ** This variables specifies whether to attempt to use TLSv1 in the - ** SSL authentication process. - */ -# ifdef USE_GNUTLS - {"ssl_min_dh_prime_bits", DT_NUM, R_NONE, UL &SslDHPrimeBits, "0" }, - /* - ** .pp - ** Availability: GNUTLS - ** - ** .pp - ** This variable specifies the minimum acceptable prime size (in bits) - ** for use in any Diffie-Hellman key exchange. A value of 0 will use - ** the default from the GNUTLS library. - */ - {"ssl_ca_certificates_file", DT_PATH, R_NONE, UL &SslCACertFile, "" }, - /* - ** .pp - ** This variable specifies a file containing trusted CA certificates. - ** Any server certificate that is signed with one of these CA - ** certificates are also automatically accepted. - ** .pp - ** Example: \fTset ssl_ca_certificates_file=/etc/ssl/certs/ca-certificates.crt\fP - */ -# endif /* USE_GNUTLS */ -# endif /* USE_SSL || USE_GNUTLS */ {"pipe_split", DT_BOOL, R_NONE, OPTPIPESPLIT, "no" }, /* ** .pp ** Used in connection with the \fIpipe-message\fP command and the ``tag- - ** prefix'' or ``tag-prefix-cond'' operators. + ** 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. */ @@ -2713,7 +1652,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. */ @@ -2723,60 +1662,35 @@ struct option_t MuttVars[] = { ** The separator to add between messages when piping a list of tagged ** messages to an external Unix command. */ -#ifdef USE_POP {"pop_authenticators", DT_STR, R_NONE, UL &PopAuthenticators, "" }, /* ** .pp - ** Availability: POP - ** - ** .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 */ - {"pop_auth_try_all", DT_BOOL, R_NONE, OPTPOPAUTHTRYALL, "yes" }, - /* - ** .pp - ** Availability: POP - ** - ** .pp - ** If \fIset\fP, Mutt-ng will try all available methods. When \fIunset\fP, Mutt-ng 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. - */ - {"pop_checkinterval", DT_SYN, R_NONE, UL "pop_mail_check", 0}, {"pop_mail_check", DT_NUM, R_NONE, UL &PopCheckTimeout, "60" }, /* ** .pp - ** Availability: POP - ** - ** .pp - ** This variable configures how often (in seconds) POP 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 - ** Availability: POP - ** - ** .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, ""}, /* - ** .pp - ** Availability: POP - ** ** .pp ** The name of your POP server for the ``fetch-mail'' function. You ** can also specify an alternative port, username and password, i.e.: @@ -2790,27 +1704,18 @@ struct option_t MuttVars[] = { {"pop_last", DT_BOOL, R_NONE, OPTPOPLAST, "no" }, /* ** .pp - ** Availability: POP - ** - ** .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 - ** Availability: POP - ** - ** .pp - ** Controls whether or not Mutt-ng will try to reconnect to a POP server when 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, "" }, /* - ** .pp - ** Availability: POP - ** ** .pp ** Your login name on the POP server. ** .pp @@ -2819,23 +1724,13 @@ struct option_t MuttVars[] = { {"pop_pass", DT_STR, R_NONE, UL &PopPass, ""}, /* ** .pp - ** Availability: POP - ** - ** .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 ** presents a security risk since the superuser of your machine may read it ** regardless of the file's permissions. */ -#endif /* USE_POP */ - {"post_indent_string", DT_STR, R_NONE, UL &PostIndentString, ""}, - /* - ** .pp - ** Similar to the ``$$attribution'' variable, Mutt-ng will append this - ** string after the inclusion of a message which is being replied to. - */ #ifdef USE_NNTP {"nntp_post_moderated", DT_QUAD, R_NONE, OPT_TOMODERATED, "ask-yes" }, /* @@ -2843,7 +1738,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 @@ -2860,19 +1755,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. */ -#ifdef USE_SOCKET {"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 @@ -2883,11 +1777,10 @@ struct option_t MuttVars[] = { ** \fBNote:\fP For this example to work, you must be able to log in to the ** remote machine without having to enter a password. */ -#endif /* USE_SOCKET */ {"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. */ @@ -2912,7 +1805,7 @@ struct option_t MuttVars[] = { ** .pp ** Used in connection with the print-message command. If this option ** is \fIset\fP, the command specified by $$print_command is executed once for - ** each message which is to be printed. If this option is \fIunset\fP, + ** each message which is to be printed. If this option is \fIunset\fP, ** the command specified by $$print_command is executed only once, and ** all the messages are concatenated, with a form feed as the message ** separator. @@ -2924,26 +1817,18 @@ 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. */ - {"quit", DT_QUAD, R_NONE, OPT_QUIT, "yes" }, - /* - ** .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 - ** 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. - */ {"quote_empty", DT_BOOL, R_NONE, OPTQUOTEEMPTY, "yes" }, /* ** .pp @@ -2971,9 +1856,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. @@ -3002,23 +1887,12 @@ 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 ** recommended. */ - {"record", DT_PATH, R_NONE, UL &Outbox, ""}, - /* - ** .pp - ** This specifies the file into which your outgoing messages should be - ** appended. (This is meant as the primary method for saving a copy of - ** your messages, but another way to do this is using the ``$my_hdr'' - ** command to create a \fTBcc:\fP header field with your email address in it.) - ** .pp - ** The value of \fI$$record\fP is overridden by the ``$$force_name'' and - ** ``$$save_name'' variables, and the ``$fcc-hook'' command. - */ {"reply_regexp", DT_RX, R_INDEX|R_RESORT, UL &ReplyRegexp, "^(re([\\[0-9\\]+])*|aw):[ \t]*"}, /* ** .pp @@ -3029,17 +1903,17 @@ 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 + ** .pp ** This ** option is useful for reading a mailing list that sets the ``\fTReply-To:\fP'' ** header field to the list address and you want to send a private @@ -3055,7 +1929,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: @@ -3086,131 +1960,10 @@ 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 - ** to save attachments to files named like this: - ** .pp - ** \fT=?iso-8859-1?Q?file=5F=E4=5F991116=2Ezip?=\fP - ** .pp - ** When this variable is \fIset\fP interactively, the change doesn't have - ** the desired effect before you have changed folders. - ** .pp - ** Note that this use of RFC 2047's encoding is explicitly, - ** prohibited by the standard, but nevertheless encountered in the - ** 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 - ** 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 - ** 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. - */ - {"save_empty", DT_BOOL, R_NONE, OPTSAVEEMPTY, "yes" }, - /* - ** .pp - ** When \fIunset\fP, mailboxes which contain no saved messages will be removed - ** 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 - ** delete MH and Maildir directories. - */ - {"save_name", DT_BOOL, R_NONE, OPTSAVENAME, "no" }, - /* - ** .pp - ** This variable controls how copies of outgoing messages are saved. - ** When set, a check is made to see if a mailbox specified by the - ** recipient address exists (this is done by searching for a mailbox in - ** the ``$$folder'' directory with the \fIusername\fP part of the - ** recipient address). If the mailbox exists, the outgoing message will - ** be saved to that mailbox, otherwise the message is saved to the - ** ``$$record'' mailbox. - ** .pp - ** Also see the ``$$force_name'' variable. - */ - {"score", DT_BOOL, R_NONE, OPTSCORE, "yes" }, - /* - ** .pp - ** When this variable is \fIunset\fP, scoring is turned off. This can - ** be useful to selectively disable scoring for certain folders when the - ** ``$$score_threshold_delete'' variable and friends are used. - ** - */ - {"score_threshold_delete", DT_NUM, R_NONE, UL &ScoreThresholdDelete, "-1" }, - /* - ** .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 will never mark a message for deletion. - */ - {"score_threshold_flag", DT_NUM, R_NONE, UL &ScoreThresholdFlag, "9999" }, - /* - ** .pp - ** Messages which have been assigned a score greater than or equal to this - ** variable's value are automatically marked ``flagged''. - */ - {"score_threshold_read", DT_NUM, R_NONE, UL &ScoreThresholdRead, "-1" }, - /* - ** .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 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 - ** 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 - ** appropriate widely used standard character set (such as - ** \fTiso-8859-2\fP, \fTkoi8-r\fP or \fTiso-2022-jp\fP) either - ** instead of or after \fTiso-8859-1\fP. - */ - {"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 - ** arguments as recipient addresses. - */ - {"sendmail_wait", DT_NUM, R_NONE, UL &SendmailWait, "0" }, - /* - ** .pp - ** 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: - ** .dl - ** .dt >0 .dd number of seconds to wait for sendmail to finish before continuing - ** .dt 0 .dd wait forever for sendmail to finish - ** .dt <0 .dd always put sendmail in the background without waiting - ** .de - ** .pp - ** Note that if you specify a value other than 0, the output of the child - ** process will be put in a temporary file. If there is some error, you - ** will be informed as to where to find the output. - */ - {"shell", DT_PATH, R_NONE, UL &Shell, "" }, - /* - ** .pp - ** Command to use when spawning a subshell. By default, the user's login - ** shell from \fT/etc/passwd\fP is used. - */ #ifdef USE_NNTP {"nntp_save_unsubscribed", DT_BOOL, R_NONE, OPTSAVEUNSUB, "no" }, /* @@ -3253,43 +2006,27 @@ 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" }, - /* - ** .pp - ** If \fIset\fP, the signature will be included before any quoted or forwarded - ** text. It is \fBstrongly\fP recommended that you do not set this variable - ** unless you really know what you are doing, and are prepared to take - ** some heat from netiquette guardians. - */ - {"signature", DT_PATH, R_NONE, UL &Signature, "~/.signature"}, - /* - ** .pp - ** Specifies the filename of your signature, which is appended to all - ** outgoing messages. If the filename ends with a pipe (``\fT|\fP''), it is - ** assumed that filename is a shell command and input should be read from - ** its stdout. - */ {"signoff_string", DT_STR, R_NONE, UL &SignOffString, "" }, /* ** .pp ** If \fIset\fP, this string will be inserted before the signature. This is useful ** for people that want to sign off every message they send with their name. ** .pp - ** If you want to insert your website's URL, additional contact information or + ** If you want to insert your website's URL, additional contact information or ** witty quotes into your mails, better use a signature file instead of ** the signoff string. */ {"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 @@ -3315,7 +2052,7 @@ struct option_t MuttVars[] = { ** .pp ** Specifies time, in seconds, to pause while displaying certain informational ** messages, while moving from folder to folder and after expunging - ** messages from the current folder. The default is to pause one second, so + ** messages from the current folder. The default is to pause one second, so ** a value of zero for this option suppresses the pause. */ {"sort", DT_SORT, R_INDEX|R_RESORT, UL &Sort, "date" }, @@ -3358,7 +2095,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 @@ -3393,27 +2130,18 @@ 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, ","}, - /* - ** .pp - ** ``$spam_separator'' controls what happens when multiple spam headers - ** are matched: if \fIunset\fP, each successive header will overwrite any - ** previous matches value for the spam label. If \fIset\fP, each successive - ** match will append to the previous, using ``$spam_separator'' as a - ** separator. - */ {"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. */ @@ -3431,7 +2159,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 @@ -3446,7 +2174,7 @@ struct option_t MuttVars[] = { ** .dt %F .dd number of flagged messages * ** .dt %h .dd local hostname ** .dt %l .dd size (in bytes) of the current mailbox * - ** .dt %L .dd size (in bytes) of the messages shown + ** .dt %L .dd size (in bytes) of the messages shown ** (i.e., which match the current limit) * ** .dt %m .dd the number of messages in the mailbox * ** .dt %M .dd the number of messages shown (i.e., which match the current limit) * @@ -3460,7 +2188,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" @@ -3500,8 +2228,8 @@ struct option_t MuttVars[] = { ** .pp ** \fT%_h\fP ** .pp - ** If you prefix the sequence character with a colon (\fT:\fP) character, Mutt-ng - ** will replace any dots in the expansion by underscores. This might be helpful + ** 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. */ {"status_on_top", DT_BOOL, R_BOTH, OPTSTATUSONTOP, "no" }, @@ -3519,24 +2247,11 @@ 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. **/ - {"strict_mime", DT_BOOL, R_NONE, OPTSTRICTMIME, "yes" }, - /* - ** .pp - ** When \fIunset\fP, non MIME-compliant messages that doesn't have any - ** charset indication in the ``\fTContent-Type:\fP'' header field can - ** be displayed (non MIME-compliant messages are often generated by old - ** mailers or buggy mailers like MS Outlook Express). - ** See also $$assumed_charset. - ** .pp - ** This option also replaces linear-white-space between encoded-word - ** and *text to a single space to prevent the display of MIME-encoded - ** ``\fTSubject:\fP'' header field from being devided into multiple lines. - */ {"strict_threads", DT_BOOL, R_RESORT|R_RESORT_INIT|R_INDEX, OPTSTRICTTHREADS, "no" }, /* ** .pp @@ -3552,14 +2267,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. **/ @@ -3573,16 +2288,16 @@ 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 - ** inside an xterm using a command like ``\fTxterm -e muttng\fP.'' + ** 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 + ** just looks like ordinary text. To actually make use of this format's ** features, you'll need support in your editor. ** .pp ** Note that $$indent_string is ignored when this option is set. @@ -3590,7 +2305,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" }, @@ -3610,19 +2325,11 @@ 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 - ** 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. - */ {"to_chars", DT_STR, R_BOTH, UL &Tochars, " +TCFL"}, /* ** .pp @@ -3647,11 +2354,10 @@ struct option_t MuttVars[] = { ** \fBNote\fP: When you delete a message in the trash folder, it is really ** deleted, so that there is no way to recover mail. */ -#ifdef USE_SOCKET {"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 @@ -3660,36 +2366,16 @@ struct option_t MuttVars[] = { ** \fBNote:\fP For this example to work you must be able to log in to the remote ** machine without having to enter a password. */ -#endif {"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" }, - /* - ** .pp - ** \fBWarning:\fP do not set this variable unless you are using a version - ** of sendmail which supports the \fT-B8BITMIME\fP flag (such as sendmail - ** 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 - ** 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 - ** @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. @@ -3701,39 +2387,30 @@ 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. */ #endif /* HAVE_LIBIDN */ -#ifdef HAVE_GETADDRINFO {"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 */ - {"user_agent", DT_SYN, R_NONE, UL "agent_string", 0 }, {"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. */ - {"visual", DT_PATH, R_NONE, UL &Visual, "" }, - /* - ** .pp - ** Specifies the visual editor to invoke when the \fI~v\fP command is - ** given in the builtin editor. - */ {"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 @@ -3741,13 +2418,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" }, @@ -3762,7 +2439,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" }, /* @@ -3776,7 +2453,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?"}, @@ -3789,7 +2466,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. */ @@ -3797,8 +2474,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 @@ -3807,7 +2484,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 @@ -3821,242 +2498,126 @@ struct option_t MuttVars[] = { ** Availability: NNTP ** ** .pp - ** If \fIset\fP, Mutt-ng will add a ``\fTX-Comment-To:\fP'' header field - ** (that contains full name of the original article author) to articles that + ** 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. */ #endif /*--*/ - { NULL } -}; - -static const char* Features[] = { -#ifdef NCURSES_VERSION - "ncurses", -#endif -#ifdef USE_SLANG_CURSES - "slang", -#endif -#ifdef _LIBICONV_VERSION - "iconv", -#endif -#ifdef HAVE_LIBIDN - "idn", -#endif -#ifdef USE_DOTLOCK - "dotlock", -#endif -#ifdef DL_STANDALONE - "standalone", -#endif -#ifdef USE_POP - "pop", -#endif -#ifdef USE_NNTP - "nntp", -#endif -#ifdef USE_IMAP - "imap", -#endif -#ifdef USE_SSL - "ssl", -#endif -#ifdef USE_GNUTLS - "gnutls", -#endif -#ifdef USE_SASL - "sasl", -#endif -#ifdef USE_LIBESMTP - "libesmtp", -#endif -#ifdef USE_COMPRESSED - "compessed", -#endif -#ifdef HAVE_COLOR - "color", -#endif -#ifdef CRYPT_BACKEND_CLASSIC_PGP - "classic_pgp", -#endif -#ifdef CRYPT_BACKEND_CLASSIC_SMIME - "class_smime", -#endif -#ifdef CRYPT_BACKEND_GPGME - "gpgme", -#endif -#ifdef USE_HCACHE - "header_cache", -#endif -#ifdef HAVE_QDBM - "qdbm", -#endif -#ifdef HAVE_GDBM - "gdbm", -#endif -#ifdef HAVE_DB4 - "db4", -#endif - /* last */ - NULL + { NULL, -1, R_NONE, -1, NULL } }; const struct mapping_t SortMethods[] = { - {"date", SORT_DATE}, - {"date-sent", SORT_DATE}, - {"date-received", SORT_RECEIVED}, - {"mailbox-order", SORT_ORDER}, - {"subject", SORT_SUBJECT}, - {"from", SORT_FROM}, - {"size", SORT_SIZE}, - {"threads", SORT_THREADS}, - {"to", SORT_TO}, - {"score", SORT_SCORE}, - {"spam", SORT_SPAM}, - {NULL, 0} + {"date", SORT_DATE}, + {"date-sent", SORT_DATE}, + {"date-received", SORT_RECEIVED}, + {"mailbox-order", SORT_ORDER}, + {"subject", SORT_SUBJECT}, + {"from", SORT_FROM}, + {"size", SORT_SIZE}, + {"threads", SORT_THREADS}, + {"to", SORT_TO}, + {"score", SORT_SCORE}, + {"spam", SORT_SPAM}, + {NULL, 0} }; /* same as SortMethods, but with "threads" replaced by "date" */ const struct mapping_t SortAuxMethods[] = { - {"date", SORT_DATE}, - {"date-sent", SORT_DATE}, - {"date-received", SORT_RECEIVED}, - {"mailbox-order", SORT_ORDER}, - {"subject", SORT_SUBJECT}, - {"from", SORT_FROM}, - {"size", SORT_SIZE}, - {"threads", SORT_DATE}, /* note: sort_aux == threads - * isn't possible. - */ - {"to", SORT_TO}, - {"score", SORT_SCORE}, - {"spam", SORT_SPAM}, - {NULL, 0} + {"date", SORT_DATE}, + {"date-sent", SORT_DATE}, + {"date-received", SORT_RECEIVED}, + {"mailbox-order", SORT_ORDER}, + {"subject", SORT_SUBJECT}, + {"from", SORT_FROM}, + {"size", SORT_SIZE}, + {"threads", SORT_DATE}, /* note: sort_aux == threads + * isn't possible. + */ + {"to", SORT_TO}, + {"score", SORT_SCORE}, + {"spam", SORT_SPAM}, + {NULL, 0} }; const struct mapping_t SortBrowserMethods[] = { - {"alpha", SORT_SUBJECT}, - {"date", SORT_DATE}, - {"size", SORT_SIZE}, - {"unsorted", SORT_ORDER}, - {NULL} + {"alpha", SORT_SUBJECT}, + {"date", SORT_DATE}, + {"size", SORT_SIZE}, + {"unsorted", SORT_ORDER}, + {NULL, 0} }; const struct mapping_t SortAliasMethods[] = { - {"alias", SORT_ALIAS}, - {"address", SORT_ADDRESS}, - {"unsorted", SORT_ORDER}, - {NULL} + {"alias", SORT_ALIAS}, + {"address", SORT_ADDRESS}, + {"unsorted", SORT_ORDER}, + {NULL, 0} }; const struct mapping_t SortKeyMethods[] = { - {"address", SORT_ADDRESS}, - {"date", SORT_DATE}, - {"keyid", SORT_KEYID}, - {"trust", SORT_TRUST}, - {NULL} + {"address", SORT_ADDRESS}, + {"date", SORT_DATE}, + {"keyid", SORT_KEYID}, + {"trust", SORT_TRUST}, + {NULL, 0} }; /* functions used to parse commands in a rc file */ -static int parse_list (BUFFER *, BUFFER *, unsigned long, BUFFER *); -static int parse_spam_list (BUFFER *, BUFFER *, unsigned long, BUFFER *); -static int parse_unlist (BUFFER *, BUFFER *, unsigned long, BUFFER *); - -static int parse_lists (BUFFER *, BUFFER *, unsigned long, BUFFER *); -static int parse_unlists (BUFFER *, BUFFER *, unsigned long, BUFFER *); +static int parse_attachments (BUFFER *, BUFFER *, unsigned long, BUFFER *); +static int parse_unattachments (BUFFER *, BUFFER *, unsigned long, BUFFER *); static int parse_alias (BUFFER *, BUFFER *, unsigned long, BUFFER *); static int parse_unalias (BUFFER *, BUFFER *, unsigned long, BUFFER *); -static int parse_ifdef (BUFFER *, BUFFER *, unsigned long, BUFFER *); -static int parse_ignore (BUFFER *, BUFFER *, unsigned long, BUFFER *); -static int parse_unignore (BUFFER *, BUFFER *, unsigned long, BUFFER *); static int parse_source (BUFFER *, BUFFER *, unsigned long, BUFFER *); static int parse_set (BUFFER *, BUFFER *, unsigned long, BUFFER *); static int parse_my_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *); static int parse_unmy_hdr (BUFFER *, BUFFER *, unsigned long, BUFFER *); -static int parse_subscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *); -static int parse_unsubscribe (BUFFER *, BUFFER *, unsigned long, BUFFER *); - -static int parse_alternates (BUFFER *, BUFFER *, unsigned long, BUFFER *); -static int parse_unalternates (BUFFER *, BUFFER *, unsigned long, BUFFER *); struct command_t { - char *name; - int (*func) (BUFFER *, BUFFER *, unsigned long, BUFFER *); - unsigned long data; - unsigned long data1; + const char *name; + int (*func) (BUFFER *, BUFFER *, unsigned long, BUFFER *); + unsigned long data; }; struct command_t Commands[] = { - {"alternates", parse_alternates, 0}, - {"unalternates", parse_unalternates, 0}, -#ifdef USE_SOCKET - {"account-hook", mutt_parse_hook, M_ACCOUNTHOOK}, -#endif - {"alias", parse_alias, 0}, - {"auto_view", parse_list, UL &AutoViewList}, - {"alternative_order", parse_list, UL &AlternativeOrderList}, - {"bind", mutt_parse_bind, 0}, - {"charset-hook", mutt_parse_hook, M_CHARSETHOOK}, -#ifdef HAVE_COLOR - {"color", mutt_parse_color, 0}, - {"uncolor", mutt_parse_uncolor, 0}, -#endif - {"exec", mutt_parse_exec, 0}, - {"fcc-hook", mutt_parse_hook, M_FCCHOOK}, - {"fcc-save-hook", mutt_parse_hook, M_FCCHOOK|M_SAVEHOOK}, - {"folder-hook", mutt_parse_hook, M_FOLDERHOOK}, -#ifdef USE_COMPRESSED - {"open-hook", mutt_parse_hook, M_OPENHOOK}, - {"close-hook", mutt_parse_hook, M_CLOSEHOOK}, - {"append-hook", mutt_parse_hook, M_APPENDHOOK}, -#endif - {"hdr_order", parse_list, UL &HeaderOrderList}, - {"ifdef", parse_ifdef, 1}, - {"ifndef", parse_ifdef, 0}, -#ifdef HAVE_ICONV - {"iconv-hook", mutt_parse_hook, M_ICONVHOOK}, -#endif - {"ignore", parse_ignore, 0}, - {"lists", parse_lists, 0}, - {"macro", mutt_parse_macro, 0}, - {"mailboxes", buffy_parse_mailboxes, M_MAILBOXES}, - {"unmailboxes", buffy_parse_mailboxes, M_UNMAILBOXES}, - {"message-hook", mutt_parse_hook, M_MESSAGEHOOK}, - {"mbox-hook", mutt_parse_hook, M_MBOXHOOK}, - {"mime_lookup", parse_list, UL &MimeLookupList}, - {"unmime_lookup", parse_unlist, UL &MimeLookupList}, - {"mono", mutt_parse_mono, 0}, - {"my_hdr", parse_my_hdr, 0}, - {"pgp-hook", mutt_parse_hook, M_CRYPTHOOK}, - {"crypt-hook", mutt_parse_hook, M_CRYPTHOOK}, - {"push", mutt_parse_push, 0}, - {"reply-hook", mutt_parse_hook, M_REPLYHOOK}, - {"reset", parse_set, M_SET_RESET}, - {"save-hook", mutt_parse_hook, M_SAVEHOOK}, - {"score", mutt_parse_score, 0}, - {"send-hook", mutt_parse_hook, M_SENDHOOK}, - {"send2-hook", mutt_parse_hook, M_SEND2HOOK}, - {"set", parse_set, 0}, - {"source", parse_source, 0}, - {"spam", parse_spam_list, M_SPAM}, - {"nospam", parse_spam_list, M_NOSPAM}, - {"subscribe", parse_subscribe, 0}, - {"toggle", parse_set, M_SET_INV}, - {"unalias", parse_unalias, 0}, - {"unalternative_order", parse_unlist, UL &AlternativeOrderList}, - {"unauto_view", parse_unlist, UL &AutoViewList}, - {"unhdr_order", parse_unlist, UL &HeaderOrderList}, - {"unhook", mutt_parse_unhook, 0}, - {"unignore", parse_unignore, 0}, - {"unlists", parse_unlists, 0}, - {"unmono", mutt_parse_unmono, 0}, - {"unmy_hdr", parse_unmy_hdr, 0}, - {"unscore", mutt_parse_unscore, 0}, - {"unset", parse_set, M_SET_UNSET}, - {"unsubscribe", parse_unsubscribe, 0}, - {NULL} + {"bind", mutt_parse_bind, 0}, + {"color", mutt_parse_color, 0}, + {"exec", mutt_parse_exec, 0}, + {"account-hook", mutt_parse_hook, M_ACCOUNTHOOK}, + {"append-hook", mutt_parse_hook, M_APPENDHOOK}, + {"close-hook", mutt_parse_hook, M_CLOSEHOOK}, + {"crypt-hook", mutt_parse_hook, M_CRYPTHOOK}, + {"fcc-hook", mutt_parse_hook, M_FCCHOOK}, + {"fcc-save-hook", mutt_parse_hook, M_FCCHOOK|M_SAVEHOOK}, + {"folder-hook", mutt_parse_hook, M_FOLDERHOOK}, + {"mbox-hook", mutt_parse_hook, M_MBOXHOOK}, + {"message-hook", mutt_parse_hook, M_MESSAGEHOOK}, + {"open-hook", mutt_parse_hook, M_OPENHOOK}, + {"pgp-hook", mutt_parse_hook, M_CRYPTHOOK}, + {"reply-hook", mutt_parse_hook, M_REPLYHOOK}, + {"save-hook", mutt_parse_hook, M_SAVEHOOK}, + {"send2-hook", mutt_parse_hook, M_SEND2HOOK}, + {"send-hook", mutt_parse_hook, M_SENDHOOK}, + {"macro", mutt_parse_macro, 0}, + {"mono", mutt_parse_mono, 0}, + {"push", mutt_parse_push, 0}, + {"uncolor", mutt_parse_uncolor, 0}, + {"unhook", mutt_parse_unhook, 0}, + {"unmono", mutt_parse_unmono, 0}, + {"alias", parse_alias, 0}, + {"attachments", parse_attachments, 0 }, + {"my_hdr", parse_my_hdr, 0}, + {"reset", parse_set, M_SET_RESET}, + {"set", parse_set, 0}, + {"toggle", parse_set, M_SET_INV}, + {"unset", parse_set, M_SET_UNSET}, + {"source", parse_source, 0}, + {"unalias", parse_unalias, 0}, + {"unattachments", parse_unattachments, 0}, + {"unmy_hdr", parse_unmy_hdr, 0}, + {NULL, NULL, 0} };