On Fri, Mar 9, 2018 at 8:02 AM, Ben Coman <btc@openinworld.com> wrote:
thx for looking into this.�� half way there ;)
do you have the Pharo build numbers that match these Nautilus versions?

I don't. PharoLauncher didn't work for me, when I try to launch an image I get an exception "MessageNotUnderstood: MacProcess>>waitForCommand:". So I just downloaded images from get.pharo.org and then used Monticello to identify the Nautilus packages versions and bisected in a 6.0 image until I found the version that introduced the bug. Do you need the build numbers? I suppose I can get the builds from
https://ci.inria.fr/pharo/ ?

cheers,
Siemen
��

cheers -ben

On 9 March 2018 at 14:30, Siemen Baader <siemenbaader@gmail.com> wrote:
The regression happens between Nautilus-TheIntegrator1352.mcz and Nautilus-TheIntegrator1351.mcz. Pharo 6.0 uses Nautilus-TheIntegrator1366.mcz

I'll look more to find the actual code that breaks.

-- Siemen




On Mon, Feb 12, 2018 at 6:57 PM, Siemen Baader <siemenbaader@gmail.com> wrote:
Hi Stef,

On Sat, Feb 10, 2018 at 6:22 PM, Stephane Ducasse <stepharo.self@gmail.com> wrote:
Hi Siemen

I use often cmd-L too and may be we got a regression.

I'm pretty sure I started doing it after I saw you do it in the MOOC ;)

And indeed I have the same behavior in Pharo 70.
Can you try to see how to address it?

Yes, I can try to look into it. I don't have any clear idea where to start other than browsing Nautilus code and perhaps uses of NautilusChanged, but perhaps it is not that hard to find.

-- Siemen

Stef

On Fri, Feb 9, 2018 at 8:37 PM, Siemen Baader <siemenbaader@gmail.com> wrote:
> Hi all,
>
> I downloaded Pharo 6.1 for OSX and whenever I revert changes in Nautilus
> with CMD-L, the content is reverted and the orange dirty marker triangle
> disappears. But when I switch to a different method, Nautilus shows the
> 'Content has been modified. What do you want to do?' dialog, as it only
> should when content is actually different.
>
> I use this all the time, I can't imagine I'm the only one, but I couldn't
> find the problem mentioned anywhere. Does anyone else have it? What to do?
>
> -- Siemen