On 2007-02-27, at 10:35 EST, Michael Potter wrote:
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".
If you want to try to investigate further, that would be great. I
don't have time in the next few days to do so.
Here's what I did:
I launched Laszlo using the OpenLaszlo Explorer shortcut. This opens
a Terminal session, but also starts Safari. I confirmed that if I
went to the Terminal window and used the Save Settings as Default
feature, it indeed wrote to the preferences, and from then on,
launching Terminal always tried to run the OpenLaszlo Explorer
command file. Editing the prefs with the Property List Editor
allowed me to get my Terminal back.
