From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Alan Mackenzie <acm@muc.de>, emacs-devel@gnu.org
Subject: Re: Reworking loaddefs.el generation
Date: Wed, 01 Jun 2022 07:13:37 +0200 [thread overview]
Message-ID: <87ee092cfy.fsf@gnus.org> (raw)
In-Reply-To: <jwv7d615xx9.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Tue, 31 May 2022 15:04:58 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> The generation of `org.texi` from `org.org` is excruciatingly
> slow, indeed. Maybe we can better hide that latency with a more careful
> scheduling, but maybe we could also try to speed it up: I mean if you
> compare it to the time it takes for texi2pdf to process the result it's
> rather shameful (after all, the generation of the `org.texi` seems
> algorithmically a lot simpler).
If somebody want to poke at this, then perhaps this is a good starting
point:
(progn
(require 'ox-texinfo)
(with-temp-buffer
(insert-file-contents "~/src/emacs/trunk/doc/misc/org.org")
(setq default-directory (expand-file-name "~/src/emacs/trunk/doc/misc/"))
(profiler-start 'cpu)
(org-export-to-file 'texinfo "/tmp/org.texi"))
(profiler-stop)
(profiler-report))
1564 19% - org-export-resolve-fuzzy-link
looks pretty suspicious, for instance. (And that thing should have an
easier calling convention...)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2022-06-01 5:13 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-27 10:53 Reworking loaddefs.el generation Lars Ingebrigtsen
2022-05-27 12:03 ` Andreas Schwab
2022-05-27 12:17 ` Lars Ingebrigtsen
2022-05-27 12:43 ` Stefan Monnier
2022-05-27 13:00 ` Lars Ingebrigtsen
2022-05-31 16:10 ` Lars Ingebrigtsen
2022-05-31 16:33 ` Lars Ingebrigtsen
2022-05-31 16:53 ` Lars Ingebrigtsen
2022-05-31 17:32 ` Eli Zaretskii
2022-05-31 17:40 ` Lars Ingebrigtsen
2022-05-31 18:09 ` Lars Ingebrigtsen
2022-05-31 19:24 ` Eli Zaretskii
2022-05-31 19:33 ` Lars Ingebrigtsen
2022-06-01 2:26 ` Eli Zaretskii
2022-06-01 2:29 ` Lars Ingebrigtsen
2022-06-01 11:40 ` Eli Zaretskii
2022-06-01 12:13 ` Lars Ingebrigtsen
2022-06-01 19:02 ` Eli Zaretskii
2022-06-02 9:14 ` Lars Ingebrigtsen
2022-05-31 18:44 ` Alan Mackenzie
2022-05-31 18:47 ` Lars Ingebrigtsen
2022-06-01 3:55 ` Lars Ingebrigtsen
2022-06-01 5:43 ` Lars Ingebrigtsen
2022-06-01 11:16 ` Lars Ingebrigtsen
2022-06-01 11:26 ` Lars Ingebrigtsen
2022-06-01 12:00 ` Andreas Schwab
2022-06-01 12:10 ` Lars Ingebrigtsen
2022-06-01 14:23 ` Lars Ingebrigtsen
2022-06-01 11:47 ` Stefan Monnier
2022-06-01 12:09 ` Lars Ingebrigtsen
2022-05-31 19:04 ` Stefan Monnier
2022-06-01 5:13 ` Lars Ingebrigtsen [this message]
2022-06-01 11:07 ` Eli Zaretskii
2022-06-01 12:29 ` Lars Ingebrigtsen
2022-05-31 19:00 ` Lars Ingebrigtsen
2022-05-31 19:12 ` 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=87ee092cfy.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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.