This is not unlike how the gmail frontend handles mails in 'categories'. Can't be of much assistance, but interested in your solution :).
Maybe something like: add mu4e-mark-all-new-for-setting-not-new (:)) to mu4e-index-updated-hook and mu4e-headers-mode-hook? The marks can then be applied like mu4e normally does Just thinking out loud.. Oliver Dunkl writes: >> My experience is that the 'new' flag for a given message is removed only >> when the /contents/ of that message are viewed. Which is very much how i >> prefer it. :-) > > But what makes the difference between 'new' and 'unseen' thats not clear > for me. My problem is to know when a new message comes to my system. > > I know there were also two different workflows[0] in mutt discussed. > > I fetch my emails with 'fetchmail' and deliver these with exim/procmail > to my users maildir. My problem is to know if there are new messages > between two fetchmail calls. > > My idea is to make a move cmd with update the flag -N for all messages > in the buffer after quiting the header-view with 'q'. You can also > control it with a variable e.g. mu4e-unflag-new-after-quit-header. If it > is true the one workflow is called and if it is false the other one is > called. But I am not sure how much work this could be e.g. in the > function 'mu4e~headers-quit-buffer'. > > \= odi > > [0] http://dev.mutt.org/trac/wiki/NewMailHandling > > -- > Oliver Dunkl > Software Engineer > IM: [email protected] > IRC: odi (irc.freenode.net) -- Jeroen Tiebout -- You received this message because you are subscribed to the Google Groups "mu-discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
