https://github.com/SquareBracketAssociates/DeepIntoPharo

I will wait for the new version of pillar to port it. Right now I
cannot latex it on my machine.

Stef

On Thu, Jan 18, 2018 at 7:25 PM, Alistair Grant <akgrant0...@gmail.com> wrote:
> Hi Stef,
>
> On 18 January 2018 at 18:43, Stephane Ducasse <stepharo.s...@gmail.com> wrote:
>> Tx alistair
>>
>> this is great that we made progress on this point.
>> May be we should update the fileSystem chapter
>
> Yep.  Can you point me to the source?  I will try and take a look.
>
> I also think I'll add #workingDirectory: (be able to set the working
> directory).  I know Rajula did the work, but it didn't make it in to
> the PR for some reason.  Hopefully I can dig it up.
>
> Cheers,
> Alistair
>
>
>
>
>> On Thu, Jan 18, 2018 at 9:51 AM, Alistair Grant <akgrant0...@gmail.com> 
>> wrote:
>>> Hi Hilaire & Denis,
>>>
>>> On 18 January 2018 at 09:38, Denis Kudriashov <dionisi...@gmail.com> wrote:
>>>> Also notice that OS can give program very surprising working directory when
>>>> you run it using UI tools.
>>>> For example in MacOS drag image to the vm using Finder assigns root (/) as
>>>> working directory.
>>>>
>>>>
>>>> 2017-12-15 21:38 GMT+01:00 Hilaire <hila...@drgeo.eu>:
>>>>>
>>>>> Oh, in a build for a DrGeo app based on P7, the working directory is one
>>>>> level highter to the image folder.
>>>>>
>>>>> So in P7, there are two different results for the working directory: the
>>>>> user home directory, and one level hight to image dir.
>>>>>
>>>>> What's the context? Where to look at?
>>>
>>> For Pharo 7:
>>>
>>> The working directory is C getcwd().  The differences you are seeing
>>> will be the result of how Pharo is launched.  If you run it from the
>>> command line, it will be the current directory of the shell.  I don't
>>> use MacOS, but it sounds like dragging a file to an executable always
>>> uses the root directory as cwd.
>>>
>>> The working directory is cached in DiskStore DefaultWorkingDirectory.
>>> It's set at session startup to DiskStore
>>> class>>defaultWorkingDirectory, which ultimately calls getcwd().
>>>
>>> HTH,
>>> Alistair
>>>
>>
>

Reply via email to