[dev-context] texexec vs texmfstart texexec.rb

Sanjoy Mahajan sanjoy at mrao.cam.ac.uk
Fri Nov 17 00:41:02 CET 2006

I'm just checking over the context man pages (which Hans sent me off
list) that will go into the next TeXLive.  The main change since the
old (Perl) days is that texexec is now not a standalone program.
Rather, one calls it using texmfstart.  

So people will be confused when they see a man page for texexec but
find no executable with the same name.  Similarly, there's a man page
for texmfstart but no texmfstart executable.  Instead it's a ruby
script texmfstart.rb.

So I think that the default installation should supply the direct
executables.  Here's what I do on Linux (no idea whether any of the
above or below applies to Windows).  For texmfstart:

  ruby `kpsewhich --format=texmfscripts texmfstart.rb` "$@"

For texexec:

  texmfstart texexec.rb "$@"

Both are in ~/bin but ideally for TeXlive they would go to /usr/bin
(or wherever TeXlive puts things).


`Never underestimate the evil of which men of power are capable.'
         --Bertrand Russell, _War Crimes in Vietnam_, chapter 1.

More information about the dev-context mailing list