Re: Do shell script vs terminal discrepancy
Re: Do shell script vs terminal discrepancy
- Subject: Re: Do shell script vs terminal discrepancy
- From: Paul Skinner <email@hidden>
- Date: Fri, 04 Dec 2009 16:23:59 -0500
You're on the right path <rimshot> airdrummer. This is an issue with
the fact that do shell script ignores the configuration files that an
interactive shell would read. So there's no $PATH extending, so no non-
default path installed tools are available.
Even if I call the tool with a full path this will always fail
because it won't have access to the dependencies that imagemagik
requires. It's not possible unless I could build IM in a default path
for sh shell.
Oh well, it's not like I could distribute this script with an IM
dependency anyway. I spent 3 hours installing and updating macports,
rubygems and IM just to get this to run properly in the terminal. And
I certainly wouldn't think of futzing around with the install paths. I
wonder if it is possible to somehow get the default sh shell paths to
see the tools using symlinks and such. No, I'd probably just shoot
myself in the foot with the terminal.
Back to square one.
Hey, does anyone know how to resize and image in the shell using Core
Image and get the channel values of each pixel?
Thanks,
Paul
On Dec 4, 2009, at 3:54 PM, airdrummer wrote:
the other thing to check is your path to convert: the a/s
environment may be different from the terminal's. what does
do shell script 'which convert'
return, and is it the same in terminal?
_______________________________________________
Do not post admin requests to the list. They will be ignored.
AppleScript-Users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
Archives: http://lists.apple.com/archives/applescript-users
This email sent to email@hidden