How about fixing windows VM? Ugly but should work :)
On 15 November 2012 12:45, Bruni camillo <[email protected]> wrote: > How about forking directly at the beginning, then busy wait in bash for a > certain file to be created at the end of the st script and only then > continue. > > Ugly but should work > > On 15 Nov 2012 16:06, "Tudor Girba" <[email protected]> wrote: >> >> Hi, >> >> Actually, the reason why I cannot use this solution is that on Windows, >> when I have a large enough image, I can build it, I can save it even, but I >> cannot reopen it. Hence my only way around it is to not close it :). >> >> Cheers, >> Doru >> >> >> On 15 Nov 2012, at 14:23, Camillo Bruni <[email protected]> wrote: >> >> > >> > On 2012-11-14, at 11:07, Tudor Girba <[email protected]> wrote: >> > >> >> Hi, >> >> >> >> I have the following requirement: >> >> - I start an image from the command line with an initial script >> >> - I want to wait until the Smalltalk script finishes until I can >> >> continue >> >> with the command line script >> >> - But, I do not want to stop the image >> >> >> >> I can achieve the first two points by having the image quit at the end. >> >> Is >> >> there a way in which I can somehow continue the command line execution >> >> without stopping the image? >> > >> > I don't know the details but if you save+quit your image and immediately >> > open >> > it again it will continue where you where before. so the following is >> > the >> > closest thing I can come up with >> > >> > ./vm.sh Pharo.image st doStuffAndSave.st; >> > ./vm.sh Pharo.image & # relaunch and fork to background >> > ./doStuffAfter.sh >> > >> > but yeah, that violates your not-image-stop requirement :) >> > >> >> -- >> www.tudorgirba.com >> >> "Being happy is a matter of choice." >> >> >> >> > -- Best regards, Igor Stasenko.
