From: "Rudolf Adamkovič" <salutis@me.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: "Fraga, Eric" <e.fraga@ucl.ac.uk>,
"emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: The Org mode in the Org Git does not export
Date: Wed, 28 Sep 2022 14:45:19 +0200 [thread overview]
Message-ID: <m28rm3hdls.fsf@me.com> (raw)
In-Reply-To: <871qrwgptv.fsf@localhost>
Ihor Radchenko <yantar92@gmail.com> writes:
Thank you for helping me out.
Context:
With all this talk about Emacs 29 around the corner, I became scared
that the upcoming Org will render my Org notes unusable. Hence, I
decided to ask now, before it happens.
> Can you
> 1. M-x debug-on-entry <RET> org-export--generate-copy-script <RET>
> 2. Start export
> 3. Step into the function (use "d", not "c" binding)
> 4. Try to identify which part (if any) is being slow
FYI: I had to do "(require 'ox)" before this worked.
I spent about 30 minutes pressing "d". I saw Org sorting some character
encodings in a large number of steps, and then it started doing a large
number of various tasks, spending time in the AVL tree, etc. I have no
idea what else to do.
I could not figure out how to step through N times at once for N > 1. I
tried 'C-9 C-9 d' to step through 99 times, but that did not work. The
documentation for 'debugger-step-through' contains just two sentences,
and I do not even understand the second one:
"Proceed, stepping through subexpressions of this expression. Enter
another debugger on next entry to eval, apply or funcall."
> If the above does not work, you can also try
> 1. M-x trace-function <RET> org-export--generate-copy-script <RET>
> 2. M-x elp-instrument-function <RET> org-export--generate-copy-script
> <RET>
> 2. Run export, possibly terminating it with C-g in the process
> 3. M-x elp-results <RET>
> 4. Share the contents of the trace buffer and the contents of the
> elp-results buffer.
So, I ran the export for 17 minutes and then terminated with 'C-g'. The
trace buffer included a very long line, which made Emacs froze, and I
had to kill it, after waiting for 5 minutes, losing all data in the
process.
I then tried to run the export for 3 minutes, and I managed to copy the
trace buffer, but upon pasting it into another buffer, Emacs froze
again, and I had to kill it again, losing data once again.
I then ran the export for 3 minutes once again, this time enabling just
the 'elp-instrument-function' to avoid freezing. The 'elp-results'
output:
> org-export--generate-copy-script 1221 2.8268540000 0.0023151957
(The buffer also contains a header line, with e.g. "Function Name", but
Emacs did not allow me to select and copy it for you.)
Rudy
--
"Mathematics takes us still further from what is human into the region
of absolute necessity, to which not only the actual world, but every
possible world, must conform."
-- Bertrand Russell, 1902
Rudolf Adamkovič <salutis@me.com> [he/him]
Studenohorská 25
84103 Bratislava
Slovakia
next prev parent reply other threads:[~2022-09-28 14:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-25 16:40 The Org mode in the Org Git does not export Rudolf Adamkovič
2022-09-25 17:06 ` Fraga, Eric
2022-09-27 22:19 ` Rudolf Adamkovič
2022-09-28 3:06 ` Ihor Radchenko
2022-09-28 12:45 ` Rudolf Adamkovič [this message]
2022-09-28 12:55 ` Rudolf Adamkovič
2022-09-28 13:24 ` Ihor Radchenko
2022-09-28 15:49 ` Max Nikulin
2022-09-28 13:14 ` Ihor Radchenko
2022-09-28 15:56 ` Rudolf Adamkovič
2022-09-28 17:29 ` Rudolf Adamkovič
2022-09-29 2:30 ` Ihor Radchenko
2022-09-29 13:37 ` Rudolf Adamkovič
2022-09-29 13:56 ` Ihor Radchenko
2022-09-30 12:01 ` Rudolf Adamkovič
2022-10-01 3:02 ` Ihor Radchenko
2022-10-01 18:04 ` Rudolf Adamkovič
2022-10-07 5:31 ` Ihor Radchenko
2022-10-07 9:10 ` Rudolf Adamkovič
2022-10-07 10:24 ` Ihor Radchenko
2022-10-07 14:18 ` Rudolf Adamkovič
2022-10-09 6:36 ` Ihor Radchenko
2022-10-09 15:29 ` Rudolf Adamkovič
2022-10-10 10:15 ` Ihor Radchenko
2022-10-10 22:08 ` Rudolf Adamkovič
2022-09-26 4:39 ` Ihor Radchenko
2022-09-27 22:30 ` Rudolf Adamkovič
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://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m28rm3hdls.fsf@me.com \
--to=salutis@me.com \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.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).