unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: notmuch@notmuchmail.org
Subject: bug: wrong order of messages in notmuch-show
Date: Sun, 01 Jul 2018 23:27:57 +0200	[thread overview]
Message-ID: <87efgmmysi.fsf@len.workgroup> (raw)

Dear notmuch developers,

notmuch sometimes shows emails of one thread in wrong order.  Now
I found an example in a public mailing list so it is possible to
share this example.  It is a small thread from the notmuch
mailing list, you might find it by searching for id:87zhzccrwg.fsf@tethera.net

While this email is the last written and sent in this thread it
is shown as first email in the notmuch show output, as shown in
this "screenshot" of the corresponding notmuch-emacs buffer:

      File Edit Options Buffers Tools Help
      'notmuch search thread:<>' lists multiple threads
-->   David Bremner <david@tethera.net> (Yest. 15:42) (inbox new unread)
      Subject: Re: 'notmuch search thread:<>' lists multiple threads
      Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com> (April 06) (inbox new unread)
       Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com> (April 06) (inbox new unread)
       David Bremner <david@tethera.net> (April 08) (inbox new unread)
        David Bremner <david@tethera.net> (April 09) (inbox new unread)
         David Bremner <david@tethera.net> (April 10) (inbox new unread)
         Subject: [PATCH] devel: add new tool to draw thread structure
         Naveen N. Rao <naveen.n.rao@linux.vnet.ibm.com> (April 18) (inbox new unread)
         Subject: Re: 'notmuch search thread:<>' lists multiple threads
          David Bremner <david@tethera.net> (April 22) (inbox new unread)


This happens often to me with emails from a ticket system which I
cannot disclose.  In this kind of technical threads order is
necessary to understand current status of affairs.

I did a test with notmuch 0.27+7~gfd3c936 and .notmuch-config
pointing to a test maildir with this 8 messages as they arrived
at my email account.  I saved a tar archive of this in case this
is important to debug the problem.

Thanks, for your attention, Gregor

             reply	other threads:[~2018-07-01 21:28 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-01 21:27 Gregor Zattler [this message]
2018-07-01 21:59 ` bug: wrong order of messages in notmuch-show Amin Bandali
2018-07-02  0:23 ` David Bremner
2018-07-02  8:06   ` Gregor Zattler
2018-07-08 12:24     ` David Bremner
2018-07-08 12:24       ` [PATCH 1/2] test: start threading test corpus David Bremner
2018-07-08 12:24       ` [PATCH 2/2] test: add known broken test for "ghost roots" David Bremner
2018-07-27  7:21 ` bug: wrong order of messages in notmuch-show Gregor Zattler
2018-07-29  9:47   ` David Bremner
2018-07-29 13:57     ` Gregor Zattler
2018-09-08 10:35 ` David Bremner
2018-09-08 20:42   ` 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=87efgmmysi.fsf@len.workgroup \
    --to=telegraph@gmx.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).