Re: Automator-users Digest, Vol 71, Issue 11
Re: Automator-users Digest, Vol 71, Issue 11
- Subject: Re: Automator-users Digest, Vol 71, Issue 11
- From: James C <email@hidden>
- Date: Fri, 23 Dec 2011 13:58:50 +1300
Peter,
Thank you; I like this plan. It is not brittle to selecting one thing
and then opening another.
In my cut-down growl test version, it became two automator steps:
======== applescript =========
on run {input, parameters}
set myPath to path to me
return myPath
end run
======== shell script =========
for f in "$@"
do
/usr/local/bin/growlnotify -m "$f"
done
==========================
The remaining fault is that, while editing in Automator.app, it
returns the path to Automator.app, which would make discovering that
it is useful difficult. I will complain about this part to Apple.
Regards,
James.
On Fri, Dec 23, 2011 at 9:01 AM,
<email@hidden> wrote:
> Date: Thu, 22 Dec 2011 15:38:06 +0900
> From: Peter Mears <email@hidden>
> Subject: RE: In an automator shell script, discovering the path to the
> > application
> To: email@hidden
> Message-ID:
> <email@hidden>
> Content-Type: text/plain; charset="iso-8859-1"
>
> James,
> I am not sure if this will completely solve your quest.
> I have an apple script that will detect the folder it is being run from
> then pass that path to terminal.app and run a script from a known location.
>
> set myPath to path to me
> tell application "Finder"
> set myFolder to (container of myPath) as alias
> set p to myFolder's POSIX path's quoted form
> end tell
>
> tell application "Terminal"
> activate
> set currentTab to do script with command "cd " & p
> do script "sh ~/location/yourscript.sh" in currentTab
> end tell
>
> Hope this helps in some way.
>
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Automator-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden