>On 2010-03-18, peng shao wrote:
>
>It's the way it's supposed to work, but it is confusing.
>
>Folder hooks are processed as the manual says. However, the push
>command pushes its arguments onto a stack and mutt's input parser
>later pops those arguments off the stack to parse and execute them.
On 08:47 Thu 18 Mar , Gary Johnson wrote:
>
> It's the way it's supposed to work, but it is confusing.
>
> Folder hooks are processed as the manual says. However, the push
> command pushes its arguments onto a stack and mutt's input parser
> later pops those arguments off the stack to parse
On 2010-03-18, peng shao wrote:
> I recently found the following interesting phenomenon:
>
> I included the following lines in my muttrc
>
> mailboxes ~/.MuttMail/inbox
> set spoolfile=~/.MuttMail/inbox
> folder-hook . 'push :default'
> folder-hook inbox 'push :inbox'
>
> This is the only four
Hi Patrick,
Le 17-03-2010, à 11:21:59 -0400, Patrick Shanahan (ptilopt...@gmail.com) a
écrit :
> * steve [03-17-10 11:00]:
> > Le 17-03-2010, à 09:51:24 -0400, Patrick Shanahan (ptilopt...@gmail.com) a
> > écrit :
> > > What if you send a *new* message to a...@example.com?
> >
> > If I'm in i
Hello Chuck,
thanks for taking the time.
Chuck Smith wrote on 17.03.10:
> I was looking around for a fix for you and found something interesting.
> Look at the Mutt User Manual in the section on PGP:
>
> http://wiki.mutt.org/?MuttGuide/UseGPG
>
> Look carefully at the this command:
>
> set p
Hello Niels,
Niels den Otter wrote on 17.03.10:
> > any hints are much needed...
>
> Just to be sure. You are opening an e-mail that is signed/encrypted
> with PGP and not with S/MIME?
I am able to decrypt stored gpg encrypted messages. And replying to one of
these messages also works fine. (I
