Hi david
On 16 Jan 2016, at 02:42, Ben Coman <[email protected]> wrote:
So if occasionally if everything seems against you, after trying a
fresh Image as you already did, slide back to the last build that
worked for you (I don't think the issues you experience are Spur
related, but 50496 might be a good fallback as Pre-Spur and
Pre-GTDebugger). Then create a fresh Image from the latest build to
test your Slice and in that time maybe the other issues have gone.
Ok. So my earlier question (in Slack, I think) about how "unstable" is unstable in Pharo
is now answered. It's really unstable, not "Debian-like unstable".
No this is not really the case. In general we try hard to get alpha
stable after you get some hiccups.
This is not every day that we change FFI, GC, object internal
representations and the text editors, syntax highli
And our problems is that sometimes often we just jump over glitches
(this is why I'm getting mad because when I do videos
or other I see them in my face). Now I would love to have task forces
that check glitches.
It would also be nice to add some public info about that. I'll create an issue.
At the moment, I am stuck with GTDebugger, because it seems the old debugger
does not have any keyboard shortcut form stepping through code. And that's
something I would really really miss. So I'll suffer the pain of all the other
glitches, and see how that goes.
