Re: osascript and *.command files
Re: osascript and *.command files
- Subject: Re: osascript and *.command files
- From: Doug McNutt <email@hidden>
- Date: Wed, 10 Oct 2007 08:30:52 -0600
This whole thread gives me deja vu.
The main reason for using Terminal.app as opposed to "do shell script" is the treatment of environment variables. Do shell script sees a couple like $HOME and any you have set up in $HOME/.MacOSX/environment.plist (spelling?). Terminal.app chooses the shell of your choice and sources it's .rc file in your home directory. If you don't watch out you'll find your $PATH as set up in environment.plist will get changed to /bin:/sbin:/usr/nin:/usr/sbin by an rc file in /etc. I have deleted that file for tcsh.
For some fun scripting Terminal.app have a look at:
<ftp://ftp.macnauchtan.com/Software/Progress/tViewInit>
<ftp://ftp.macnauchtan.com/Software/Progress/>
It deals with naming Terminal.app windows so you can direct blocks of textual commands to one of them. You have to check to see that Terminal.app does what it's told. Sometimes it silently ignores you when you're dealing with properties of a window.
--
--> Halloween == Oct 31 == Dec 25 == Christmas <--
_______________________________________________
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