Hi,
I have a broken 6.1 image and uncommited code with non-ascii characters in
it. When I drag the .changes file onto a new 6.1 image it won't import due
to the non-ascii code, but I can rename the .changes file so it matches the
new image's filename and import individual code changes (also with
Hi,
I have had a few occasions where I broke an image because I either ran out
of disk space or had an endless loop that grew my image endlessly (I think).
But why does Pharo not save the image & .changes file in hidden files named
eg ~Pharo.image while it saves? Then it can rename them when
I gave up working on this issue back in September because I had other things
to do, but never resolved it — unless you call screen-sharing to another
machine that does continue to run Pharo a "solution"
As far as I can see, the problem is that my Pharo VM can't find the
primitives that allow it
Hi Tim,
If you get to it before me I'd be happy if you would like to share the actual
code you use to log in and / or which tutorial you used.
Siemen
Sent from my iPhone
> On 9 Nov 2019, at 17.16, Tim Mackinnon wrote:
>
>
> Interestingly I came across a need to investigate oauth and its
> On 15 Nov 2019, at 18:10, AndrewBlack wrote:
>
>> $ open Pharo.image
>
> Pharo runs, and so does Iceberg, but the image that it's running is my
> broken Pharo launcher image, not the new one that was just downloaded, and
> the VM running it is a 32-bit VM, because MacOS warns me that it is
