Hi there!
I am using the latest from the CVS (1.5.0i). Is there a way to have mutt
'spit' out all the possible .muttrc variables? Something like a command line
option, so it will create a .muttrc with all the defaults and/or empty ones?
TIA and cheers,
--
David Collantes - http
* David Collantes [EMAIL PROTECTED] [2002-04-05 16:30]:
I am using the latest from the CVS (1.5.0i). Is there a way
to have mutt 'spit' out all the possible .muttrc variables?
Something like a command line option, so it will create
a .muttrc with all the defaults and/or empty ones?
http
Sven Guckes wrote:
## Trivia: mutt-1.2.5 has some 208 options.
## mutt-1.3.27 now has 249 options.
## mutt-1.3.28 has 249 options, too.
## Check with grep DT_ init.h| grep -v define | sort |less
This is not entirely accurrate unless you grep -v DT_SYN
On 04-05-2002 at 12:14 EST, Michael Elkins [EMAIL PROTECTED] wrote:
Sven Guckes wrote:
## Trivia: mutt-1.2.5 has some 208 options.
## mutt-1.3.27 now has 249 options.
## mutt-1.3.28 has 249 options, too.
## Check with grep DT_ init.h| grep -v define |
Hi,
* David Collantes [04/05/02 19:22:13] wrote:
[ dump config ]
Will this be useful to more people? Is it something worth to ask as a wish?
For me, it will be nice it I could:
$ mutt --dump-vars
And have a .muttrc-full some something dumped on my directory, with all
options and their
Rocco Rutte wrote:
It would make sence. Even more usefull was a feature which Postfix has:
dump all configuration variables which are not default.
I can image it would make it easier to track errors by misconfiguration
down.
i was actually going to suggest this a long time ago, but
