Hi all,

I'm using this trick to automatically mark a github notification as
read via HTTP whenever I read the corresponding notification email
in mutt:

  message-hook "(~N|~O) ~f notificati...@github.com" "push 
'<pipe-message>read-github-notification\n'"

Full details are available here:

  
http://blog.adamspiers.org/2014/10/05/managing-your-github-notifications-inbox-with-mutt/

However there is a weird issue when I tag multiple (unread)
notification emails in mutt and press ";s" to save them all to a
folder.  In this case, mutt gives me the following prompt:

  Create /home/adam/mail/archive.2014.12pipe-entry>read-github-notification 
([yes]/no):

So clearly the message-hook is being triggered even though I'm only
trying to save messages, rather than view them.

Can anyone explain why, and offer a fix/workaround?

Many thanks!
Adam

Reply via email to