X-Git-Url: http://git.madism.org/?a=blobdiff_plain;ds=sidebyside;f=init.h;h=fdad6665fc22284c4f477cdd7aa55092733bf346;hb=7dcd7ee09b8760133ac8ec00562e4d60b2f0aebd;hp=70ba04e116d90a7ca59c642b2f0a7e73cc08faac;hpb=5fbd8a74d24624a118c9b835b136c73b8da076d7;p=apps%2Fmadmutt.git diff --git a/init.h b/init.h index 70ba04e..fdad666 100644 --- a/init.h +++ b/init.h @@ -108,17 +108,6 @@ struct option_t MuttVars[] = { ** 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. - */ {"askbcc", DT_BOOL, R_NONE, OPTASKBCC, "no" }, /* ** .pp @@ -223,15 +212,6 @@ struct option_t MuttVars[] = { ** \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 @@ -549,18 +529,6 @@ struct option_t MuttVars[] = { ** 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 @@ -953,12 +921,6 @@ struct option_t MuttVars[] = { ** 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 @@ -1030,21 +992,6 @@ struct option_t MuttVars[] = { ** 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). - */ {"mh_purge", DT_BOOL, R_NONE, OPTMHPURGE, "no" }, /* ** .pp @@ -1478,11 +1425,6 @@ struct option_t MuttVars[] = { ** .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 @@ -1511,13 +1453,6 @@ struct option_t MuttVars[] = { ** 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 @@ -1810,12 +1745,6 @@ struct option_t MuttVars[] = { ** 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" }, /* ** @@ -1863,13 +1792,6 @@ struct option_t MuttVars[] = { ** 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 @@ -1971,13 +1893,6 @@ struct option_t MuttVars[] = { ** 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