From: David Bremner <david@tethera.net>
To: Leo Gaspard <leo@gaspard.io>, notmuch@notmuchmail.org
Subject: Re: Mail to self
Date: Sat, 27 Oct 2018 16:58:51 -0300 [thread overview]
Message-ID: <87r2gbqhz8.fsf@tethera.net> (raw)
In-Reply-To: <87y3ajboev.fsf@llwynog.ekleog.org>
Leo Gaspard <leo@gaspard.io> writes:
> Hello,
>
> I'm looking for a way to have notmuch consider, when it finds both an
> unread and a read mail with the same Message-Id (eg. sending a mail to
> self from a phone), that the mail is unread (because I'd rather have too
> many mails unread than miss important mail, and it's also useful for
> tests).
>
> Do you see any way of having notmuch do this?
After a discussion on IRC, my understanding is the following. The
underlying behaviour that Leo is objecting to is that if any one file
with a given message-id has the ,S maildir flag, then when notmuch syncs
maildir flags to tags, it will remove the unread tag from that
message-id. After some back and forth and thinking about it, I think
notmuch's current behaviour is actually correct (given the constraint
that tags attach to message-ids). You could argue for different ways of
resolving conflicts for maildir flags in general, but the ",S" or "seen"
flag has fairly natural common sense semantics.
d
next prev parent reply other threads:[~2018-10-27 19:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-27 11:48 Mail to self Leo Gaspard
2018-10-27 19:58 ` David Bremner [this message]
2018-10-28 7:31 ` Leo Gaspard
2018-10-28 12:04 ` Gregor Zattler
2018-10-28 15:14 ` Leo Gaspard
2018-10-30 16:45 ` Leo Gaspard
2018-10-30 16:49 ` Leo Gaspard
2018-10-30 17:15 ` [PATCH 0/1] notmuch: be conservative and prefer marking too many messages as unread than too few notmuchmail.org
2018-10-30 17:15 ` [PATCH 1/1] " notmuchmail.org
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=87r2gbqhz8.fsf@tethera.net \
--to=david@tethera.net \
--cc=leo@gaspard.io \
--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).