Rocky Giannini <[EMAIL PROTECTED]> wrote:
>
> account-hook . 'unset imap_user ; set folder=~/Mail'
This is problematic. The problem is that, when you enter a pathname
like "=folder" into a send-hook or a $record variable, you might expect
that Mutt simply stores the "=folder" string in the hook or variable,
and then when it is needed, performs some type of dynamic expansion,
using the current value of $folder, and accesses the path specified.
However, that's not how Mutt works. Instead, at the time that you
create (instantiate?) the hook or at the time you set the variable, that
is when the current value of $folder will be read, and the full path
expanded at that time.
set folder=/dir1
folder-hook =folder 'set var=value'
set folder=/dir2
folder-hook =foobar 'set var=value'
In this example, two send-hooks are created, one on the folder
"/dir1/folder", and the other on "/dir2/foobar". If you are expecting
that the second setting of $folder will cause the first hook to be
redefined, so that it is triggered when you switch to "/dir2/folder",
you will be sadly mistaken.
--
David DeSimone | "The doctrine of human equality reposes on this:
[EMAIL PROTECTED] | that there is no man really clever who has not
Hewlett-Packard | found that he is stupid." -- Gilbert K. Chesterson
Richardson IT | PGP: 5B 47 34 9F 3B 9A B0 0D AB A6 15 F1 BB BE 8C 44
