[texworks] LaTeXmk issue with Mac OS X Yosemite (new OS)

[Herbert Schulz]

> On Oct 19, 2014, at 9:53 AM, Guillaume Cabanac <guillaume.cabanac at univ-tlse3.fr> wrote:
> 
>> Sigh... there is definitely something wrong with TeXworks under Yosemite! I have had no problem with TeXShop using it's latexmk engines.
> 
> I wanted to check that the environment of the process launched by TeXworks is OK.  So I added a Processing tool called env that launches the env command.  Here is the result
> 
> __CF_USER_TEXT_ENCODING=0x1F5:0x0:0x0
> XPC_SERVICE_NAME=org.tug.texworks.52572
> XPC_FLAGS=0x0
> PATH=/usr/bin:/bin:/usr/sbin:/sbin
> TMPDIR=/var/folders/5g/ylwb62s90y9gb1x3fwrzfy9w0000gn/T/
> LOGNAME=cabanac
> DISPLAY=/private/tmp/com.apple.launchd.GbHpSYBzYd/org.macosforge.xquartz:0
> Apple_PubSub_Socket_Render=/private/tmp/com.apple.launchd.Fa9QpW2bjC/Render
> USER=cabanac
> SHELL=/bin/bash
> SSH_AUTH_SOCK=/private/tmp/com.apple.launchd.2BxPnkxiTM/Listeners
> HOME=/Users/cabanac
> 
> 
> The PATH does not reflect what I find in the "Paths for TeX and related programs" area under the "Typesetting" tab in the settings of TexWorks.  The path "/usr/texbin" shows up in the GUI but it seems not to be passed to the process.
> 
> I had a look into the TWSystemCmd.cpp class in the TeXworks repository:
>  https://code.google.com/p/texworks/source/browse/trunk/src/TWSystemCmd.h
>  https://code.google.com/p/texworks/source/browse/trunk/src/TWSystemCmd.cpp
> 
> As I am not knowledgeable about Qt, I wondered how the process knows about the environment to set up?
> 
> "Certain processes need special environment settings in order to operate. You can set environment variables for your process by calling setEnvironment(). To set a working directory, call setWorkingDirectory(). By default, processes are run in the current working directory of the calling process."  --  http://qt-project.org/doc/qt-5/qprocess.html
> 
> Could it be that one needs to specify the environment of the process in the code? (http://qt-project.org/doc/qt-5/qprocess.html#setProcessEnvironment)
> 
> If yes, why did LaTeXmk in TeXworks worked fine until this Yosemite OS came out?  How could Qt be affected by this update?
> 
> Best,
> 
> Guillaume

Howdy,

It's a bug in Yosemite that was reported to Apple but not fixed in the release. One hopes it will get fixed in an OS update but you never know.

Good Luck,

Herb Schulz
(herbs at wideopenwest dot com)