Re: New window in Terminal.app
Re: New window in Terminal.app
- Subject: Re: New window in Terminal.app
- From: Andrew Oliver <email@hidden>
- Date: Sun, 30 Jan 2005 13:39:21 -0800
On 1/30/05 1:18 PM, "Doug McNutt" <email@hidden> wrote:
>> I'm sure I missed the discussion of why you need to use terminal.app at all,
>> rather than the much more reliable 'do shell script', but anyway...
>
> (1) Terminal has a memory so after you cd or something like that in a window -
> er shell - you can expect things to remain the way you left them.
IF you can find the right shell/window again ;)
>
> (2) A new terminal window will use your user-defined default shell and, in my
> case, execute $HOME/.tcshrc setting up $PATH and other things.
Ahh, so you're not worried about portability then, fair enough. However, I
would expect:
do shell script "source $HOME/.tcshrc; blah"
to maintain your environment if you wanted/needed it in the shell script.
>
> (3) Terminal can display status for a long job, Curl, for instance, sends
> status to stderr and uses returns as opposed to newlines. The result is that
> the lines overlay each other in Terminal but produce copious text, where you
> don't want it, in a BBEdit worksheet.
Fair enough. I have to admit I'm no fan of Apple's suggestion to redirect to
a file and read the file in your script. It works, it just 'feels dirty'. A
synch/asynch option would be nice.
Andrew
:)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Applescript-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden