Re: muchsync files renames

2015-09-01 Thread dm-list-email-notmuch
David Bremner writes: > Amadeusz Żołnowski 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

Re: muchsync files renames

2015-09-01 Thread David Bremner
Amadeusz Żołnowski 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 ma

synchronize_flags leaving files in new (was muchsync files renames)

2015-09-01 Thread dm-list-email-notmuch
Amadeusz =C5=BBo=C5=82nowski 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

Re: muchsync files renames

2015-09-01 Thread Amadeusz Żołnowski
Hi David, David Mazieres writes: > Let's just make sure I understand: Your mail starts out like this: > > Path: spam/new/nnn.MnnnPnnnQnRn.machine > Tags: new > > Then you run afew, and afew runs > > notmuch tag -new +spam > > You are saying that that even though maildir.synchroniz