From: Sean Whitton <spwhitton@spwhitton.name>
To: David Bremner <david@tethera.net>, notmuch@notmuchmail.org
Subject: Re: Forcing a sync of maildir flags?
Date: Fri, 21 Feb 2020 12:54:46 -0700 [thread overview]
Message-ID: <87d0a7zpfd.fsf@iris.silentflame.com> (raw)
In-Reply-To: <87mu9cg5xy.fsf@tethera.net>
Hello,
On Thu 20 Feb 2020 at 08:06PM -04, David Bremner wrote:
> Sean Whitton <spwhitton@spwhitton.name> writes:
>
>> So, your hypothesis is that notmuch is opting not to add the Seen flag
>> in order to avoid having to move the message from new to cur, for the
>> sake of mutt, but that's a bug because I've explicitly requested adding
>> Seen, so it ought to go ahead and move it from new to cur?
>
> Yeah, I think that's the case. This is based only vague memories of when
> I wrote 0082a557.
Thanks. Let me record in this thread what I will believe it will take a
reproduce this in a test:
1) inbox and sent are Maildirs
1) Compose mail to a mailing list which will return copies of
submissions, with `Fcc: sent -unread`
2) notmuch new, and in post-new hook, notmuch tag -unread -- folder:sent
Expected result: copy of message in both inbox and sent has Seen flag
Actual result: only copy of message in sent has Seen flag
--
Sean Whitton
next prev parent reply other threads:[~2020-02-21 19:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 4:58 Forcing a sync of maildir flags? Sean Whitton
2020-02-20 12:22 ` David Bremner
2020-02-20 13:21 ` David Bremner
2020-02-20 21:19 ` Sean Whitton
2020-02-21 0:06 ` David Bremner
2020-02-21 19:54 ` Sean Whitton [this message]
2022-05-01 23:23 ` David Bremner
2022-05-02 23:24 ` Sean Whitton
2022-05-03 12:14 ` David Bremner
2022-05-03 23:59 ` Sean Whitton
2022-03-22 19:44 ` Sean Whitton
2022-04-05 4:48 ` Sean Whitton
2022-04-13 10:27 ` Gregor Zattler
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=87d0a7zpfd.fsf@iris.silentflame.com \
--to=spwhitton@spwhitton.name \
--cc=david@tethera.net \
--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).