I checked both of those before I sent the email. I also checked all the files referenced in the bash man page.
I ran bash with ktrace and noticed that it is reading the /Applic...Explorer.command command from stdin before it is executing it. Here is some more information: when I start the terminal with File->NewCommand and check "Run command inside shell": ------------------ in .bash_profile mikepb:~ pottmi$ bash; exit # [EMAIL PROTECTED] $ ------------------- when I start the terminal with File->NewCommand and do NOT check "Run command inside shell" -------------------- in .bash_profile mikepb:~ pottmi$ /Applications/OpenLaszlo\ Server\ 3.3.3/OpenLaszlo\ Explorer.command; exit Explorer.command ^C logout [Process exited - exit code 130] ----------------------- In both cases the command I am running is bash. I put a sleep 30 in Explorer.command so I could have time to hit control-C before it actually did anything. -- Michael Potter On 2/26/07, P T Withington <[EMAIL PROTECTED]> wrote:
This is not the default behavior. I would check my Terminal/Preferences (which has settings for what to do when you start a Terminal), and your ~/.bashrc, which is executed when you create a new shell. On 2007-02-25, at 10:39 EST, Michael Potter wrote: > I use Mac OS X Tiger and recently installed > openlaszlo-3.3.3-osx-dev.install.dmg. > > Now whenever I open a new Terminal window (File->New Shell) this > command runs: > /Applications/OpenLaszlo\ Server\ 3.3.3/OpenLaszlo\ Explorer.command > > My problem is that I use Terminal for other things so I do not want > Explorer.command to always start. > > I can not figure out why this runs, I even went so far as running > ktraceon Terminal to find out where it reads that command from. I > checked every preference option in Terminal and can not find a > reference to that command. I do not have any files in > Library/Application Support/Terminal. > > As a work around I now I run File->NewCommand and use bash as the > command. At least I can get a usable terminal window. > > Here are my questions: > 1) How do I disable that behavior. > 2) Once disabled how do I start Explorer.command: > my guess is File->NewCommand /Applications/.../Explorer.command > > Thanks for your help in advance, Laszlo seems to be exactly what I am > looking for. > > -- > Michael Potter
