David Bremner <david@tethera.net> writes: > Amadeusz Żołnowski <aidecoe@aidecoe.name> writes: > >> What's more surprising is that there is a test case in notmuch test >> suite which test whether after modifing tag of a mail it is moved from >> new/ to cur/. Yes, it should be moved on any tag modification if I >> understand correctly. But it seems it does not for my maildirs... >> > > If I understand the code correctly, this movement will only happen when > one of the maildir-flag-equivalent tags is changed. I haven't dug ack > through the archives, but I think mutt uses presence in new/ as some > kind of extra unseen state, so people requested not to move files until > needed. Can you explain how/where this is implemented? I would like muchsync to do exactly what notmuch does, and ideally without replicating its logic, if I can just have libnotmuch handle this. Currently, my code looks something like this: notmuch_message_freeze() notmuch_message_remove_all_tags() notmuch_message_add_tag(); notmuch_message_add_tag(); ... if (synchronize_tags) notmuch_message_tags_to_maildir_flag() notmuch_message_thaw() And what we're finding is the above code causes the message to move from new/ to cur/, while the "notmuch tag" command does not, even while changing between the same before and after tag sets. Any ideas? Thanks, David