> Downloaded it. Installed it. Started it. Selected an image. Bam. The
As I've mentioned in several other threads, the way new images are opened
(the lib that executes the command) seems to be very unreliable and
sometimes opening image just doesn't work, and I have to open PL again and
My guess is that there's a race condition and PL closes faster, and before
the subprocess manages to be disowned.
On Mon, Apr 16, 2018 at 3:39 AM, Ben Coman <b...@openinworld.com> wrote:
> On 16 April 2018 at 06:02, Benoit St-Jean <bstj...@yahoo.com> wrote:
> > "What path did you install to?"
> > The installer put it in:
> > C:\Users\Benoît St-Jean\AppData\Local\Programs\Pharo\BCPharoLauncher>
> To work around the special character in your path, try copying that
> whole folder to C:\BCPharoLauncher
> and directly double-click Pharo.exe. Then click the Settings tool
> icon and change the Image & VM paths.
> Hopefully that will get you going for now, until we sort out a proper fix.
> cheers -ben