* Can not view messages in deeply nested threads (emacs)
@ 2019-04-08 19:27 Landry, Walter
2019-04-08 21:18 ` Brian Sniffen
0 siblings, 1 reply; 3+ messages in thread
From: Landry, Walter @ 2019-04-08 19:27 UTC (permalink / raw)
To: notmuch@notmuchmail.org
Hi Everyone,
Back in January, I posted about a problem I had when viewing large
threads. The workaround was to use tree view. That worked until today.
Now, when I try to view a new email in either tree view or the regular
view, I get the message
Re-entering top level after C stack overflow
I am guessing that the thread depth got too deep? The message is 294
(?!?!?) levels deep. I can look at messages that are in the same
thread, but not as deep. After some searching, it seems that this
happens because I have
max-specpdl-size
set too large. However, if I try setting it smaller, tree view is
unable to display the thread.
I also have astroid and alot installed. Astroid tends to freeze a lot
whenever I try to look at these messages. Alot is slow, but works. The
command line client works without issues.
Is there any way that I can look at these messages in emacs?
Thank you,
Walter Landry
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Can not view messages in deeply nested threads (emacs)
2019-04-08 19:27 Can not view messages in deeply nested threads (emacs) Landry, Walter
@ 2019-04-08 21:18 ` Brian Sniffen
2019-04-08 21:35 ` Landry, Walter
0 siblings, 1 reply; 3+ messages in thread
From: Brian Sniffen @ 2019-04-08 21:18 UTC (permalink / raw)
To: Landry, Walter; +Cc: notmuch@notmuchmail.org
Consider changing your html tenderer to anything other than ‘shr. Its handling of nested blocks is unsane.
--
Brian Sniffen
> On Apr 8, 2019, at 3:27 PM, Landry, Walter <wlandry@caltech.edu> wrote:
>
> Hi Everyone,
>
> Back in January, I posted about a problem I had when viewing large
> threads. The workaround was to use tree view. That worked until today.
> Now, when I try to view a new email in either tree view or the regular
> view, I get the message
>
> Re-entering top level after C stack overflow
>
> I am guessing that the thread depth got too deep? The message is 294
> (?!?!?) levels deep. I can look at messages that are in the same
> thread, but not as deep. After some searching, it seems that this
> happens because I have
>
> max-specpdl-size
>
> set too large. However, if I try setting it smaller, tree view is
> unable to display the thread.
>
> I also have astroid and alot installed. Astroid tends to freeze a lot
> whenever I try to look at these messages. Alot is slow, but works. The
> command line client works without issues.
>
> Is there any way that I can look at these messages in emacs?
>
> Thank you,
> Walter Landry
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> https://notmuchmail.org/mailman/listinfo/notmuch
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Can not view messages in deeply nested threads (emacs)
2019-04-08 21:18 ` Brian Sniffen
@ 2019-04-08 21:35 ` Landry, Walter
0 siblings, 0 replies; 3+ messages in thread
From: Landry, Walter @ 2019-04-08 21:35 UTC (permalink / raw)
To: Brian Sniffen; +Cc: notmuch@notmuchmail.org
Brian Sniffen writes:
> Consider changing your html tenderer to anything other than ‘shr. Its
> handling of nested blocks is unsane.
I set it to 'nil', and I still get
Re-entering top level after C stack overflow
Thanks,
Walter Landry
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2019-04-08 21:35 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2019-04-08 19:27 Can not view messages in deeply nested threads (emacs) Landry, Walter
2019-04-08 21:18 ` Brian Sniffen
2019-04-08 21:35 ` Landry, Walter
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).