This also happened to me several times when executing (do it and go) some Roassal example with error (=it opened debugger). However the occurrence is very inconsistent so I don't know what was the trigger.
Peter On Mon, Apr 20, 2015 at 1:29 PM, Yuriy Tymchuk <[email protected]> wrote: > This was just an example. The question is how do I identify what is > blocking the highlighting. > > Uko > > > On 20 Apr 2015, at 12:19, Denis Kudriashov <[email protected]> wrote: > > Hi > > Maybe highlighting is running in process with lesser priority than default > priority of #fork method. > > Code like "[ [ true ] whileTrue: [ ] ] fork" will block any processes > with lesser priority > > > 2015-04-20 12:51 GMT+03:00 Yuriy Tymchuk <[email protected]>: > >> Open a new pharo image (I’ve used latest 5, but on 4 it should work as >> well). Open playground and execute: >> >> [ [ true ] whileTrue: [ ] ] fork >> >> now open a new playground and start typing. Characters are invisible. >> Uko >> >> On 20 Apr 2015, at 11:14, Tudor Girba <[email protected]> wrote: >> >> Hi, >> >> I did not see this before. Could you reproduce the issue? >> >> Cheers, >> Doru >> >> >> On Mon, Apr 20, 2015 at 11:03 AM, Yuriy Tymchuk <[email protected]> >> wrote: >> >>> Hi. >>> >>> Sometimes it happens that playground does not do the syntax >>> highlighting. This is especially frustrating when you open a new window and >>> text is either white or transparent i.e. you cannot see what you are typing. >>> >>> I guess this is because some process is blocked by another one. Is there >>> a way to check it? Because I want to understand whether it is because of >>> me, or not. >>> >>> Cheers! >>> Uko >>> >> >> >> >> -- >> www.tudorgirba.com >> >> "Every thing has its own flow" >> >> >> > >
