From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Gemini Lasswell <gazally@runbox.com>,
36566@debbugs.gnu.org, Noam Postavsky <npostavs@gmail.com>,
Stefan Monnier <monnier@IRO.UMontreal.CA>
Subject: bug#36566: 27.0.50; debug is sometimes horribly slow
Date: Wed, 27 Apr 2022 14:28:31 +0200 [thread overview]
Message-ID: <874k2ed828.fsf@gnus.org> (raw)
In-Reply-To: <87k0bb16jc.fsf@web.de> (Michael Heerdegen's message of "Wed, 27 Apr 2022 06:42:15 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
>> Result: stepping over any evaluation of the variable `data` takes a few
>> seconds.
>
> Is that time spent in printing? I experience that from time to time,
> too, but I thought it might be related to my config. Should we maybe
> create a new report for that and close this one?
Yup, sounds good to me, so I'm closing this one.
A case to reproduce the problem that doesn't require org files would be
nice. `data' in the example here is a parse tree, so perhaps the
slowness is in printing tree-like structures? (But I haven't actually
tried to debug this.)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-04-27 12:28 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 3:09 bug#36566: 27.0.50; debug is sometimes horribly slow Michael Heerdegen
2019-07-10 3:18 ` Drew Adams
2019-07-10 11:20 ` Noam Postavsky
2019-07-10 22:46 ` Michael Heerdegen
2019-07-14 0:02 ` Gemini Lasswell
2019-07-15 2:05 ` Michael Heerdegen
2019-08-01 1:06 ` Gemini Lasswell
2019-08-01 0:53 ` Gemini Lasswell
2019-08-01 1:05 ` Noam Postavsky
2019-08-05 19:53 ` Gemini Lasswell
2019-08-19 1:30 ` Noam Postavsky
2019-09-06 16:41 ` Gemini Lasswell
2019-09-11 2:54 ` Noam Postavsky
2019-09-13 21:08 ` Gemini Lasswell
2019-09-14 13:44 ` Mauro Aranda
2019-09-14 14:05 ` Eli Zaretskii
2019-09-14 14:16 ` Mauro Aranda
2019-09-14 15:47 ` Eli Zaretskii
2022-04-25 14:41 ` Lars Ingebrigtsen
2022-04-25 23:23 ` Michael Heerdegen
2022-04-27 0:37 ` Gemini Lasswell
2022-04-27 4:42 ` Michael Heerdegen
2022-04-27 12:28 ` Lars Ingebrigtsen [this message]
2022-04-28 17:56 ` Gemini Lasswell
2022-05-13 16:01 ` Lars Ingebrigtsen
2022-05-14 3:57 ` Michael Heerdegen
2022-05-14 11:35 ` Lars Ingebrigtsen
2022-05-14 13:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-14 15:45 ` Lars Ingebrigtsen
2022-05-14 16:05 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-14 16:18 ` Lars Ingebrigtsen
2022-05-14 16:54 ` Lars Ingebrigtsen
2022-05-14 18:55 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-15 12:25 ` Lars Ingebrigtsen
2022-05-15 13:33 ` Lars Ingebrigtsen
2022-05-15 16:13 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-15 16:25 ` Lars Ingebrigtsen
2022-05-15 16:52 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-16 1:00 ` Lars Ingebrigtsen
2022-05-16 1:39 ` Michael Heerdegen
2022-05-16 1:44 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-05-16 12:11 ` Lars Ingebrigtsen
2022-05-15 7:47 ` Rudolf Schlatte
2022-05-15 12:28 ` Lars Ingebrigtsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874k2ed828.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=36566@debbugs.gnu.org \
--cc=gazally@runbox.com \
--cc=michael_heerdegen@web.de \
--cc=monnier@IRO.UMontreal.CA \
--cc=npostavs@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.