<html><body><div><br></div><div><br>On October 20, 2020 at 11:31 AM, Joseph Wright <joseph.wright@morningstar2.co.uk> wrote:<br><br></div><div><blockquote type="cite"><div class="msg-quote"><div class="_stretch"><span class="body-text-content">On 20/10/2020 19:25, Joseph Wright wrote:<br><blockquote class="quoted-plain-text" type="cite">On 20/10/2020 18:49, Adam R. Maxwell wrote:</blockquote><blockquote class="quoted-plain-text" type="cite"><blockquote class="quoted-plain-text" type="cite">If my response to Paulo is still correct, I think this is a bug in</blockquote></blockquote><blockquote class="quoted-plain-text" type="cite"><blockquote class="quoted-plain-text" type="cite">TeXWorks. It needs to set up a correct PATH variable for child</blockquote></blockquote><blockquote class="quoted-plain-text" type="cite"><blockquote class="quoted-plain-text" type="cite">processes that it launches, if they in turn can execute child</blockquote></blockquote><blockquote class="quoted-plain-text" type="cite"><blockquote class="quoted-plain-text" type="cite">processes (although there are significant security implications for</blockquote></blockquote><blockquote class="quoted-plain-text" type="cite"><blockquote class="quoted-plain-text" type="cite">this). GUI applications on Mac OS X do not inherit environment</blockquote></blockquote><blockquote class="quoted-plain-text" type="cite"><blockquote class="quoted-plain-text" type="cite">variables from shell config files: the developer needs to provide an</blockquote></blockquote><blockquote class="quoted-plain-text" type="cite"><blockquote class="quoted-plain-text" type="cite">interface to set the environment appropriate (including the PATH);</blockquote></blockquote><blockquote class="quoted-plain-text" type="cite"><blockquote class="quoted-plain-text" type="cite">TextMate is a good example of how to do this. Alternately, maybe</blockquote></blockquote><blockquote class="quoted-plain-text" type="cite"><blockquote class="quoted-plain-text" type="cite">Joseph could wrap biber in a shell script that sets up a good</blockquote></blockquote><blockquote class="quoted-plain-text" type="cite"><blockquote class="quoted-plain-text" type="cite">environment.</blockquote></blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">For the TeXworks list: Dick Koch (TeXShop developer) gave some info on</blockquote><blockquote class="quoted-plain-text" type="cite">how it works in TeXShop. Rather than try the above, he has a couple of</blockquote><blockquote class="quoted-plain-text" type="cite">dedicated entries in the GUI: one for the TeX binaries, one for</blockquote><blockquote class="quoted-plain-text" type="cite">GhostScript. That's slightly different to how TeXworks operates, of course.</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">Seems I will have to go with the Terminal-lauch idea or (more likely)</blockquote><blockquote class="quoted-plain-text" type="cite">just run Biber at the Terminal when I need it.</blockquote><blockquote class="quoted-plain-text" type="cite"><br></blockquote><blockquote class="quoted-plain-text" type="cite">Joseph</blockquote><br>Ah, sorry, re-reading I guess Adam was suggesting more or less what <br>TeXShop does, just expressed slightly differently. For reference, <br>TextMate has a small dialogue that covers a few variables (see attached).</span></div></div></blockquote></div><div><span><br data-mce-bogus="1"></span></div><div><span><br data-mce-bogus="1"></span></div><div><span>Yeah, it just lets you specify arbitrary variables; I was thinking of your prior</span></div><div><span>message about trying to frob environment variables, and this is how you</span></div><div><span>could set that up in a GUI. It's not user-friendly, though, especially for</span></div><div><span>choosing paths.</span></div><div><span><br data-mce-bogus="1"></span></div><div><span>For TeX Live Utility, I just allow choosing a single path to "TeX programs" in</span></div><div><span>the GUI (set to /Library/TeX/texbin by default, so it Just Works for MacTeX).</span></div><div><span>I construct a full path to tlmgr as needed at </span><span>runtime, and also add the</span></div><div><span>user-specified value to PATH so that when I execute tlmgr it can find</span></div><div><span>updmap/kpsewhich/etc. Sadly, you may need to sanitize the environment</span></div><div><span>or prepend to PATH (not great for security) if you do anything complex, as</span></div><div><span>clever </span><span>users have broken things so I get tlmgr from TeX Live and a </span><span>kpsewhich</span></div><div><span>from homebrew or MacPorts. That's super fun to debug via email.</span></div><div><span><br data-mce-bogus="1"></span></div><div><span>regards,</span></div><div><span>Adam</span></div><div><span><br data-mce-bogus="1"></span></div><div><span><br data-mce-bogus="1"></span></div><div><span></span></div><div><blockquote type="cite"><div class="msg-quote"></div></blockquote></div></body></html>