I have been doing like this: #!/bin/bash ./pharo Pharo.image save Builder ./pharo Builder.image LoadBuilder.st --quit
and LoadBuilder.st contains <code to load configurations and other thing> Smalltalk saveSession. Worked for me in a 3.0, so should still be fine. I could then to a set of images with various names and builders so one could have all the prerequisites and the last step just loaded my code fast on my CI. Phil On Mon, Nov 28, 2016 at 1:23 PM, Sven Van Caekenberghe <s...@stfx.eu> wrote: > Hi Dimitris, > > According to > > STCommandLineHandler>>#end > | quit | > > quit := self commandLine hasOption: 'quit'. > > (self commandLine hasOption: 'save') > ifTrue: [ Smalltalk snapshot: true andQuit: quit ]. > > quit > ifTrue: [ self exitSuccess ]. > > You should be able to combine --quit and --save to get the desired effect > but I haven't tested it. > > BTW, command line usage of Pharo works very well (and has been working > well for years). > > Sven > > > On 28 Nov 2016, at 12:13, Dimitris Chloupis <kilon.al...@gmail.com> > wrote: > > > > How to execute a script from command line , then save the image and exit > ? > > > > I use the st command but it offers either --save which saves but keeps > image opened or --exit the exits the image without saving > > > > ./pharo Ephestos.image st --save test.st > > > >
