* David T-G <[EMAIL PROTECTED]> [2002-03-27 07:13:40 -0500]:
> % Here's what the default account-hook entry looks like now:
> %
> % account-hook . 'unset imap_user ; set folder=~/Mail'
>
> Hmmm... Well, if it isn't setting $folder then I bet it's not being
> triggered at all. You're not really
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
Rocky --
...and then Rocky Giannini said...
%
% David,
%
% First -- Thanks very much for the quick response. When I saw your reply,
Happy to help!
% I thought for sure that would work -- Unfortunately, I made the change,
% and I'm still seeing the same behavior.
Ah.
%
% Here's what the
David,
First -- Thanks very much for the quick response. When I saw your reply,
I thought for sure that would work -- Unfortunately, I made the change,
and I'm still seeing the same behavior.
Here's what the default account-hook entry looks like now:
account-hook . 'unset imap_user ; set folde
David,
First -- Thanks very much for the quick response. When I saw your reply,
I thought for sure that would work -- Unfortunately, I made the change,
and I'm still seeing the same behavior.
Here's what the default account-hook entry looks like now:
account-hook . 'unset imap_user ; set folde
Rocky --
...and then Rocky Giannini said...
%
% Hi Folks,
Hello!
%
% I'm attempting to use mutt (V1.3.28i) to seamlessly read mail on a local
% spool *and* two imap servers.
Sounds easy enough.
%
...
% account-hook . 'unset imap_user'
% account-hook imap://imap1.blah.com 'set folder=imap
