On 19 March 2016 at 16:45, Peter Uhnák <i.uh...@gmail.com> wrote: > I don't actually see the reason why it should assume root folder if you > don't specify a path… that's stupid on many levels (I blame mac). >
It's root because that's where the system launches applications from, when you double-click them in the Finder (or via the open command, I think). You'll see that GUI-launched images do not inherit your shell environment either. However, if you run pharo from command-line, you get the usual unix behavior. > On Linux you get home, although that's imho also wrong and it should use > the folder of the image… but maybe that's a misconfiguration of OSProcess. > No, it's the same logic than on Mac (albeit $HOME is arguably a little more sensible than the filesystem's root). I'm not sure what's the correct behavior here, unless there is a way to know if pharo was launched from GUI (where working directory is meaningless and pharo should probably chdir() to the image directory) or from command-line (where the working directory is meaningful and should be honored. On OSX, maybe there's a way to pass GUI-specific arguments, through the Info.plist file?
