Re: [Pharo-dev] The new implementation of current working directory

Hi Rajula, On Sun, Jul 09, 2017 at 10:38:42PM -0700, Rajula Vineet wrote: > Hi Alistair, > > --- > > From: Alistair Grant [via Smalltalk] > Sent: Monday, July 3, 2017 7:29 PM > To: Rajula

Re: [Pharo-dev] The new implementation of current working directory

Hi Tim, On Mon, Jul 10, 2017 at 07:32:12AM +0100, Tim Mackinnon wrote: > Just as a side note - a quick spot check of my other recent images (1 > 64 bit normal 6.0 and another 32 bit 6.0, are all correct) - its just > the one where I used the newer vm. I'm not aware of all the changes that have

Re: [Pharo-dev] The new implementation of current working directory

Just as a side note - a quick spot check of my other recent images (1 64 bit normal 6.0 and another 32 bit 6.0, are all correct) - its just the one where I used the newer vm. Tim > On 10 Jul 2017, at 06:32, Rajula Vineet wrote: > > Hey Tim, > > The new implementation

Re: [Pharo-dev] The new implementation of current working directory

Ok - that should rule out those changes, however it may be a sign of things to come (or maybe not - its just the discussions here made me think of what I’m seeing). I am running the image from the command line on OSX Sierra, using 64 bit. If I run System reporter it nicely shows the problem

Re: [Pharo-dev] The new implementation of current working directory

Hi Alistair, From: Alistair Grant [via Smalltalk] Sent: Monday, July 3, 2017 7:29 PM To: Rajula Vineet Reddy(IMT2014045) Subject: Re: The new implementation of current working directory Hi Rajula, On Thu, Jun 29, 2017 at

Re: [Pharo-dev] The new implementation of current working directory

Hey Tim, The new implementation hasn`t been merged into the pharo code base. This error is not related to the new implementation. Probably it is related to your local directories. Are you using a linux? Are you running from the image directory? If you don`t, the path changes and pharo can not

Re: [Pharo-dev] The new implementation of current working directory

I've just realised an important difference which maybe accentuates this thread - my image is actually a v7 vm with a Pharo 6 image and the iceberg update instructions that Esteban sent around. Is it possible the working dir changes are in that new vm? If so, the problem I'm getting might be

Re: [Pharo-dev] The new implementation of current working directory

Guys - I don’t know if this is useful input, but I’ve just noticed a weird issue with the default directory in a new Pharo6 image (probably related to this thread). I’m trying to write my first baselineOf: metacello method - and have been confused that when testing it out, I get a walkback

Re: [Pharo-dev] The new implementation of current working directory

Hi Rajula, On Thu, Jun 29, 2017 at 05:42:02AM -0700, Rajula Vineet wrote: > Hi all, > > As I have already been posting about my GSoC work and updates on my blog > and on the mailing list >

Re: [Pharo-dev] The new implementation of current working directory

On Fri, Jun 30, 2017 at 4:12 PM, Guillermo Polito wrote: > > > On Fri, Jun 30, 2017 at 9:56 AM, Alistair Grant > wrote: > >> Rajula, thanks for your write-up. >> >> As the person who pushed Rajula to send his email I feel I should >> respond.

Re: [Pharo-dev] The new implementation of current working directory

Hi Guillermo, On Fri, Jun 30, 2017 at 10:12:32AM +0200, Guillermo Polito wrote: > On Fri, Jun 30, 2017 at 9:56 AM, Alistair Grant wrote: > > Rajula, thanks for your write-up. > > As the person who pushed Rajula to send his email I feel I should > respond. >

Re: [Pharo-dev] The new implementation of current working directory

On Fri, Jun 30, 2017 at 9:56 AM, Alistair Grant wrote: > Rajula, thanks for your write-up. > > As the person who pushed Rajula to send his email I feel I should > respond. > > While I'm in favour of Rajula's proposed changes, scripting in > particular will be much easier,

Re: [Pharo-dev] The new implementation of current working directory

Thanks for the detailed explanation Rajula. I think it makes perfect sense to separate working and image directories from each other. What you didn't mention is how the current working directory is resolved when an image is not started from the command line but by using the operating systems

Re: [Pharo-dev] The new implementation of current working directory

> On 30 Jun 2017, at 09:56, Alistair Grant wrote: > > Rajula, thanks for your write-up. > > As the person who pushed Rajula to send his email I feel I should > respond. > > While I'm in favour of Rajula's proposed changes, scripting in > particular will be much easier,

Re: [Pharo-dev] The new implementation of current working directory

Rajula, thanks for your write-up. As the person who pushed Rajula to send his email I feel I should respond. While I'm in favour of Rajula's proposed changes, scripting in particular will be much easier, I think we need to make the change generally known as it will not always be obvious, e.g. at

[Pharo-dev] The new implementation of current working directory

Hi all, As I have already been posting about my GSoC work and updates on my blog and on the mailing list . In this post, I would like to go in depth of my work on