unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: "Dan Čermák" <dan.cermak@posteo.net>
To: "notmuch\@notmuchmail.org" <notmuch@notmuchmail.org>
Subject: Re: emacs slow with large threads
Date: Sat, 19 Jan 2019 01:11:20 +0100	[thread overview]
Message-ID: <878szh8q1j.fsf@cgc-instruments.com> (raw)
In-Reply-To: <87fttpy0n5.fsf@mechane.wlandry.net>

Hi Landry,

I am afraid this is a common limitation of emacs: if you start opening
large files (especially with long lines) it becomes very slow.

A viable workaround is to open the offending thread in the tree view
(bound to 'z' by default) and then only view individual messages.


Cheers,

Dan

"Landry, Walter" <wlandry@caltech.edu> writes:

> Hello Everyone,
>
> I am using the emacs frontend to notmuch.  It has mostly been a pleasant
> experience, but I am having a problem with large threads.  Essentially,
> when I try to view a large thread, the machine locks up for many
> minutes.  The problem seems very similar to these posts.
>
>   https://notmuchmail.org/pipermail/notmuch/2013/014811.html
>   https://notmuchmail.org/pipermail/notmuch/2015/020379.html
>
> I tried turning off html rendering by setting mm-text-html-renderer to
> nil.  That helped, but it is still taking at least 10 minutes to render
> a thread.  I killed it when I ran out of patience.
>
> The thread has 231 messages, and running
>
>   notmuch show thread:000000000000d637 | wc -l
>
> shows that it is 46918 lines long.  Running that on the command line is
> fast, taking 0.123 seconds.  As a comparison, I tried opening the thread
> with astroid.  It was not instantaneous, but it only took about 3
> seconds.
>
> I am guessing that the emacs mode is trying to process the result.  I
> can work around this a bit by opening individual messages with "C-u RET"
> instead of "RET".  But then I lose context.
>
> Is there anything else I can do to make this work?
>
> Thanks,
> Walter Landry
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> https://notmuchmail.org/mailman/listinfo/notmuch

  reply	other threads:[~2019-01-19  0:11 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-19  0:03 emacs slow with large threads Landry, Walter
2019-01-19  0:11 ` Dan Čermák [this message]
2019-01-19 15:45   ` Landry, Walter
2019-01-21 11:07     ` Dan Čermák
2019-01-21 12:39       ` Emilio Francesquini
2019-01-22 17:49         ` Brian Sniffen
2019-01-22 18:35           ` Emilio Francesquini
2019-01-22 18:46             ` Emilio Francesquini
2019-01-19  0:27 ` Brian Sniffen
2019-01-19  9:03 ` David Edmondson
2019-01-19 15:43   ` Landry, Walter

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=878szh8q1j.fsf@cgc-instruments.com \
    --to=dan.cermak@posteo.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).