synchronize_flags leaving files in new (was muchsync files renames)

[Amadeusz Żołnowski]

David Mazieres expires 2015-11-30 PST
<mazieres-id6wst8pvwmdssdepck8t5fkje at temporary-address.scs.stanford.edu>
writes:
>> $ notmuch tag +hey thread:00000000000108bf
>> $ notmuch search thread:00000000000108bf
>> thread:00000000000108bf  Yest. 11:58 [1/1] Somebody; Subject (hey reklama unread)
>> $ notmuch search --output=files thread:00000000000108bf
>> /home/aidecoe/Mail/aidecoe/2015/new/1441022521.M714465P23412V000000000000FE04I0000000000141A38_0.freja,S=53857
>
> First, just to be absolutely sure, doe the file exist?

100% sure.


> Second, I wonder if the ",S=53857" suffix (size) is throwing things
> off.  Perhaps libnotmuch only expects suffixes when they are of the
> form ",S=53857:2,<flags>."  Since muchsync does not add a size field
> (in either the new or cur subdirectory), it could be leading to the
> different behavior.  To test this, can you rename the file in the new
> directory without the ",S=..." and see if the behavior changes?

,S=... doesn't have any impact. I have tested it.


-- 
Amadeusz Żołnowski
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 950 bytes
Desc: not available
URL: <http://notmuchmail.org/pipermail/notmuch/attachments/20150902/89878df3/attachment.sig>