Re: New window in Terminal.app
Re: New window in Terminal.app
- Subject: Re: New window in Terminal.app
- From: Doug McNutt <email@hidden>
- Date: Sun, 30 Jan 2005 14:18:14 -0700
At 12:12 -0800 1/30/05, Andrew Oliver 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.
(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.
(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.
>This solution still falls foul of Terminal.app's brain-dead window targeting.
I am working on some targeting that works. Some earlier posts about using title rather than name show real promise. By creating a new Terminal window and immediately giving the front window a (custom) title it appears that you can refer to the window "by name" while really using the title that you give to it. The dictionary doesn't say that though it does confuse the words "name" and "title". I'll report in a few days.
Programming by experiment when RTFM fails. . . sigh
--
Applescript syntax is like English spelling:
Roughly, but not thoroughly, thought through.
_______________________________________________
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