On 2000-03-01 23:09:22 +1100, Chuck Dale wrote:
> <RandomRant generality="waytoohigh">
>
> The problem (as I see it) is that .muttrc goes against the principles
> which Mutt is following. Particularly in modularisation. The .muttrc
> contains absolutely everything configurable in the program - it defines
> the interface (keys, column presentation, folder hooks, colours), mail transfer
> (sendmail settings, mailboxes which receive mail), personal settings
> (real name, personal headers) and a few other random settings as well.
>
> </RandomRant>
Actually it doesn't have to have anything at all. You can get by with
no .muttrc. In fact, sometimes I start mutt with "-F /dev/null" when I
need to do something where I know stuff in my .muttrc is going to stop
me, for example I want to use another IMAP server and have none of my
hooks (which really are tied to my normal server) working.
> One way to make things clearer would be to have sections like
> [colors]
> [keybindings]
> [mailboxes]
> [lists]
> [folder_hooks]
Nothing stops you from laying out your .muttrc file like this. In fact,
this is the exact layout my own personal .muttrc file takes.
Having specifically-named sections as an object to parse is a pointless
waste of space and parsing time. If it really bugs you, use a comment.
For example:
# colors
color index blue default ~F
color index red default ~N
color index magenta default ~T
color index yellow default ~D
# key bindings
bind index p previous-entry
bind index n next-entry
# mailboxes
set imap_user="fred"
set folder="{mail.example.org}INBOX."
set spoolfile="{mail.example.org}INBOX"
# lists
subscribe [EMAIL PROTECTED] [EMAIL PROTECTED]
subscribe [EMAIL PROTECTED]
lists [EMAIL PROTECTED]
# hooks
folder-hook . unscore *
folder-hook . score '~A' +50
folder-hook . score '~F' +50
folder-hook . score '~E' -60
save-hook ~l +%B
--
Matt "...the only place for 63,000 bugs is a rain forest"
