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 <[email protected]>
To: "squeak-dev"<[email protected]>
Cc: "gettimothy"<[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 -- [email protected]
To unsubscribe send an email to [email protected]