Johannes Graumann wrote:
>
> 4) I have also added '~/texmf/scripts/context/stubs/unix' to my path to make
> the stubs residing therein accessible on the command line. 'which texexec'
> now returns
> ~/texmf/scripts/context/stubs/unix/texexec
> Which seems right.
> Also added to the path '~/texmf/scripts/context/ruby'. 'which texexec.rb'
> now returns
> ~/texmf/scripts/context/ruby/texexec.rb
> However, just calling 'texexec document.tex' does not work - NOTHING
> happens, new prompt, no errors.
> Same thing with 'texmfstart texexec.rb document.tex' - which is the command
> the 'texexec'-stub actually calls.
>
strange indeed, so what does
texmfstart --verbose texexec.rb --verbose document.tex
tell you
> I'm at the end of my knowledge and intuition. Can anybody help circumventing
> the need for the monster 'ruby ~/texmf/scripts/context/ruby/texexec.rb
> document.tex'?
>
oh, we'll find a way, esp since it has worked on my linux boxes for a few years
now
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
-----------------------------------------------------------------
_______________________________________________
ntg-context mailing list
ntg-context@ntg.nl
http://www.ntg.nl/mailman/listinfo/ntg-context
