From: "Amadeusz Żołnowski" <aidecoe@aidecoe.name>
To: David Mazieres expires 2015-11-30 PST
<mazieres-id6wst8pvwmdssdepck8t5fkje@temporary-address.scs.stanford.edu>
Cc: notmuch@notmuchmail.org
Subject: Re: synchronize_flags leaving files in new (was muchsync files renames)
Date: Wed, 02 Sep 2015 22:01:26 +0100 [thread overview]
Message-ID: <87vbbslemx.fsf@freja.aidecoe.name> (raw)
In-Reply-To: <87k2s93ewg.fsf@ta.scs.stanford.edu>
[-- Attachment #1: Type: text/plain, Size: 1063 bytes --]
David Mazieres expires 2015-11-30 PST
<mazieres-id6wst8pvwmdssdepck8t5fkje@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
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 950 bytes --]
next prev parent reply other threads:[~2015-09-02 21:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-22 21:02 muchsync files renames Amadeusz Żołnowski
2015-08-23 5:41 ` David Mazieres
2015-08-23 8:44 ` Amadeusz Żołnowski
2015-08-23 20:06 ` David Mazieres
2015-08-23 20:43 ` David Mazieres
2015-08-24 22:14 ` Amadeusz Żołnowski
2015-08-26 6:31 ` Amadeusz Żołnowski
[not found] ` <87vbbwnbb4.fsf@freja.aidecoe.name>
[not found] ` <87io7wr50y.fsf@ta.scs.stanford.edu>
2015-08-31 11:59 ` Amadeusz Żołnowski
2015-08-31 17:27 ` dm-list-email-notmuch
2015-08-31 22:11 ` Amadeusz Żołnowski
2015-08-31 23:43 ` David Mazieres
2015-09-01 22:52 ` Amadeusz Żołnowski
2015-09-01 23:20 ` synchronize_flags leaving files in new (was muchsync files renames) dm-list-email-notmuch
2015-09-02 21:01 ` Amadeusz Żołnowski [this message]
2015-09-02 0:37 ` muchsync files renames David Bremner
2015-09-02 0:46 ` dm-list-email-notmuch
2015-09-02 21:21 ` Amadeusz Żołnowski
2015-09-02 23:05 ` David Bremner
2015-09-09 17:49 ` Amadeusz Żołnowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vbbslemx.fsf@freja.aidecoe.name \
--to=aidecoe@aidecoe.name \
--cc=mazieres-id6wst8pvwmdssdepck8t5fkje@temporary-address.scs.stanford.edu \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).