* Russell L. Harris <[EMAIL PROTECTED]> [2002-07-30 06:22]: > I am a mutt newbie. It seems to me that > configuration of mutt would be easier if: > * muttrc contains the entire set of mutt > configuration variables
are you saying that there are options missing in the manual? if so then please send in a bug report using "flea". > (variables not applicable to the particular > installation may be commented out, using #) you want manuals which depend on the current installation? what about systems which more than one mutt binary? my point: this won't work. > * the configuration variables are grouped in categories.. Been there, done that, got the tshirt. but that was some five years ago. > * each variable would be accompanied by a brief > comment regarding applicability and proper usage examples? well, you can fill manuals with billions of examples - but then the real power is with combining them with other options. and that's where online setup files can help more. > Are there drawbacks to such a scheme? yes. copy cats will simply rely on the examples without thinking. but we usually send these people over to the pine folks. hehehe > I have begun categorizing the configuration variables. > I solicit comments and recommendations. > Would anyone be interested in posting a copy > of the commented configuration file? please don't post huse setup files onto this list, thankyou. instead, upload it to your webserver and post the url. Sven -- Sven Guckes http://www.math.fu-berlin.de/~guckes/mutt/setup.html Mutt setup from scratch, Sven's sample setup; attribution, "limit", "list" vs "subscribe", histories, mailcap, POP, hooks, use of external pagers, troubleshooting, adding header lines, "from Mozilla to Mutt".
