X-Git-Url: http://git.madism.org/?p=apps%2Fmadmutt.git;a=blobdiff_plain;f=init.h;h=64e7db17e6d9991c9312d57af289852e82f399c1;hp=c20fd52d7467c8e2f91a7f2030c5390d991bbd12;hb=8c3ace92538b826576b892108b8f5eb6d68e62cc;hpb=3cff23a6fb2bdd6e49fc1d67d50e5438a9149dad

diff --git a/init.h b/init.h
index c20fd52..64e7db1 100644
--- a/init.h
+++ b/init.h
@@ -119,12 +119,6 @@ struct option_t MuttVars[] = {
    ** 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
@@ -555,18 +549,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
@@ -884,19 +866,6 @@ struct option_t MuttVars[] = {
    ** 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"},
   /*
@@ -972,12 +941,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
@@ -1064,17 +1027,6 @@ struct option_t MuttVars[] = {
    ** 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
@@ -1126,28 +1078,6 @@ 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.
    */
-  {"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
@@ -2135,19 +2065,6 @@ struct option_t MuttVars[] = {
    ** 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
@@ -2169,22 +2086,6 @@ struct option_t MuttVars[] = {
    ** 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
@@ -2247,22 +2148,6 @@ struct option_t MuttVars[] = {
    ** 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
@@ -2314,15 +2199,6 @@ struct option_t MuttVars[] = {
    ** 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