# [OS X TeX] New Packages for Feb 12

Steffen Wolfrum osxtex_2 at st.estfiles.de
Tue Feb 20 06:36:56 EST 2007

No, this doesn't change anything.

While figuring out where the problem ends I just experienced that it is the same not only for ConTeXt but also for LaTeX files:

Once again: Create test.tex and file.tex as below and process (LaTeX) test.tex …

1) test.tex
\documentclass[11pt]{article}
\begin{document}
\input file.tex
\end{document}

2) file.tex
some text

… with TeXShop 2.09d it is done immediately, but with 2.10 not even a console window pops up:
the hit button "Typeset" stays blue/pressed and after two second the beachball starts spinning!

Don't you experience the same?

Steffen

On Tue, 20 Feb 2007 09:46:26 +0000, Jonathan Kew wrote:
> On 20 Feb 2007, at 9:18 am, Steffen Wolfrum wrote:
>
>> I know, TeXShop is just a front-end for processing programs like (im
>> my case) …
>>
>> #!/bin/tcsh
>>
>> set path= ($path /usr/local/TeXLive/bin/i386-apple-darwin-current >> /usr/local/bin) >> texmfstart texexec "$1"
>
> There's a possible problem with this: it *appends* a TeX binaries
> directory to the current path, which means that if your path already
> includes some other (old?) TeX binaries directory, maybe from a
> different distribution, you may not be running the programs you think.
>
> Personally, I use engine scripts in TeXShop that do *not* set the
> path at all, and instead rely on having the directories I want
> already present in my default path. If I do want to ensure that an
> engine uses binaries from a particular (non-default) location, then I
> have the engine script *prefix* that directory to the path.
>
> Don't know if this explains your problems, but it may be worth
> checking paths carefully.
>
> BTW, with the newest distributions, the recommended approach is to
> use /usr/texbin as the path for TeX-related binaries; see the
> documentation about the TeX Distributions pref panel, paths, etc.
>
> JK