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 (variables
not applicable to the particular installation may be commented out, using #)
* the configuration variables are grouped in categories,
--8P1HSweYDcXXzwPJ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
Alas! Russell L. Harris spake thus:
I am a mutt newbie. It seems to me that configuration of mutt would be=
=20
easier if:
=20
* muttrc contains the entire
* 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
On Tue, Jul 30, 2002 at 10:22:43 +0200, Sven Guckes wrote:
* Russell L. Harris [EMAIL PROTECTED] [2002-07-30 06:22]:
(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
* Vincent Lefevre [EMAIL PROTECTED] [2002-07-30 09:29]:
On Tue, Jul 30, 2002 at 10:22:43 +0200, Sven Guckes wrote:
* Russell L. Harris [EMAIL PROTECTED] [2002-07-30 06:22]:
(variables not applicable to the particular
installation may be commented out, using #)
you want manuals which
On Tue, Jul 30, 2002 at 14:40:00 +0200, Sven Guckes wrote:
a better way is that of vim which includes the info
that the option/variable is only available when
some code is in binary as indicated by +feature
in the outut of the :version command.
Yes, we should have something like that in
