On 09 Oct 2015, at 15:42, Andrei Chis <chisvasileandrei@gmail.com> wrote:

This error happens now in Moose every time something is printed to the transcript.
Seems that rubric has diverged a bit in Pharo

Du to problems with changes that where crosscutting some changes where done that need to

be re=synced back to the repository�� someone needs to do that. There is even an issue tracker entry

for that.

On Fri, Oct 9, 2015 at 8:16 AM, Alain Plantec via Pharo-users <pharo-users@lists.pharo.org> wrote:

---------- Forwarded message ----------
From: Alain Plantec <alain.plantec@yahoo.com>
To: Any question about pharo is welcome <pharo-users@lists.pharo.org>
Cc:
Date: Fri, 9 Oct 2015 08:16:00 +0200
Subject: Re: [Pharo-users] MNU: RubPluggableTextMorph>>appendEntry
Hello,
I��ve just tested.
It seems to works well with the last version of Pharo 5
Cheers
Alain

> On 08 Oct 2015, at 22:40, Alexandre Bergel <alexandre.bergel@me.com> wrote:
>
> Hi!
>
> A new Pharo user bumps into a nasty bug. No idea why it appears time to time.
> The method ThreadSafeTranscript>>stepGlobal does a "self changed: #appendEntry.�� This apparently update by RubPluggableTextMorph by calling "RubPluggableTextMorph >>update: #appendEntry��. All this ultimately sends #appendEntry to RubPluggableTextMorph, which is not understood.
>
> What is the solution for this?
>
> https://pharo.fogbugz.com/f/cases/16749/MNU-RubPluggableTextMorph-appendEntry
>
> Alexandre
>
>
> --
> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
> Alexandre Bergel http://www.bergel.eu
> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
>
>
>
>