all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: how to build emacs without documentation?
Date: Tue, 13 Aug 2013 19:32:02 +0300	[thread overview]
Message-ID: <83a9klpn5p.fsf@gnu.org> (raw)
In-Reply-To: <jwvzjslir38.fsf-monnier+gnu.emacs.help@gnu.org>

> From: Stefan Monnier <monnier@iro.umontreal.ca>
> Date: Tue, 13 Aug 2013 10:51:51 -0400
> 
> As for "info", well, that was pretty much immediate until Texinfo-5.0
> came along.  So you might like to downgrade to Texinfo-4.x to enjoy
> a more normal speed.

I renamed the new makeinfo to makeinfo5, and keep the old v4.x one
under the name makeinfo.

> I still have no idea how they managed to slow things down so much.

Because they implemented makeinfo in Perl, and made it a real
translator, that builds an intermediate parse tree representation, and
then invokes an appropriate back-end to produce output.  By contrast,
the original makeinfo was a one-pass converter which left most of the
text intact and just acted on the few directives, expanding them
in-line.

> It feels like it's a good 100 times slower.  Actual measurement will
> probably show the slowdown factor to be smaller, but still the
> difference is insane.

The slowdown factor is around 18.



  parent reply	other threads:[~2013-08-13 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.3001.1376231269.12400.help-gnu-emacs@gnu.org>
2013-08-13 14:51 ` how to build emacs without documentation? Stefan Monnier
2013-08-13 15:26   ` Rustom Mody
2013-08-13 16:32   ` Eli Zaretskii [this message]
     [not found]   ` <mailman.3136.1376411515.12400.help-gnu-emacs@gnu.org>
2013-08-14 16:49     ` Stefan Monnier
2013-08-14 17:56       ` Eli Zaretskii
2013-08-11 14:27 Gregor Zattler
2013-08-13 15:52 ` Glenn Morris

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=83a9klpn5p.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=help-gnu-emacs@gnu.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 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.