On 2/27/07, P T Withington <[EMAIL PROTECTED]> wrote:
Googling for 'OS X Terminal ExecutionString' reveals that this issue
is not limited to Laszlo.
Apparently if you start the Terminal by asking it to execute a script
and then in that Terminal happen to select 'File/Use Settings As
Default' or File/Window Settings/Use Settings As Default, it will
save the script as the 'ExecutionString' property, and in the future,
run that script every time the Terminal is launched. This seems like
an OS X mis-feature, since this ExecutionString property does not
seem to show up in any of the preference panes for the Terminal.
I don't recall doing any of that. The reason I remember that is I
seldom change anything with Terminal preferences or settings. I
certainly don't recall selecting anything labeled: "Use Settings As
Default".
I am not asking you to do anything more, you have been quite helpful.
I think the next step would be for me to reproduce the problem by
uninstalling laszlo and reinstalling to see if the problem can be
recreated. I don't doubt that it is something I did, I just doubt
that I did it by selecting "Use Settings as Default".
The solution is to either delete your Terminal preferences
altogether, or use a preferences editor to set the Execution String
property to empty.
FYI: I deleted the Execution String property (not just setting it to
empty). That worked but do you think it will cause a different
problem?
On 2007-02-26, at 22:31 EST, Michael Potter wrote:
> I used the prefsetter application downloaded from version tracker to
> delete the ExecutionString parm from com.apple.Terminal.plist. That
> fixed the problem.
>
> I sent my entire com.apple.Terminal.plist file to P.T. so he could
> take a stab as to why the installation of laszlo modified the Terminal
> plist.
>
> Thanks for the help.
>
> P.T., if you need me to uninstall laszlo and reinstall it to track
> down the problem I would be happy to do that. I will need
> instructions for uninstalling tho. Normally I just move the
> application from Applications folder to Trash, but I think the laszlo
> installation is more elaborate than that.
>
> --
> Michael Potter
>
> On 2/26/07, Michael Potter <[EMAIL PROTECTED]> wrote:
>> Here is a link to someone else who had the same problem:
>> http://forums.osxfaq.com/viewtopic.php?
>> t=14114&sid=b52226c322595e5a5cfda3fa208aa9ad
>>
>> I will try your suggestions tonight and report back what I find.
>> The resolution to the problem above was similar to what you are
>> suggesting so I suspect your suggestion will work.
>>
>> Thanks,
>> --
>> Michael Potter
>>
>> On 2/26/07, P T Withington <[EMAIL PROTECTED]> wrote:
>> > Totally strange. I have never seen this.
>> >
>> > The only other places I can think to look are ~/.MacOSX/
>> > environment.plist, ~/Library/Preferences/com.apple.Terminal.plist,
>> > and ~/Library/Application\ Support/Terminal.
>> >
>> > You could try deleting your terminal prefs file (with the terminal
>> > not running), and see if that clears things up.
>> >
>> > On 2007-02-26, at 11:37 EST, Michael Potter wrote:
>> >
>> > > 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
>> > >>
>> > >>
>> >
>> >
>>
