Hi,
I'm setting up my environment on Tiger from scratch and TM is giving me lip with the "Pipe text through" in the Web Preview. Markdown.pl lives in:
~/usr/local/bin/Markdown.pl
which i what I've placed in the Pipe through field. Permissions on the script are correct: chmod +x /usr/local/bin/markdown.pl
TM tells me: "/bin/bash: line 1: /Users/tim/usr/local/bin/ Markdown.pl: No such file or directory"
by .bash_profile has: export PATH=$PATH:/usr/local/bin:/usr/local/ php5/bin:/usr/sbin
in it. Any ideas. I probably missing something really basic.
Thanks,
-t
On May 20, 2005, at 3:45, Tim Martens wrote:
~/usr/local/bin/Markdown.pl
The “~” is shorthand for your home directory. So it does not live in the above path.
by .bash_profile has: export PATH=$PATH:/usr/local/bin:/usr/local/ php5/bin:/usr/sbin
In that case, you should be able to just use “Markdown.pl” w/o the path. Otherwise use: /usr/local/bin/Markdown.pl, i.e. without the tilde.
On May 19, 2005, at 4:30 PM, Allan Odgaard wrote:
The “~” is shorthand for your home directory. So it does not live in the above path.
I knew that. But I missed it. Thank you Allan
by .bash_profile has: export PATH=$PATH:/usr/local/bin:/usr/local/ php5/bin:/usr/sbin
In that case, you should be able to just use “Markdown.pl” w/o the path. Otherwise use: /usr/local/bin/Markdown.pl, i.e. without the tilde.
Strangely neither: Markdown.pl nor "Markdown.pl" even with the profile above. Any ideas why?
On May 20, 2005, at 22:58, Tim Martens wrote:
In that case, you should be able to just use “Markdown.pl” w/o the path. Otherwise use: /usr/local/bin/Markdown.pl, i.e. without the tilde.
Strangely neither: Markdown.pl nor "Markdown.pl" even with the profile above. Any ideas why?
Which version of TM are you using?
1.1b5 or earlier requires that you setup two custom shell variables for bash to function properly. BASH_ENV and SHLVL, the former should be set to the script you wish to source (e.g. ~/.bash_profile), the latter just to 1 (you can search the list archives for more info).
To check the state of your variables (including PATH) then open a new document, type “env”, and press control-R, that dumps all the variables normally available to a command executed by TM. So you can check what PATH is really set to (and if the two variables mentioned are setup properly).
Starting with 1.1b6 TM should take care of all this itself, and (unless there's a user override) it sets BASH_ENV to an init script which does:
[ -f /etc/profile ] && . /etc/profile
if [ -f ~/.bash_profile ]; then . ~/.bash_profile elif [ -f ~/.bash_login ]; then . ~/.bash_login elif [ -f ~/.profile ]; then . ~/.profile fi
-
Allan Odgaard -
Tim Martens