From: "Peter Münster" <pmlists@free.fr>
Subject: Re: texexec --check
Date: Thu, 11 May 2006 18:29:30 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.58.0605111822330.818@gaston.pm> (raw)
In-Reply-To: <4462E8D0.5050105@wxs.nl>
On Thu, 11 May 2006, Hans Hagen wrote:
> Taco Hoekwater wrote:
> > Peter M?nster wrote:
> >
> >> Hello,
> >>
> >> "texexec --check" takes about 2 minutes on my system and there are a lot of
> >> warnings like:
> >>
> >
> > What version of ruby?
> >
> what does
>
> texmfstart --verbose texexec
>
> report? if it takes long, texmfstart will do a rather extensive search on disk
No, this call is very fast. Complete output:
texmfstart version 1.8.6
locating 'texexec.rb' in current path '.'
locating 'texexec.rb' in caller path '/usr/local/bin'
using direct kpse
using 'kpsewhich' to locate 'texexec' in suffix space 'rb' (1)
registering 'texexec' as '/opt/teTeX/texmf-context/scripts/context/ruby/texexec.rb'
registering 'THREAD' as '/opt/teTeX/texmf-context/scripts/context/ruby'
starting texexec.rb
using 'system' call: ruby /opt/teTeX/texmf-context/scripts/context/ruby/texexec.rb
TeXExec | version 6.2.0 - 1997-2006 - PRAGMA ADE/POD
TeXExec | --check check versions
TeXExec | --figures generate overview of figures
TeXExec | --listing list of file content
TeXExec | --make make formats
TeXExec | --modules generate module documentation
TeXExec | --mptex process mp file
TeXExec | --mpxtex process mpx file
TeXExec | --pdfarrange impose pages (booklets)
TeXExec | --pdfcombine combine multiple pages
TeXExec | --pdfcopy copy pages from file(s)
TeXExec | --pdfselect select pages from file(s)
TeXExec | --pdftrim trim pages from file(s)
TeXExec | --process process file
Now, after the ruby update, "texexec --check" takes still a long time. Here
is the complete output:
TeXExec | current distribution: web2c
TeXExec | context source date: unknown
TeXExec | format path: . /home/peter/.texmf-config/web2c/unset /home/peter/.texmf-config/web2c /home/peter/.texmf-var/web2c/unset /home/peter/.texmf-var/web2c /home/peter/texmf/web2c/unset /home/peter/texmf/web2c /texmf-config/web2c/unset /texmf-config/web2c /texmf-var/web2c/unset /texmf-var/web2c /texmf/web2c/unset /texmf/web2c /texmf-local/web2c/unset /texmf-local/web2c /texmf-context/web2c/unset /texmf-context/web2c /texmf-dist/web2c/unset /texmf-dist/web2c
TeXExec | start of analysis
TeXExec | end of analysis
TeXExec |
TeXExec | TeXExec | version 6.2.0 - 1997-2006 - PRAGMA ADE/POD
TeXExec | TeXUtil | version 9.1.0 - 1997-2005 - PRAGMA ADE/POD
TeXExec | CtxTools | version 1.3.2 - 2004/2006 - PRAGMA ADE/POD
It takes a lot of time between "start of analysis" and "end of analysis".
The format path seems strange to me with all the "unset" at the end.
Cheers, Peter
--
http://pmrb.free.fr/contact/
next prev parent reply other threads:[~2006-05-11 16:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 19:26 Peter Münster
2006-05-11 6:37 ` Taco Hoekwater
2006-05-11 7:33 ` Hans Hagen
2006-05-11 16:29 ` Peter Münster [this message]
2006-05-11 18:39 ` Hans Hagen
2006-05-11 19:01 ` Peter Münster
2006-05-11 18:48 ` Peter Münster
2006-05-11 16:22 ` Peter Münster
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=Pine.LNX.4.58.0605111822330.818@gaston.pm \
--to=pmlists@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).