Re: Are .st files just passed to the image? i.e. `start-image.sh --name ClaudeTweak --port 9877 --morphic --boot-script /tmp/bootscript_smoke.st` . How can I trap; this? thx in advance.

start-image.sh --name ClaudeTweak --port 9877 --morphic --boot-script /tmp/bootscript_smoke.st





i.e, I want to execute script on image starrt.



replace the "start-image.sh" with a generic ./bin/squeak   shared/ClaudfeTweak --boot-script /tmp/bootscript_smoke.st







we are currently debugging why the Morphic is not painting the world,. All my Workspaces are in the Morphic world, but they are not being rendered.   





This is part of the "unfreezing" of the Tweak import into 64 bits.



thank you for your time.



t




From: Thiede, Christoph via Squeak-dev <[email protected]>
To: "The general-purpose Squeak developers list"<[email protected]>
Cc: "gettimothy"<[email protected]>, "Thiede,  Christoph"<[email protected]>
Date: Wed, 22 Jul 2026 22:19:37 -0400
Subject: [squeak-dev] Re: Are .st files just passed to the image? i.e. `start-image.sh --name ClaudeTweak --port 9877 --morphic --boot-script /tmp/bootscript_smoke.st` . How can I trap; this? thx in advance.



What exactly isn't working for you? Arguments before the image name go to the VM (e.g., -headless) and arguments after the image name go to the image. --doit et al. are processed by DoItFirst in the image. A script file is filed in by another class (ProjectLauncher
 iirc). You can handle further arguments either in the class-side startUp: logic of your own class or by injecting your handler using one of the prior ways.



Best, 

Christoph










From: gettimothy via Squeak-dev < mailto:[email protected] >
 Sent: Sunday, 19 July 2026 18:22:18
 To: squeak-dev < mailto:[email protected] >
 Cc: gettimothy < mailto:[email protected] >
 Subject: [squeak-dev] Re: Are .st files just passed to the image? i.e. `start-image.sh --name ClaudeTweak --port 9877 --morphic --boot-script /tmp/bootscript_smoke.st` . How can I trap; this? thx in advance. 
 


DoItFirst is, apparently the class I was looking for...









  

./bin/squeak shared/ClaudeTweak.image -headless  -- --filein /tmp/bootscript_smoke.st



is what I am trying to accomplish...however, the simple <options> '-test' is  failing unless I have the syntax wrong...for example...





./bin/squeak -title test  shared/Croquet64SDKHack.image

 ./bin/squeak -title 'test'  shared/Croquet64SDKHack.image

 ./bin/squeak -title "test"  shared/Croquet64SDKHack.image





drops right into the squeak -help output.



thank you in advance









From: gettimothy via Squeak-dev < mailto:[email protected] >
 To: "squeak-dev"< mailto:[email protected] >
 Cc: "gettimothy"< mailto:[email protected] >
 Date: Sat, 18 Jul 2026 14:36:08 -0400
 Subject: [squeak-dev] Are .st files just passed to the image? i.e. `start-image.sh --name ClaudeTweak --port 9877 --morphic --boot-script /tmp/bootscript_smoke.st` . How can I trap; this? thx in advance.



Hi folks



The working theory is that the --boot-script arguments are passed to the image w/o VM influence at all.





The open question is what handles the *.st script on image launch...





On a 64-bit Squeak 6.1 Cog VM, passing a trailing script argument after the image name (per  --help's 'first argument normally names a Squeak script') results in  Smalltalk getSystemAttribute: 2 correctly returning the path, but nothing in the image appears to file it in automatically



cordially








Squeak-dev mailing list -- mailto:[email protected]  

 To unsubscribe send an email to mailto:[email protected] 










Squeak-dev mailing list -- mailto:[email protected]  

To unsubscribe send an email to mailto:[email protected]

Squeak-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]