From: "R. Bastian" <rbastian@free.fr>
To: ConTeXt <ntg-context@ntg.nl>
Subject: Re: texexec slow
Date: Thu, 23 Apr 2009 14:37:52 +0200 [thread overview]
Message-ID: <20090423143752.75be6f4e@KUBUNTU64> (raw)
In-Reply-To: <6faad9f00904230332p21279574ud33a2b508955d69c@mail.gmail.com>
On Thu, 23 Apr 2009 12:32:23 +0200
Mojca Miklavec <mojca.miklavec.lists@gmail.com> scribit:
> On Thu, Apr 23, 2009 at 12:29, Mojca Miklavec
> <mojca.miklavec.lists@gmail.com> wrote:
> >> Th script installed 158 Mb with a new 'texexec' (controlled with 'which texexec').
> >> But it is not a bit faster. After 3 min, I break (Ctrl-C) ...
> >>
> >> ruby --version => ruby 1.8.7 ... instantaneous
> >
> > ruby --version is definitely faster, but texexec --version takes about
> > a second here.
> >
> > Running a two-page document for the second time takes 3 seconds here.
> > (The first run is a bit slower.)
> >
> > Can you post the document and some logfile to the mailing list? It may
> > happen that you run into some infinite loop with one of your macros.
>
> Please also describe what platform you work on. With luatex memory
> might also be an issue, but that's probably not the case with pdftex.
I tested 'texexec' on another computer (Kubuntu 7.10, TL2007, ruby 1.8.6) and it works,
but I need it on [Debian 5.0, Gnome, ruby 1.8.7] where it fails.
>
> What's the time needed to run pdflatex on similar document size?
I dont know; 'first-setup.sh' erased the path to the format files ;-)
but 'pdflatex' was very clever. (I must reinstall 'texlive'.)
>
> Mojca
>
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://tex.aanhet.net
archive : https://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2009-04-23 12:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-23 8:24 R. Bastian
2009-04-23 8:48 ` Hans Hagen
2009-04-23 9:08 ` R. Bastian
[not found] ` <6faad9f00904230222q166fbd8cvaf90f9ed7bca15f2@mail.gmail.com>
[not found] ` <20090423122232.5e7cdbc0@KUBUNTU64>
[not found] ` <6faad9f00904230329r6c31c5a3h4dfb2dbda1d998af@mail.gmail.com>
[not found] ` <6faad9f00904230332p21279574ud33a2b508955d69c@mail.gmail.com>
2009-04-23 12:37 ` R. Bastian [this message]
2009-04-23 14:26 ` Aditya Mahajan
2009-04-23 14:55 ` R. Bastian
2009-04-23 15:10 ` R. Bastian
2009-04-23 17:32 ` R. Bastian
2009-04-23 21:19 ` Mojca Miklavec
2009-04-24 6:36 ` Taco Hoekwater
2009-04-24 9:17 ` Mojca Miklavec
2009-04-23 17:40 ` Hans Hagen
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=20090423143752.75be6f4e@KUBUNTU64 \
--to=rbastian@free.fr \
--cc=ntg-context@ntg.nl \
/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.
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 NNTP newsgroup(s).