Re: Fink and 'sh'
Re: Fink and 'sh'
- Subject: Re: Fink and 'sh'
- From: Walter Ian Kaye <email@hidden>
- Date: Mon, 22 Mar 2004 14:53:06 -0800
At 10:50p +0100 03/22/2004, Brennan didst inscribe upon an electronic papyrus:
On 22/3/04 at 16:17, Graff <email@hidden> wrote:
> Of course, as someone already said, this solution depends on the
> "where" command being able to find the "lame" command. The problem is
> that the "where" command looks at your PATH, which is not set properly
> in the first place. This means that it won't find "lame" so it is kind
> of circular in this case. I didn't think of this when I first posted
> my answer.
Hmm. I don't really understand this. What do you mean when you say that
PATH is not set properly? I understand that PATH is an environment
variable, presumably a list of places where to look for commands. However,
do shell script "/bin/tcsh -c 'where lame"
*does* return the path to LAME. It does the right thing already. Do I
still have to worry about PATH?
As I mentioned earlier, `which` and `where` rely on PATH. That is why
they are orders of magnitude faster than the `find` command. ;)
Although... I first installed LAME with the package from
<http://www.culater.net> but afterwards the Terminal didn't know it by
name. Only after I installed it with Fink, was I able to run it from the
terminal by name only. Is that relevant?
Yes. See above.
-boo
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.