Hi,

* Russell L. Harris [02-07-30 08:39:13 +0200] wrote:
> * muttrc contains the entire set of mutt configuration
> variables (variables not applicable to the particular
> installation may be commented out, using #)

Hmm, I don't think this is really necessary because of two
reasons. First of all, one doesn't need every variable to be
set; second, I wouldn't switch to mutt if the first thing I
saw was a file containing ~200 variables with lots of
comments. But in fact, that's what the manual is for: sorted
by category with good explanations instead of a short
comment. If you like, just take manual.txt and reorder the
variables in section 6.

[...]

> Are there drawbacks to such a scheme?  Would anyone be
> interested in posting a copy of the commented
> configuration file?  Would this project have the blessing
> of the author of mutt?

There's a muttrcbuilder on the web which does produces
muttrcs while variables are sorted by categories. Those
people will certainly be interested in what you have to
contribute.

> I have begun categorizing the configuration variables.  I
> solicit comments and recommendations.

Lots of people do it. But organizing muttrc highly depends
on personal tasts and such.

   bye, Rocco

Reply via email to