Hello again, Seems I am still having some trouble with the latex bundle. Basically, the first time I attempt to typeset after launching textmate, I get:
================================================== The current PATH is:
/usr/bin /bin /usr/sbin /sbin Please add the directory containing “kpsewhich” to PATH in TextMate's Shell Variables preferences.
Alternatively, the PATH can be retrieved from Terminal but this requires a relaunch: (button to perform this operation) ==================================================
Now as a matter of fact the correct path is present in my shell variables in textmate's preferences (in "shell variables" under "advanced"), as opposed to just /usr/bin, /bin and sbin as mentioned in the message; furthermore, it is already in my usual PATH. If I do click on the button, it quits and restarts and everything is ok. Checking the preferences, a new PATH var has been added, containing my shell path. This addition occurs even if the exact same path variable is already present in textmate's preferences.
If I now quit and restart textmate, the same process is repeated, and a new path variable added to the preferences before I can typeset (identical to the other ones already there), and everything works after that, until I quit again, and so on.
This did not happen before I updated my latex and support bundles.
Maybe I'm just being thick, but I can't see what is going on, and this is starting to get annoying. Any ideas?
On Nov 18, 2008, at 5:40 PM, Achilleas Lazarides wrote:
Hello again, Seems I am still having some trouble with the latex bundle. Basically, the first time I attempt to typeset after launching textmate, I get:
================================================== The current PATH is:
/usr/bin /bin /usr/sbin /sbin Please add the directory containing “kpsewhich” to PATH in TextMate's Shell Variables preferences.
Alternatively, the PATH can be retrieved from Terminal but this requires a relaunch: (button to perform this operation) ==================================================
Now as a matter of fact the correct path is present in my shell variables in textmate's preferences (in "shell variables" under "advanced"), as opposed to just /usr/bin, /bin and sbin as mentioned in the message; furthermore, it is already in my usual PATH. If I do click on the button, it quits and restarts and everything is ok. Checking the preferences, a new PATH var has been added, containing my shell path. This addition occurs even if the exact same path variable is already present in textmate's preferences.
If I now quit and restart textmate, the same process is repeated, and a new path variable added to the preferences before I can typeset (identical to the other ones already there), and everything works after that, until I quit again, and so on.
This did not happen before I updated my latex and support bundles.
Maybe I'm just being thick, but I can't see what is going on, and this is starting to get annoying. Any ideas?
Update TextMate to bleeding edge by ⌥+Click (Option+click) the “Check for updates…” button in TextMate's Software Update preference pane.
—Alex
On 19/11/2008, at 4:58 AM, Alex Ross wrote:
On Nov 18, 2008, at 5:40 PM, Achilleas Lazarides wrote:
Hello again, Seems I am still having some trouble with the latex bundle. Basically, the first time I attempt to typeset after launching textmate, I get:
================================================== The current PATH is:
/usr/bin /bin /usr/sbin /sbin Please add the directory containing “kpsewhich” to PATH in TextMate's Shell Variables preferences.
Alternatively, the PATH can be retrieved from Terminal but this requires a relaunch: (button to perform this operation) ==================================================
Now as a matter of fact the correct path is present in my shell variables in textmate's preferences (in "shell variables" under "advanced"), as opposed to just /usr/bin, /bin and sbin as mentioned in the message; furthermore, it is already in my usual PATH. If I do click on the button, it quits and restarts and everything is ok. Checking the preferences, a new PATH var has been added, containing my shell path. This addition occurs even if the exact same path variable is already present in textmate's preferences.
If I now quit and restart textmate, the same process is repeated, and a new path variable added to the preferences before I can typeset (identical to the other ones already there), and everything works after that, until I quit again, and so on.
This did not happen before I updated my latex and support bundles.
Maybe I'm just being thick, but I can't see what is going on, and this is starting to get annoying. Any ideas?
Update TextMate to bleeding edge by ⌥+Click (Option+click) the “Check for updates…” button in TextMate's Software Update preference pane.
I had the same problem and updating to the cutting edge did not help. I had to include /usr/texbin in the path in ~/.MacOSX/environment.plist
All the best
Guido -- Guido Governatori http://www.governatori.net/Textmate
On Nov 18, 2008, at 9:14 PM, Guido Governatori wrote:
On 19/11/2008, at 4:58 AM, Alex Ross wrote:
On Nov 18, 2008, at 5:40 PM, Achilleas Lazarides wrote:
Hello again, Seems I am still having some trouble with the latex bundle. Basically, the first time I attempt to typeset after launching textmate, I get:
================================================== The current PATH is:
/usr/bin /bin /usr/sbin /sbin Please add the directory containing “kpsewhich” to PATH in TextMate's Shell Variables preferences.
Alternatively, the PATH can be retrieved from Terminal but this requires a relaunch: (button to perform this operation) ==================================================
Now as a matter of fact the correct path is present in my shell variables in textmate's preferences (in "shell variables" under "advanced"), as opposed to just /usr/bin, /bin and sbin as mentioned in the message; furthermore, it is already in my usual PATH. If I do click on the button, it quits and restarts and everything is ok. Checking the preferences, a new PATH var has been added, containing my shell path. This addition occurs even if the exact same path variable is already present in textmate's preferences.
If I now quit and restart textmate, the same process is repeated, and a new path variable added to the preferences before I can typeset (identical to the other ones already there), and everything works after that, until I quit again, and so on.
This did not happen before I updated my latex and support bundles.
Maybe I'm just being thick, but I can't see what is going on, and this is starting to get annoying. Any ideas?
Update TextMate to bleeding edge by ⌥+Click (Option+click) the “Check for updates…” button in TextMate's Software Update preference pane.
I had the same problem and updating to the cutting edge did not help. I had to include /usr/texbin in the path in ~/.MacOSX/ environment.plist
Updating to cutting edge is not enough. You have to ⌥+Click (Option +Click) the “Check now” button in the Software Update prefpane. This downloads a special TM build that corrects a bug with the way TextMate puts Shell Variables into the environment. After this, setting “PATH” in the Shell Variables section of preferences is enough.
—Alex
Le 18 nov. 08 à 21:36, Alex Ross a écrit :
Updating to cutting edge is not enough. You have to ⌥+Click (Option +Click) the “Check now” button in the Software Update prefpane. This downloads a special TM build that corrects a bug with the way TextMate puts Shell Variables into the environment. After this, setting “PATH” in the Shell Variables section of preferences is enough.
Hi
With 1.5.7 I 've no problem but with 1.5.8 i've the same error :
Please add the directory containing “kpsewhich” to PATH in TextMate's Shell
I don't understand : setting "PATH" in the Shell Variables
I have kpsewhich here : /usr/local/texlive/2008/bin/universal-darwin/ kpsewhich
and my path is
Mundus:~ ego$ echo $PATH /usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/texbin:/usr/X11/bin:/ usr/local/git/bin
I need some help, please
Best Regards
Alain
Le 30 nov. 08 à 17:32, Alex Ross a écrit :
On Nov 30, 2008, at 5:31 PM, Alain Matthes wrote:
/usr/local/texlive/2008/bin/universal-darwin/
Add this to your PATH.
I can make this but it's not funny because /usr/texbin is a link to universal-darwin/
It's not possible to update something to avoid this ?
And if I want to use the Shell Variables in the prefs of TextMate, what is the syntax ?
Alain
On Nov 30, 2008, at 5:52 PM, Alain Matthes wrote:
Le 30 nov. 08 à 17:32, Alex Ross a écrit :
On Nov 30, 2008, at 5:31 PM, Alain Matthes wrote:
/usr/local/texlive/2008/bin/universal-darwin/
Add this to your PATH.
I can make this but it's not funny because /usr/texbin is a link to universal-darwin/
It's not possible to update something to avoid this ?
I have this link:
lrwxr-xr-x 1 root wheel 63 Sep 4 18:51 /usr/texbin -> ../Library/ TeX/Distributions/.DefaultTeX/Contents/Programs/i386
Maybe you can make /usr/texbin point to /usr/local/texlive/2008/bin/ universal-darwin/?
And if I want to use the Shell Variables in the prefs of TextMate, what is the syntax ?
There is no syntax for it. You simply open the preferences, go to the Advanced pane, and select the shell variables tab. Or did I miss your point?
—Alex
Le 30 nov. 08 à 18:05, Alex Ross a écrit :
It's not possible to update something to avoid this ?
I have this link:
lrwxr-xr-x 1 root wheel 63 Sep 4 18:51 /usr/texbin -> ../Library/ TeX/Distributions/.DefaultTeX/Contents/Programs/i386
But I have the same link
lrwxr-xr-x 1 root wheel 63 13 oct 23:18 texbin -> ../Library/ TeX/Distributions/.DefaultTeX/Contents/Programs/i386 and kpsewhich is here
Maybe you can make /usr/texbin point to /usr/local/texlive/2008/bin/ universal-darwin/?
No, MacTeX and the preference system work with this and I have no problem until 1.5.8
And if I want to use the Shell Variables in the prefs of TextMate, what is the syntax ?
There is no syntax for it. You simply open the preferences, go to the Advanced pane, and select the shell variables tab. Or did I miss your point?
variable = PATH ? and value = ???
Best Regards
Alain
On Nov 30, 2008, at 6:53 PM, Alain Matthes wrote:
And if I want to use the Shell Variables in the prefs of TextMate, what is the syntax ?
There is no syntax for it. You simply open the preferences, go to the Advanced pane, and select the shell variables tab. Or did I miss your point?
variable = PATH ? and value = ???
Have you updated to the recent cutting edge build of TextMate? If not, do that first.
After updating, open TextMate's preferences. Go to the Advanced pane, and select the Shell Variables tab. If you have other “PATH” variables set there already, remove them. Now, add a new variable by clicking the + sign.
Set the “Variable” part to “PATH”. Set the “Value” part to “/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/ bin:/usr/texbin:/usr/X11/bin:/usr/local/git/bin”.
Make sure that the box next to your new “PATH” variable is checked.
That should be enough to let the Typeset and View command find your tex installation.
—Alex
Silly question by a newbie: How do I update to the cutting edge build?
Alex Ross wrote:
On Nov 30, 2008, at 6:53 PM, Alain Matthes wrote:
And if I want to use the Shell Variables in the prefs of TextMate, what is the syntax ?
There is no syntax for it. You simply open the preferences, go to the Advanced pane, and select the shell variables tab. Or did I miss your point?
variable = PATH ? and value = ???
Have you updated to the recent cutting edge build of TextMate? If not, do that first.
After updating, open TextMate's preferences. Go to the Advanced pane, and select the Shell Variables tab. If you have other “PATH” variables set there already, remove them. Now, add a new variable by clicking the + sign.
Set the “Variable” part to “PATH”. Set the “Value” part to “/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/ bin:/usr/texbin:/usr/X11/bin:/usr/local/git/bin”.
Make sure that the box next to your new “PATH” variable is checked.
That should be enough to let the Typeset and View command find your tex installation.
—Alex
textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/listinfo/textmate
Le 30 nov. 08 à 19:09, Alex Ross a écrit :
Set the “Variable” part to “PATH”. Set the “Value” part to “/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/ bin:/usr/texbin:/usr/X11/bin:/usr/local/git/bin”.
ok now I can compile
Only the file " /etc/paths " is used and not the files in " /etc/ paths.d ".
is it a big problem to avoid this?
Best Regards
Alain
On Nov 30, 2008, at 8:11 PM, Alain Matthes wrote:
Le 30 nov. 08 à 19:09, Alex Ross a écrit :
Set the “Variable” part to “PATH”. Set the “Value” part to “/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/ bin:/usr/texbin:/usr/X11/bin:/usr/local/git/bin”.
ok now I can compile
Great!
Only the file " /etc/paths " is used and not the files in " /etc/ paths.d ".
is it a big problem to avoid this?
Hm, I'm not sure what you mean? If you set PATH as above (as it appears in Terminal), then you shouldn't have any problems.
—Alex
Le 30 nov. 08 à 21:19, Alex Ross a écrit :
Hm, I'm not sure what you mean? If you set PATH as above (as it appears in Terminal), then you shouldn't have any problems.
I don't like to use PATH in the Shell Variable manually
1) With 1.5.7, it was not necessary 2) What is the problem to get the path with a script ?
Alain
Le 30 nov. 08 à 21:19, Alex Ross a écrit :
On Nov 30, 2008, at 8:11 PM, Alain Matthes wrote:
Le 30 nov. 08 à 19:09, Alex Ross a écrit :
Set the “Variable” part to “PATH”. Set the “Value” part to “/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/ bin:/usr/texbin:/usr/X11/bin:/usr/local/git/bin”.
ok now I can compile
Great!
Only the file " /etc/paths " is used and not the files in " /etc/ paths.d ".
is it a big problem to avoid this?
Hm, I'm not sure what you mean?
I mean that textmate knows a part of the "path"
usr/bin:/bin:/usr/sbin:/sbin:/usr/local/ bin
this part is in the file /etc/paths but it's necessary to get the other part to read inside the folder /etc/paths.d the file "TEX"
Alain
On Nov 30, 2008, at 9:52 PM, Alain Matthes wrote:
Le 30 nov. 08 à 21:19, Alex Ross a écrit :
Hm, I'm not sure what you mean? If you set PATH as above (as it appears in Terminal), then you shouldn't have any problems.
I don't like to use PATH in the Shell Variable manually
- With 1.5.7, it was not necessary
- What is the problem to get the path with a script ?
There are several problems with sourcing the users shell profile. Often users have code that is not meant to be run, except when starting a new terminal. Other times, there are bugs in the user's profile that prevents commands from working. So, sourcing the profile is inadvisable.
I agree that it is inconvenient to maintain a PATH in the Shell Variables. In the future TextMate will have a better method to handle it. But we are stuck with the shell vars prefpane for now.
—Alex
Alex Ross <tm-alex@...> writes:
There are several problems with sourcing the users shell profile. Often users have code that is not meant to be run, except when starting a new terminal. Other times, there are bugs in the user's profile that prevents commands from working. So, sourcing the profile is inadvisable.
I agree that it is inconvenient to maintain a PATH in the Shell Variables. In the future TextMate will have a better method to handle it. But we are stuck with the shell vars prefpane for now.
—Alex
textmate mailing list textmate@... http://lists.macromates.com/listinfo/textmate
I'm confused because TextMate does in general source your ~/.bash_profile all general shell processing except, as I understand it, for direct invocations of interpreters (e.g. Ruby, etc.) via the #!/usr/bin/ruby interpreter call. I believe there is a generally accepted mechanism for separating login from non-login shell scripting for most of the common shell startup sequences. What is frustrating is that if you want to keep managing your path sane, you should keep it in as few places as possible. It seems like following the general TextMate approach to process your path via the same sequence that TM's bash_init.sh uses would be most consistent, if imperfect. I've taken to using the ~/.MacOSX/environment.plist mechanism which has it's own problems.
-eric
-
Achilleas Lazarides -
Alain Matthes -
Alex Ross -
Eric DeWitt -
Erich Neuwirth -
Guido Governatori