* Mikko Hänninen ([EMAIL PROTECTED]) [000129 14:44]:
> First, let me explain about the = shortcut. The = gets expanded to the
> contents of $folder whenever it's seen. So if you set $folder to ~/mail
> (which gets immediately expanded to /home/user/mail or something like
> that), and then have a
Jim Breton <[EMAIL PROTECTED]> wrote on Sat, 29 Jan 2000:
> If I want to trigger a command in the "mutt" folder but not in
> "mutt-sent" how can I do this? The hook seems to make a match on either
> one.
>
> I've tried "mutt" and "=mutt" for the hook. There must be some regexp
> pattern that wo
Yep you were right. Thanks. :)
Btw, this leads me to another question. Suppose I have two folders, one called "mutt"
and the other one is "mutt-sent"
If I want to trigger a command in the "mutt" folder but not in "mutt-sent" how can I
do this? The hook seems to make a match on either one.
* Jim Breton ([EMAIL PROTECTED]) [000129 12:40]:
> folder-hook =mutt "my_hdr From: Jim Breton <[EMAIL PROTECTED]>"
>
> But if I load mutt like this:
>
> mutt -f ~/mail/mutt
A guess (untested because I don't have time right now to test it) is
that it's noticing that "~/mail/mutt" != "=mutt
Hi, it seems that my folder hooks are not run when I load a specific folder from the
command line.
For instance, I have a folder hook that looks like this:
folder-hook =mutt "my_hdr From: Jim Breton <[EMAIL PROTECTED]>"
But if I load mutt like this:
mutt -f ~/mail/mutt
It does not set
