At 22:22 +0100 10/2/11, Phil Dobbin wrote: >On 2/10/11 at 22:06, [email protected] (Doug McNutt) wrote: > >>At 15:13 +0100 10/2/11, Phil Dobbin wrote: >>>I got it working on the command line by cd'ing to the directory it was >>>located in & giving it an absolute path using ~/ >> >>AppleScript is well known for not running startup scripts for shells. Your >>$PATH variable may not be what you think.. >> >>That tilde I see at the end of your line above scares me. >> >>Is your script perhaps in $HOME/bin/ ? AppleScript won't find it without a >>full path and it might not understand the tilde either. You can't set a >>working directory in AppleScript unless you do it for each do shell script >>call. BBEdit worksheets are a bit better but you still can't set a directory >>in one worksheet and discover it in another. > >Hi, Doug. > >It's a shell script rather than an Applescript & the tilde ~/ is pointing to >the directory that the script resides in (in this case: ~/scripts).
What I was thinking is that running the shell script from within bbedit might be done by the Bare Bones folks using procedures that come through AppleScript.. Somewhere I got the idea that your script runs fine from a Terminal.app session but gets in trouble when you start from within bbedit. Have you tried running it from within a bbedit worksheet? -- --> There are 10 kinds of people: those who understand binary, and those who don't <-- -- You received this message because you are subscribed to the "BBEdit Talk" discussion group on Google Groups. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at <http://groups.google.com/group/bbedit?hl=en> If you have a feature request or would like to report a problem, please email "[email protected]" rather than posting to the group. Follow @bbedit on Twitter: <http://www.twitter.com/bbedit>
