yes as always you are correct I lost the names of all my temporary variables but I got that fixed by reimporting the filetree repository.

Thank you for your efforts they never go unnoticed.

By the way this is a fresh image that does this, I use a startup script to load all my libraries. Maybe one of those libs does something funky to the changes file. Epicea looks interesting.

��The one thing that makes me wonder is how needed the image file format really is. I get it that is there to store the complete live enviroment but even in that case it can still be broken to individual files each with a specific role, some binary and some text. Afterall there is no reason why state cannot be stored even in text files. In any case I know you guys have many good ideas to improve the situation and I am sure with time you will.

On Fri, Nov 27, 2015 at 7:37 PM Marcus Denker <marcus.denker@inria.fr> wrote:

> On 27 Nov 2015, at 13:32, Dimitris Chloupis <kilon.alios@gmail.com> wrote:
>
> Marcus you are awesome thank, so all I had to do was erase my Ephestos.changes file and now I can browse addMiscExtraTo: and I have no MNUs or red boxes of doom.
>
> There was something fishy about my changes file, I found addMiscExtraTo: in PharoV4.sources and in Ephestos.changes, the issue is that I never touched that method , so why should it be in changes file ? I thought changes are for the things you change in the image.
>
> But no complains , it looks like now the problem is gone.
>

The .changes does not only have the changes that you did, but in addition all changes that we did to Pharo since the release of Pharo4���

The whole mechanism is not very good��� we really should replace it. The good news is that we are working on the first step
��already: Epicea will be used for recording changes, so after that we re free to simplify source storage as it will now overlap anymore
with change history recording.

Be careful with an image where you delete the .changes: all methods that point to that file will be decompiled��� losing comments and much more.

The best thing is to re-create an image from the release (loading your code).

�� �� �� �� Marcus