Hi, I've been using notmuch together with mutt to solve an email annoyance: a message in multiple folders should be marked read all at once. With vanilla mutt you need to mark the message read in each folder (my messages are filtered into mailing list folders, so I have this problem when a message is CCed to multiple mailing lists that I subscribe to). Here's the macro I use: macro index \Cr "<enter-command>unset wait_key<enter><pipe-message>~/notmuch/contrib/notmuch-mutt/notmuch-mutt tag --whole-thread -- -unread<enter><sync-mailbox><previous-unread><next-unread>" "Mark thread read and jump to next unread message" Together with a notmuch-mutt patch that I recently sent: http://notmuchmail.org/pipermail/notmuch/2012/012527.html Forking a notmuch-mutt process and syncing the mailbox afterwards takes some time. It would be much smoother if mutt was linked against notmuch... So here is my question: Can mutt-kz do this? Ideally <read-thread> would use notmuch to remove the unread tag from all messages in a thread. It's not clear to me from skimming the source. The notmuch integration seems to be focussed on virtual folders/queries and some convenience commands rather than replacing mutt's message access (e.g. maildir) completely with notmuch. Stefan