** Controls whether 8-bit data is converted to 7-bit using either
** \fTquoted-printable\fP or \fTbase64\fP encoding when sending mail.
*/
- {"allow_ansi", DT_BOOL, R_NONE, OPTALLOWANSI, "no" },
- /*
- ** .pp
- ** 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
- ** your color choices, and even present a security problem, since a
- ** message could include a line like ``\fT[-- PGP output follows ...\fP" and
- ** give it the same color as your attachment color.
- */
- {"ascii_chars", DT_BOOL, R_BOTH, OPTASCIICHARS, "no" },
- /*
- ** .pp
- ** 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
** \fTDelivered-To:\fP header fields when bouncing messages.
** Postfix users may wish to \fIunset\fP this variable.
*/
- { "braille_friendly", DT_BOOL, R_NONE, OPTBRAILLEFRIENDLY, "no" },
- /*
- ** .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
- ** visual terminals don't permit making the cursor invisible.
- */
{"check_new", DT_BOOL, R_NONE, OPTCHECKNEW, "yes" },
/*
** .pp
** of the message you are replying to into the edit buffer.
** The ``$$weed'' setting applies.
*/
- {"help", DT_BOOL, R_BOTH, OPTHELP, "yes" },
- /*
- ** .pp
- ** When \fIset\fP, help lines describing the bindings for the major functions
- ** provided by each menu are displayed on the first line of the screen.
- ** .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 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
** 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.
*/
-#ifdef USE_HCACHE
- {"header_cache", DT_PATH, R_NONE, UL &HeaderCache, "~/.cache/madmutt/" },
- /*
- ** .pp
- ** Availability: Header Cache
- **
- ** .pp
- ** The $$header_cache variable points to the header cache database.
- ** .pp
- ** If $$header_cache points to a directory it will contain a header cache
- ** database per folder. If $$header_cache points to a file that file will
- ** be a single global header cache. By default it is \fIunset\fP so no
- ** header caching will be used.
- */
-#if defined(HAVE_GDBM)
- {"header_cache_pagesize", DT_STR, R_NONE, UL &HeaderCachePageSize, "16384"},
- /*
- ** .pp
- ** Availability: Header Cache
- **
- ** .pp
- ** Change the maildir header cache database page size.
- ** .pp
- ** Too large
- ** or too small of a page size for the common header can waste
- ** space, memory effectiveness, or CPU time. The default should be more or
- ** less the best you can get. For details google for mutt header
- ** cache (first hit).
- */
-#endif /* HAVE_GDBM */
-#ifdef HAVE_QDBM
- { "header_cache_compress", DT_BOOL, R_NONE, OPTHCACHECOMPRESS, "no" },
- /*
- ** .pp
- ** If enabled the header cache will be compressed. So only one fifth of the usual
- ** diskspace is used, but the uncompression can result in a slower open of the
- ** cached folder.
- */
-#endif /* HAVE_QDBM */
-#endif /* USE_HCACHE */
{"maildir_trash", DT_BOOL, R_NONE, OPTMAILDIRTRASH, "no" },
/*
** .pp
** variable specifies the characters at which to split a folder name into
** ``hierarchy items.''
*/
- {"sidebar_delim", DT_STR, R_BOTH, UL &SidebarDelim, "|"},
- /*
- ** .pp
- ** This specifies the delimiter between the sidebar (if visible) and
- ** other screens.
- */
{"sidebar_visible", DT_BOOL, R_BOTH, OPTMBOXPANE, "no" },
/*
** .pp
** This variable controls the number of lines of context that are given
** when scrolling through menus. (Similar to ``$$pager_context''.)
*/
- {"menu_move_off", DT_BOOL, R_NONE, OPTMENUMOVEOFF, "yes" },
- /*
- ** .pp
- ** When \fIunset\fP, the bottom entry of menus will never scroll up past
- ** the bottom of the screen, unless there are less entries than lines.
- ** When \fIset\fP, the bottom entry may move off the bottom.
- */
- {"menu_scroll", DT_BOOL, R_NONE, OPTMENUSCROLL, "no" },
- /*
- ** .pp
- ** When \fIset\fP, menus will be scrolled up or down one line when you
- ** attempt to move across a screen boundary. If \fIunset\fP, the screen
- ** is cleared and the next or previous page of the menu is displayed
- ** (useful for slow links to avoid many redraws).
- */
- {"meta_key", DT_BOOL, R_NONE, OPTMETAKEY, "no" },
- /*
- ** .pp
- ** If \fIset\fP, forces Madmutt to interpret keystrokes with the high bit (bit 8)
- ** set as if the user had pressed the \fTESC\fP key and whatever key remains
- ** after having the high bit removed. For example, if the key pressed
- ** has an ASCII value of \fT0xf8\fP, then this is treated as if the user had
- ** pressed \fTESC\fP then ``\fTx\fP''. This is because the result of removing the
- ** high bit from ``\fT0xf8\fP'' is ``\fT0x78\fP'', which is the ASCII character
- ** ``\fTx\fP''.
- */
{"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, "no" },
/*
** .pp
** menu, attachments which cannot be decoded in a reasonable manner will
** be attached to the newly composed message if this option is set.
*/
- {"mix_entry_format", DT_STR, R_NONE, UL &MixEntryFormat, "%4n %c %-16s %a"},
- /*
- ** .pp
- ** This variable describes the format of a remailer line on the mixmaster
- ** chain selection screen. The following \fTprintf(3)\fP-like sequences are
- ** supported:
- ** .pp
- ** .dl
- ** .dt %n .dd The running number on the menu.
- ** .dt %c .dd Remailer capabilities.
- ** .dt %s .dd The remailer's short name.
- ** .dt %a .dd The remailer's e-mail address.
- ** .de
- */
- {"mixmaster", DT_PATH, R_NONE, UL &Mixmaster, 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.
- */
{"move", DT_QUAD, R_NONE, OPT_MOVE, "ask-no" },
/*
** .pp
** .pp
** Also see the ``$$write_inc'' variable.
*/
- {"read_only", DT_BOOL, R_NONE, OPTREADONLY, "no" },
- /*
- ** .pp
- ** If set, all folders are opened in read-only mode.
- */
{"realname", DT_STR, R_BOTH, UL &Realname, "" },
/*
** .pp
** and replying. The default value corresponds to the English ``Re:'' and
** the German ``Aw:''.
*/
- {"reply_self", DT_BOOL, R_NONE, OPTREPLYSELF, "no" },
- /*
- ** .pp
- ** 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
** 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" },
- /*
- ** .pp
- ** Setting this variable causes the ``status bar'' to be displayed on
- ** the first line of the screen rather than near the bottom.
- */
{"strict_mailto", DT_BOOL, R_NONE, OPTSTRICTMAILTO, "yes" },
/*
**
** i.e. a space will be inserted between the quote characters and the actual
** text.
*/
- {"suspend", DT_BOOL, R_NONE, OPTSUSPEND, "yes" },
- /*
- ** .pp
- ** 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
** This variable only affects decoding.
*/
#endif /* HAVE_LIBIDN */
- {"use_ipv6", DT_BOOL, R_NONE, OPTUSEIPV6, "yes" },
- /*
- ** .pp
- ** 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.
- */
{"agent_string", DT_BOOL, R_NONE, OPTXMAILER, "yes" },
/*
** .pp
** does not support posting to that newsgroup or a group is totally read-only, that
** posting will not have any effect.
*/
- {"nntp_cache_dir", DT_PATH, R_NONE, UL &NewsCacheDir, "~/.cache/madmutt/"},
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** 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
- ** As for the header caching in connection with IMAP and/or Maildir,
- ** this drastically increases speed and lowers traffic.
- */
{"nntp_host", DT_STR, R_NONE, UL &NewsServer, "" },
/*
** .pp
** presents a security risk since the superuser of your machine may read it
** regardless of the file's permissions.
*/
- {"nntp_newsrc", DT_PATH, R_NONE, UL &NewsRc, "~/.cache/madmutt/newsrc"},
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** This file contains information about subscribed newsgroup and
- ** articles read so far.
- ** .pp
- ** To ease the use of multiple news servers, the following \fTprintf(3)\fP-style
- ** sequence is understood:
- ** .pp
- ** .ts
- ** %s newsserver name
- ** .te
- */
{"nntp_context", DT_NUM, R_NONE, UL &NntpContext, "1000" },
/*
** .pp
** Controls whether or not Madmutt will try to reconnect to a newsserver when the
** was connection lost.
*/
- {"nntp_inews", DT_PATH, R_NONE, UL &Inews, ""},
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** If \fIset\fP, specifies the program and arguments used to deliver news posted
- ** by Madmutt. Otherwise, Madmutt posts article using current connection.
- ** The following \fTprintf(3)\fP-style sequence is understood:
- ** .pp
- ** .ts
- ** %s newsserver name
- ** .te
- ** .pp
- ** Example: \fTset inews="/usr/local/bin/inews -hS"\fP
- */
{"nntp_group_index_format", DT_STR, R_BOTH, UL &GroupFormat, "%4C %M%N %5s %-45.45f %d"},
/*
** .pp
** If \fIset\fP, Madmutt will prompt you for the \fTFollowup-To:\fP header
** field before editing the body of an outgoing news article.
*/
- {"nntp_save_unsubscribed", DT_BOOL, R_NONE, OPTSAVEUNSUB, "no" },
- /*
- ** .pp
- ** Availability: NNTP
- **
- ** .pp
- ** When \fIset\fP, info about unsubscribed newsgroups will be saved into the
- ** ``newsrc'' file and into the news cache.
- */
{"nntp_show_new_news", DT_BOOL, R_NONE, OPTSHOWNEWNEWS, "yes" },
/*
** .pp