Liviu Daia on Tue 16/02 01:02 +0200:
> [sound logical reasons why this is not so]
>
> The fact it's not automatically sourced is just a minor annoyance; if
> you don't want to miss a change when you update your .muttrc, all you
> have to do is put the two commands next to each other (which, BTW, you
> should have done from the very beginning, as the way the sample muttrc
> files are organized sucks big time).
Well, I for one like to separate my sourcings into a section or file of
their own.
What would solve this problem (and many others) is being able to create
arbitrary local variables that do not correspond to configuration
variables.
It would then be a matter of
localvar ="~/.mutt/aliases"
aliases =$localvar
source $localvar
Or, I imagine just allowing configuration variables to be referenced (is
this done already?) as in
aliases ="~/.mutt/aliases"
source $aliases
would also work, but is not nearly as flexible as the former method.
--
Scott
