emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@gmail.com>
To: "Rudolf Adamkovič" <salutis@me.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 11:06:36 +0800	[thread overview]
Message-ID: <871qrwgptv.fsf@localhost> (raw)
In-Reply-To: <m2pmfgihot.fsf@me.com>

Rudolf Adamkovič <salutis@me.com> writes:

> "Fraga, Eric" <e.fraga@ucl.ac.uk> writes:
>
>> Try M-x toggle-debug-on-quit RET and then export, hitting C-g when it
>> gets stuck.  That'll give you a backtrace which might help debug this.
>
> Thank you Eric.  I tried it and stopped after more than 3 minutes of
> waiting.  The output:
>
> ;; Debugger entered--Lisp error: (quit)
> ;;   org-export--generate-copy-script(#<buffer notebook.org<2>>)
> ;;   org-export-copy-buffer()
> ;;   org-html-format-latex( ...

This does give some useful information.

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

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.

-- 
Ihor Radchenko,
Org mode contributor,
Learn more about Org mode at https://orgmode.org/.
Support Org development at https://liberapay.com/org-mode,
or support my work at https://liberapay.com/yantar92


  reply	other threads:[~2022-09-28  3:06 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 [this message]
2022-09-28 12:45       ` Rudolf Adamkovič
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=871qrwgptv.fsf@localhost \
    --to=yantar92@gmail.com \
    --cc=e.fraga@ucl.ac.uk \
    --cc=emacs-orgmode@gnu.org \
    --cc=salutis@me.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).