Jean Magnan de Bornier wrote:
Le 29 mai � 13:47:04 gnwiii@gmail.com �crit notamment:
| On my systems, teTeX-3 does not include a texmfstart executable. One approach | is to copy the texmfstart.rb script to "texmfstart" in a directory on your PATH.
| Earlier, I posted a script I have been testing to the list. The | script uses kpsewhich | to find the .rb or .pl script corresponding to the name used to invoke | the script, and then runs perl or ruby with the full path to the | script. This saves having to copy the scripts everytime you update | context.
Thank you and Hans, I'll look for your script asa I go back to my other machine; I must confess (no criticism) that I'm a bit surprised things like that are left to every user to deal with, as the rest of context is so elaborated. cheers,
well, the problem is that each distribution does it different; the whole idea behind texmfstart is that one you have that one script running, all others should work as well since one cna say: texmfstart texexec somefile to process a file,and similarily: texmfstart ctxtools texmfstart rlxtools texmfstart pdftools texmfstart tmftools texmfstart textools texmfstart pstopdf and what else is distributed with context 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 -----------------------------------------------------------------