unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Landry, Walter" <wlandry@caltech.edu>
To: Brian Sniffen <bts@evenmere.org>
Cc: "notmuch@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: Can not view messages in deeply nested threads (emacs)
Date: Mon, 8 Apr 2019 21:35:39 +0000	[thread overview]
Message-ID: <874l78uqmv.fsf@mechane.wlandry.net> (raw)
In-Reply-To: <DFACD384-F6C9-4F87-A8EE-BE4193B136FA@evenmere.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

      reply	other threads:[~2019-04-08 21:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]

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=874l78uqmv.fsf@mechane.wlandry.net \
    --to=wlandry@caltech.edu \
    --cc=bts@evenmere.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).