On Sat, Jan 16, 2016 at 6:57 AM, David Allouche <david@allouche.net> wrote:
On 15 Jan 2016, at 23:49, Nicolai Hess <nicolaihess@gmail.com> wrote:
2016-01-15 23:33 GMT+01:00 David Allouche <david@allouche.net>:
So yes, it's broken, but maybe it's something else entirely, I get new reproducible errors every few minutes: errors when activating pretty printing in the diff viewer in Monticello,
this is a known error from the "recent" change for rubric text component
unexpected contextual menu showing up when I do Cmd-T in the debugger,
known ( from the recent changes for debugger :) )
infinite recursions when trying to debug through the MonticelloRepositoryBrowser...
I don't know this error. But I don't think "this" MonticelloRepositoryBrowser is actually used.
I think that was actually a bug in the debugger, or inspector, not in MonticelloRepositoryBrowser.
And yes, this appear to be dead code. I found it before finding the actual browser, and thought it might be a good place to start exploring Monticello.
I tried the old debugger in my new latest image (in the hope that syntax highlighting would not be broken there), but I realised it advertised no keyboard shortcut for stepping through the codeâ¦
Starting to wonder if I should go back to spending my evenings playing Elite Dangerous, and come back in a few weeks when stuff is hopefully less buggy everywhere :-(
Generally I'm impressed at Pharo's stability given depth of the surgery that is sometimes done on it - but after all it is bleeding edge and sometimes things get in a bind. Since all the tools are built and run inside the Image, sometimes its a bit like changing the tyres on a moving car - but there is the advantage that we are *always* eating our own dogfood. 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. cheers -ben