From: David Bremner <david@tethera.net>
To: Alan Schmitt <alan.schmitt@polytechnique.org>,
notmuch <notmuch@notmuchmail.org>
Subject: Re: show a single message in a huge thread
Date: Wed, 02 Jun 2021 13:02:13 -0300 [thread overview]
Message-ID: <87v96wjlve.fsf@tethera.net> (raw)
In-Reply-To: <871r9klat9.fsf@tethera.net>
David Bremner <david@tethera.net> writes:
> Alan Schmitt <alan.schmitt@polytechnique.org> writes:
>
>> Hello,
>>
>> On 2021-06-01 15:33, David Bremner <david@tethera.net> writes:
>>
>>>> Is this a bug of notmuch-emacs? Is there a way to display a single
>>>> message independently of its context?
>>>>
>>>
>>> I'm not sure what the best UI is, but here is a start:
>>>
>>> (defun notmuch-show-single-message (query)
>>> (interactive "sQuery: ")
>>> (message query)
>>> (let ((notmuch-show-indent-messages-width 0)
>>> (notmuch-show-only-matching-messages t))
>>> (notmuch-show query)))
>>
>> Thank you for the suggestion, unfortunately I get a very similar error.
>> I found the id of the message I want, and when I run this function, I
>> get this backtrace.
>>
>
> The code I posted worked fine for me for one message from a thread of
> 323 messages. It could be a I need a really giant thread to test, or
> perhaps the structure of the individual messages matters also. The long
> threads I have are from Debian mailing lists, so the message structure
> tests to be be mainly one part of plain text.
I played with this some more, and I think I understand what the issue
is, although I still cannot duplicate the crash. By unless given the
"--part" option the CLI returns the whole thread structure, even if it
does not populate it. So there is a big tree of empty lists, and
recursively traversing this tree is what is crashing. In principle
passing "--part=0" to the CLI should turn off this behaviour, but I
don't know how much needs to be changed on the emacs side to display the
result properly.
next prev parent reply other threads:[~2021-06-02 16:02 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 [this message]
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
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=87v96wjlve.fsf@tethera.net \
--to=david@tethera.net \
--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).