"BTW, Nautilus is stable and used daily by the whole community."

This still rankles ... I have been a Smalltalker since long before Squeak and have been using Pharo since Seaside first ran on it - if not earlier than that ...

I also received from another on the mail list

"and in fact I cannot reproduce it."

"And in fact" is such a wicked rhetorical move ... in a game I have lost all interest in playing now that I am retired.

It may take me a lot of effort to track these 2 bugs down as far as "Follow these steps to reproduce" .. but then I am not a CONSORTIUM member ( I used to pay big bucks for Smalltalk, back in the day ) so may be I am too far outside the "whole community".... btw.

I will spare you my plot's view of the term "stable" and the notion of stability ... and will be sure I rename key files as I go along ... [ why are we still having to rename files such as these when able to run multiple images in the same dir ? ]

ciao

On 26 February 2014 04:36, Sven Van Caekenberghe <sven@stfx.eu> wrote:

On 26 Feb 2014, at 01:57, Robert Shiplett <grshiplett@gmail.com> wrote:

> I am running from that latest.zip tonight and PackageTreeNautilusUI >>update is getting a walkback messageNoUnderstood for
> receiver of >>protocolsFor: is nil
>
> I simply flipped to class view in Announcements and then flipped that toggle back.
>
> Does this need to be reported, or is Nautilus still known to be unstable ?

I can't reproduce this either, please be more specific.

BTW, Nautilus is stable and used daily by the whole community. Of course, it is a complex piece of code with lots of UI and system interactions, so issues are always possible.

Sven