Hi.

I'm using notmuch to index my mail, and noticed that some emails disappear from my searches (saved searches in emacs).

Such mail appear when I do a search including a subject: but not with tags, for instance.

Example :
$ notmuch search tag:ldpw3wg | grep ACTION-10
gives no results, whereas :
$ notmuch search subject:ACTION-10 tag:ldpw3wg | grep ACTION-10
thread:00000000000003ae   Thu. 09:34 [4/7] Steve K Speicher, Arnaud Le Hors, Michael Hausenblas| Erik Wilde, Kevin Page, Armin.Haller@csiro.au; ACTION-10: First Editor's Draft is available! (inbox ldpw3wg newinbox unread)

As you can see, the ldpw3wg is supposed to be attached to that thread.

Attached is the output of notmuch show thread:00000000000003ae.

Needless to say that it's very uncomfortable to miss new mail :-(

Thanks in advance.

Best regards,

Olivier Berger <olivier.berger@it-sudparis.eu> writes:

There are several different subjects in the thread you included.  The
default is to report the newest subject from a matched message. In the
first case, I believe that subject is "Multiple representations of the
same resource without content negotiation" which does not match "ACTION-10".

Maybe you know this, but just in case, tags in notmuch are attached to
messages, not threads.  I don't think that is relevant to your bug
report though.

At the moment I don't think there is a bug here, although maybe the
documentation for the "summary" output format could be improved.

All the best,

David

Olivier Berger <olivier.berger@it-sudparis.eu> writes:

There are several different subjects in the thread you included.  The
default is to report the newest subject from a matched message. In the
first case, I believe that subject is "Multiple representations of the
same resource without content negotiation" which does not match "ACTION-10".

Maybe you know this, but just in case, tags in notmuch are attached to
messages, not threads.  I don't think that is relevant to your bug
report though.

At the moment I don't think there is a bug here, although maybe the
documentation for the "summary" output format could be improved.

All the best,

David

severity 688699 normal
thanks

Hi.

David Bremner <david@tethera.net> writes:

Thanks for your answer.

I'm relieved.

Actually, you're right, and the messages are there, tagged as could be
expected, and I was just confused by the change of subject by someone
who used a reply instead of posting a new mail.

Is there a way to change the summary behaviour, i.e. report the initial
thread's subject instead of the latest (configurable option ?) ?

I think I could also imagine a feature that could "split" threads in
such cases, i.e. overriding the in-reply-to headers somehow. What do you
think ?

I'll probably convert this bug as a wishlist for the summary behaviour option
idea.

Thanks again, David.

Best regards,

Olivier Berger <olivier.berger@it-sudparis.eu> writes:

Currently this is controlled by the sort order (--sort) option to
notmuch search. There is not currently a way to display the earliest
thread subject while sorting the threads in the default reverse
chronological order.  As far as I know, it would not be too hard to add
an option to do this on the command line.  You would probably have to
convince people that the increase in UI complexity is worth it. And of
course somebody needs to actually do the work.

This is a topic that comes up from time to time. I believe this would
require some changes to the way that threads are computed/stored in
notmuch; currently the thread structure can be entirely recovered from
the raw messages, and does not need to be backed up.  You could file a
separate wishlist bug or discuss this on the upstream mailing list if
you like.

d

retitle 688699 Optionnaly allow to view initial subject in thread summaries
severity 688699 wishlist
thanks

David Bremner <david@tethera.net> writes:

OK, moving that bug to a wishlist.

Will report on the ML.

Thanks for your help.

Best regards,