Thanks for your reply. It looks like Terminal is always executing a
command called "/tmp/CodeWarriorJava.command". Here is the output I see
when opening a new shell:
When I rerun my app in CW, the CodeWarriorJava.command file is
automatically recreated. At least I know now what command is being
executed when I start a shell--I just don't know how to tell terminal
not to use that command.
oz
On Mar 30, 2005, at 9:34 PM, Dmitry Markman wrote:
???
I'm using CW and Terminals in the same time
for years (from mac os x beta)
and never saw any problem
I can open as many terminals windows as I want
before or after CodeWarrior started my java application
in fact I'm doing that every day many many times
so you have to provide more information I guess
On Mar 31, 2005, at 12:07 AM, John Osborne wrote:
This is a question for any CodeWarrior users out there. When I launch
my application from CW, the Terminal app starts a new shell with the
specific Java command needed to launch app. However, I can't seem to
open a new Terminal window without launching my app. Any and all new
shells execute this java command--it's like Terminal is hardwired to
this one command. I can't seem to find anyway in Terminal or CW to
turn this behavior off. To get to a command line I have background my
Java app and then quit it. Any suggestions from the CW crowd(?) would
be appreciated.
John Osborne (oz)
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
Dmitry Markman
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
