From: Brian Sniffen <bts@evenmere.org>
To: Emilio Francesquini <francesquini@gmail.com>
Cc: notmuch@notmuchmail.org
Subject: Re: emacs slow with large threads
Date: Tue, 22 Jan 2019 12:49:14 -0500 [thread overview]
Message-ID: <AA754A29-A337-4E09-B07B-2242AAD8FC15@evenmere.org> (raw)
In-Reply-To: <CANN71N4mpFDSkCMN8knf-UnfP7ybQ7Jrc1Gy=5r547PiPZC+WA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2006 bytes --]
I think that becomes buffer local when set. Are you sure it me a difference?
--
Brian Sniffen
> On Jan 21, 2019, at 7:39 AM, Emilio Francesquini <francesquini@gmail.com> wrote:
>
> Hello there,
>
> I recently ran into the same (slowness) problem when viewing long threads.
> After some profiling I found out that disabling indentation did the trick for me. In my case it went from unusable (>5 minutes) to ~3 seconds for large threads.
>
> (setq notmuch-show-indent-content nil)
>
> Hope it helps.
>
>> On Mon, Jan 21, 2019 at 9:07 AM Dan Čermák <dan.cermak@posteo.net> wrote:
>> "Landry, Walter" <wlandry@caltech.edu> writes:
>>
>> > Dan Čermák <dan.cermak@posteo.net> writes:
>> >
>> >> 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.
>> >
>> > Tree view works well [1]. Everything is fast, and I kind of prefer that
>> > view anyway.
>> >
>> > Thanks,
>> > Walter Landry
>> >
>> > [1] I have been using notmuch for almost a year, and I did not realize
>> > that there is a separate tree view.
>>
>> I have been using notmuch for about two years and iirc didn't realize
>> tree view existed until about half a year ago. Should really have read
>> the manual and all the key bindings at first.
>>
>> > _______________________________________________
>> > notmuch mailing list
>> > notmuch@notmuchmail.org
>> > https://notmuchmail.org/mailman/listinfo/notmuch
>> _______________________________________________
>> notmuch mailing list
>> notmuch@notmuchmail.org
>> https://notmuchmail.org/mailman/listinfo/notmuch
> _______________________________________________
> notmuch mailing list
> notmuch@notmuchmail.org
> https://notmuchmail.org/mailman/listinfo/notmuch
[-- Attachment #2: Type: text/html, Size: 3457 bytes --]
next prev parent reply other threads:[~2019-01-22 17:49 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
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 [this message]
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=AA754A29-A337-4E09-B07B-2242AAD8FC15@evenmere.org \
--to=bts@evenmere.org \
--cc=francesquini@gmail.com \
--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).