Hi Dave,

On Fri, Jul 22, 2022 at 1:13 PM David T. Lewis <lewis at mail.msen.com> wrote:

> On Fri, Jul 22, 2022 at 08:06:19AM -0700, Eliot Miranda wrote:
> > Hi Dave,
> >
> > > On Jul 22, 2022, at 7:53 AM, David T. Lewis <lewis at mail.msen.com>
> wrote:
> > >
> > > ???On Fri, Jul 22, 2022 at 07:38:07AM -0700, Eliot Miranda wrote:
> > >>
> > >>
> > >>>> On Jul 22, 2022, at 3:13 AM, Marcel Taeumel <marcel.taeumel at hpi.de>
> wrote:
> > >>>
> > >>> ???
> > >>> Hi Eliot --
> > >>>
> > >>>> 1. the update fails with a merge conflict in the release builder
> between: [...]
> > >>>
> > >>> If you want to prepare a VMMaker Trunk image, you would use a
> regular Trunk image, not a release image. I think. So, why aren't you using
> a recent 6.1alpha image?
> > >>> -> http://files.squeak.org/6.1alpha/Squeak6.1alpha-22134-64bit/
> > >>>
> > >>
> > >> OK, I???ll try that.  Thanx!!
> > >>
> > >
> > > This will probably work with the 6.0 release image:
> > >
> > > ./Squeak.app/Contents/MacOS/Squeak trunk6-64.image
> UpdateSqueakTrunkImage.st --doit 'Project current addDeferredUIMessage:
> [PreferenceWizardMorph allInstances do: [:e | e delete]]'
> > >
> > > Or maybe just add "PreferenceWizardMorph allInstances do: [:e | e
> delete]." as the first line of the script.
> >
> > Given that there seems to be a drop event generated somewhere that may
> cause the script to be launched again later, is there a way of asking if
> the script is tuning in the context of DoItFirst?  Then the first line
> would be
> >
> >     self isRunningAsDoItFirst ifTrue: [^self].
> >     ???do stuff second time around when the system is headful???
> >
>
> It's best to do only very minimal things in any of the DoItFirst
> options. These run at the very earliest possible time in the startup
> list processing, so many things have not yet been initialized at that
> point. For doing anything non-trivial, you will want to use the normal
> start up script loader (as you already are doing for the VMMaker scripts).
>
I'm not trying to use DoItFirst.  I'm just trying to load scripts as used
to work.  Now, once I revert back to the old syntax of
    vmexe image.image script.st
scripts run, but every time a script is run a Note stating
    Cannot start a second instance of Squeak\with the image "{1}"\because
the VM is configured as singleton application.

Why is that happening?  It shouldn't, right?

The --doit option (and similar) is just a hook for running a snippet
> prior to startup processing, which is helpful if you have a broken
> image that you need to repair before it goes through the full startup
> list. Or you can use it to evaluate some expressions prior to running
> your actual script file.
>
> Dave
>

We need a page that specifies the startup semantics in the Squeak Help.

_,,,^..^,,,_
best, Eliot
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20220722/c7d58fd2/attachment-0001.html>