From: Tomi Ollila <tomi.ollila@iki.fi>
To: Alan Schmitt <alan.schmitt@polytechnique.org>,
David Bremner <david@tethera.net>,
notmuch <notmuch@notmuchmail.org>
Subject: Re: performance in emacs displaying a huge thread
Date: Wed, 22 Sep 2021 11:25:26 +0300 [thread overview]
Message-ID: <m2o88lrp8p.fsf@guru.guru-group.fi> (raw)
In-Reply-To: <874kaduoht.fsf@m4x.org>
On Wed, Sep 22 2021, Alan Schmitt wrote:
> On 2021-09-21 21:27, Tomi Ollila <tomi.ollila@iki.fi> writes:
>
>> I'd be interested to know if changing max-lisp-eval-depth to a larger value
>> made difference.
>>
>> e.g (set max-lisp-eval-depth 1600)
>
> Thank you for the suggestion. I tried with 1600, and I get a different
> error (and the numbers are larger now).
>
> Debugger entered--Lisp error: (error "Variable binding depth exceeds
> max-specpdl-size")
Now it failed due to exceeding max-specpdl-size (which seems to be 1600
by default)
W/o knowing better I'd try (setq max-specpdl-size 3200) now...
(further tries could be enlarging the values discussed 10-fold...)
Tomi
>
> Best,
>
> Alan
next prev parent reply other threads:[~2021-09-22 8:25 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-15 18:20 performance in emacs displaying a huge thread Alan Schmitt
2020-01-15 20:15 ` Örjan Ekeberg
2020-01-16 7:30 ` Alan Schmitt
2020-02-15 10:26 ` Alan Schmitt
2021-08-02 2:11 ` David Bremner
2021-08-20 7:43 ` Alan Schmitt
2021-08-20 16:55 ` David Bremner
2021-08-21 7:08 ` Alan Schmitt
2021-08-21 13:45 ` David Bremner
2021-09-21 7:59 ` Alan Schmitt
2021-09-21 12:42 ` David Bremner
2021-09-21 14:24 ` Alan Schmitt
2021-09-21 15:38 ` David Bremner
2021-09-21 16:14 ` Alan Schmitt
2021-09-23 1:48 ` David Bremner
2021-09-24 14:04 ` Alan Schmitt
2021-09-24 23:33 ` David Bremner
2021-09-25 7:01 ` Alan Schmitt
2021-09-25 13:26 ` David Bremner
2021-10-06 6:49 ` Alan Schmitt
2021-09-21 18:27 ` Tomi Ollila
2021-09-22 6:13 ` Alan Schmitt
2021-09-22 8:25 ` Tomi Ollila [this message]
2021-09-22 9:41 ` Alan Schmitt
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=m2o88lrp8p.fsf@guru.guru-group.fi \
--to=tomi.ollila@iki.fi \
--cc=alan.schmitt@polytechnique.org \
--cc=david@tethera.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).