Jan. 25, 2015
3:21 p.m.
On Sun, Jan 25, 2015 at 09:54:12AM +0100, Sven Van Caekenberghe wrote:
On 25 Jan 2015, at 07:13, Pierce Ng <pierce@samadhiweb.com> wrote:
On OSX, "OSProcessAccessor forThisOSProcess primGetCurrentWorkingDirectory" gives "/", while on Linux the same gives "/home/pierce/work/pharo30". (Above requires the OSProcess package which is available from the Config Browser.)
That sounds right. It calls getcwd() from the VM process. primGetCurrentWorkingDirectory "Call getcwd() to get the current working directory." The current working directory of the VM process will ("man 3 getcwd" for an exact description) will vary depending on how you launch the VM. Dave
Why not just use
FileSystem disk workingDirectory
?