Hey, wow, this is an awesome idea!
While I do not care about marking github issues read/unread, this is still a good inspiration for a message hooks I might develop to notify myself about new mail in certain cases, using notify-send! Thanks a lot for sharing! Matthias On 11-08-2016 20:50:08, Keith Smiley wrote: > Hey everyone, > > I've had a long running problem with my mutt configuration when using > message-hook to run a script for unread messages. The configuration looks like > this: > > ``` > message-hook '~U !~T ~f notifications@github\.com' \ > "push '<enter-command>set my_old_pipe_decode=\$pipe_decode \ > nopipe_decode<enter> \ > <pipe-message>ghnotification.sh<enter> \ > <enter-command>set pipe_decode=\$my_old_pipe_decode<enter><top>'" > ``` > > Full code here: > > https://github.com/keith/dotfiles/commit/2071bd80f5d2b44189a1ed6d2aaf00085eaf719f > > The intention here is to run a script that curls the magic image in GitHub > emails to mark them as read on GitHub. Doing this for unread (and as an > optimization for the problem, also untagged) messages works fine from the > index. > If I open a message from the index, the script is executed correctly. The > problem comes when I *delete* an *unread* email from the index. In this case > it > seems that the command is interpreted as a series of key presses. This results > in a directory being created locally called: > > ``` > enter-command>set my_old_pipe_decode (etc) > ``` > > It seems that the problem is in how I'm executing the command doesn't work > with > my delete command: > > ``` > macro index,pager d "<save-message>+gmail/trash<enter>" "Delete message" > ``` > > Any advice on how to work around this would be greatly appreciated! > > > Thanks for reading! > > -- > Keith Smiley > -- Mit freundlichen Grüßen, Kind regards, Matthias Beyer Proudly sent with mutt. Happily signed with gnupg.
signature.asc
Description: PGP signature
