unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jonathan Wilner <jonathan@teamwilner.com>
To: Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: notmuch <notmuch@notmuchmail.org>
Subject: Re: show a single message in a huge thread
Date: Fri, 11 Jun 2021 09:45:04 -0700	[thread overview]
Message-ID: <CADtp3N=5Vk0__Z_CuYY2vy_O5KpOuqq8JkPv-e4MrOTdDsVHrw@mail.gmail.com> (raw)
In-Reply-To: <878s3rmlfj.fsf@m4x.org>


[-- Attachment #1.1: Type: text/plain, Size: 1062 bytes --]

I definitely also have this problem with large threads - big time hangs
using Notmuch in Emacs. My simple tests indicate that it happens in Emacs,
not using Notmuch at the command line, though that can also take quite a
long time to return.

I'm suspicious that there's something with HTML parsing - does that seem
possible? It might also make sense if Delta Chat is giving you HTML versus
plaintext.



On Thu, Jun 3, 2021 at 12:55 AM Alan Schmitt <alan.schmitt@polytechnique.org>
wrote:

> Hello,
>
> On 2021-06-02 09:18, David Bremner <david@tethera.net> writes:
>
> > The code I posted worked fine for me for one message from a thread of
> > 323 messages.
>
> The thread that used to crash (before your patch) was from DeltaChat,
> which is an email-based chat app. The thread it produces are like lists
> more than trees. So I guess the depth of the tree is what matters.
>
> Best,
>
> Alan
> _______________________________________________
> notmuch mailing list -- notmuch@notmuchmail.org
> To unsubscribe send an email to notmuch-leave@notmuchmail.org
>

[-- Attachment #1.2: Type: text/html, Size: 1661 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2021-06-11 16:45 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 10:10 show a single message in a huge thread alan.schmitt
2021-05-28 12:37 ` David Bremner
2021-05-28 14:16   ` Alan Schmitt
2021-06-01  6:57     ` Alan Schmitt
2021-06-01 18:33       ` David Bremner
2021-06-01 18:48         ` Jameson Graef Rollins
2021-06-02  6:46         ` Alan Schmitt
2021-06-02 12:18           ` David Bremner
2021-06-02 16:02             ` David Bremner
2021-06-02 19:19               ` Tomi Ollila
2021-06-02 23:31                 ` First attempt at a fix for single message display deep in thread David Bremner
2021-06-02 23:31                   ` [PATCH 1/2] emacs/show: add parameter notmuch-show-single-message David Bremner
2021-06-02 23:31                   ` [PATCH 2/2] emacs/tree: use notmuch-show-single-message David Bremner
2021-06-03  7:53                   ` First attempt at a fix for single message display deep in thread Alan Schmitt
2021-06-03  7:55             ` show a single message in a huge thread Alan Schmitt
2021-06-11 16:45               ` Jonathan Wilner [this message]
2021-06-12 20:39                 ` Tomi Ollila
2021-05-28 16:01 ` Jameson Graef Rollins

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='CADtp3N=5Vk0__Z_CuYY2vy_O5KpOuqq8JkPv-e4MrOTdDsVHrw@mail.gmail.com' \
    --to=jonathan@teamwilner.com \
    --cc=alan.schmitt@polytechnique.org \
    --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).