From: Austin Clements <amdragon@MIT.EDU>
To: Andrei POPESCU <andreimpopescu@gmail.com>
Cc: notmuch@notmuchmail.org, Taesoo Kim <tsgatesv@gmail.com>
Subject: Re: [PATCH 0/2] automatic tagging based on imap maildir
Date: Sun, 28 Oct 2012 11:31:38 -0400 [thread overview]
Message-ID: <20121028153138.GB15377@mit.edu> (raw)
In-Reply-To: <20121028100324.GF6431@sid.nuvreauspam>
Quoth Andrei POPESCU on Oct 28 at 12:03 pm:
> On Sb, 27 oct 12, 10:00:46, David Bremner wrote:
> >
> > As I said (or tried to say), in my opinion, duplication with an external
> > package is not the main issue; I think moving features into the core
> > when appropriate is a normal development process. On the other hand, I'm
> > not really a gmail user, so I don't know yet if these patches solve
> > enough of the problem to be interesting.
>
> They are interesting not only for Gmail[1], but also for other kinds of
What is preventing folder: searches from addressing this?
> setups. As far as I understand (please correct me if I'm wrong),
> currently notmuch treats multiple copies of a message similar to Gmail
> (indexes one, but ignores the rest), which is why I'm *not* receiving
> any mailing lists on my Gmail account.
notmuch tracks all copies of a message, but its output generally shows
messages, rather than files, so you see a message only once regardless
of how many copies there are in the file system.
Why does that cause you to not receive mailing lists? (Or did I
misinterpret your statement?)
> Besides that consider also that I'm subscribed to about 40 mailing
> lists, each sorted to it's own folder by rules based on List-Id (which
> notmuch doesn't support yet as far as I know). This separation is very
> useful for my read-flow.
>
> However, there are messages crossposed to several lists. It would be
> great if notmuch or (more probably) a client using notmuch could mark
> all copies of a message as read in all folders, but still keep it there
> (otherwise the thread in the respective folder is incomplete).
If I understand what you're saying, this is exactly what notmuch does.
When you remove the "unread" tag, notmuch will (should?) add the
"seen" maildir flag to all copies of that message in the file system
(barring some corner-cases that flag sync doesn't handle well; maybe
you're encountering one of those?). And since notmuch never deletes
files, they will remain in the folders they were filed in.
> [1] yes, this is probably one missing feature that prevents me from
> putting my Gmail account in notmuch as well.
>
> Kind regards,
> Andrei
next prev parent reply other threads:[~2012-10-28 15:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-25 23:33 [PATCH 0/2] automatic tagging based on imap maildir Taesoo Kim
2012-10-25 23:33 ` [PATCH 1/2] Automatic tagging based on maildir Taesoo Kim
2012-10-26 11:31 ` David Bremner
2012-10-26 13:19 ` Michal Nazarewicz
2012-10-26 17:14 ` Jani Nikula
2012-10-25 23:33 ` [PATCH 2/2] fix: initialize error var before using it Taesoo Kim
2012-10-26 17:10 ` [PATCH 0/2] automatic tagging based on imap maildir Amadeusz Żołnowski
2012-10-26 23:02 ` David Bremner
2012-10-27 4:41 ` Taesoo Kim
2012-10-27 13:00 ` David Bremner
2012-10-28 10:03 ` Andrei POPESCU
2012-10-28 15:31 ` Austin Clements [this message]
2012-10-28 21:44 ` Andrei POPESCU
2012-10-28 22:12 ` Austin Clements
2012-10-29 0:07 ` Andrei POPESCU
2012-10-30 18:18 ` 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=20121028153138.GB15377@mit.edu \
--to=amdragon@mit.edu \
--cc=andreimpopescu@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=tsgatesv@gmail.com \
/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).