Hello, "texexec --check" takes about 2 minutes on my system and there are a lot of warnings like: /opt/teTeX/texmf-context/scripts/context/ruby/base/kpserunner.rb:68: warning: string pattern instead of regexp; metacharacters no longer effective /opt/teTeX/texmf-context/scripts/context/ruby/base/kpsefast.rb:322: warning: string pattern instead of regexp; metacharacters no longer effective /opt/teTeX/texmf-context/scripts/context/ruby/base/kpsefast.rb:457: warning: string pattern instead of regexp; metacharacters no longer effective and so on. Cheers, Peter -- http://pmrb.free.fr/contact/
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 Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.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/
� wrote:
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
the unsets are ok, they result from unset engine or progname vars; i wonder what separator is used btw, interesting path, what does kpsewhich -show-path=fmt return? -- ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com | www.pragma-pod.nl -----------------------------------------------------------------
On Thu, 11 May 2006, Hans Hagen wrote:
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
btw, interesting path, what does
kpsewhich -show-path=fmt
return?
It returns: .:!!/home/peter/.texmf-config/web2c/unset:!!/home/peter/.texmf-var/web2c/unset:/home/peter/texmf/web2c/unset:!!/opt/teTeX/texmf-config/web2c/unset:!!/opt/teTeX/texmf-var/web2c/unset:!!/opt/teTeX/texmf/web2c/unset:!!/opt/teTeX/texmf-local/web2c/unset:!!/opt/teTeX/texmf-context/web2c/unset:!!/opt/teTeX/texmf-dist/web2c/unset:!!/home/peter/.texmf-config/web2c/:!!/home/peter/.texmf-var/web2c/:/home/peter/texmf/web2c/:!!/opt/teTeX/texmf-config/web2c/:!!/opt/teTeX/texmf-var/web2c/:!!/opt/teTeX/texmf/web2c/:!!/opt/teTeX/texmf-local/web2c/:!!/opt/teTeX/texmf-context/web2c/:!!/opt/teTeX/texmf-dist/web2c/ Peter -- http://pmrb.free.fr/contact/
After an update to ConTeXt 2006.05.11, "texexec --check" is fast and gives more information. Thank you! Peter -- http://pmrb.free.fr/contact/
On Thu, 11 May 2006, Taco Hoekwater wrote:
Peter Münster wrote:
"texexec --check" takes about 2 minutes on my system and there are a lot of warnings like:
What version of ruby?
1.8.0 I've made an update to 1.8.2 and the warnings are gone, thanks! Cheers, Peter -- http://pmrb.free.fr/contact/
participants (3)
-
Hans Hagen -
Peter Münster -
Taco Hoekwater