- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] #currentWorkingDirectoryPath is not correct on macOS when using drag and drop to open

by Alistair Grant

Hi Max, On Fri, 8 Mar 2019 at 08:21, Max Leske <maxleske(a)gmail.com> wrote: > > Hi, > > OSPlatform>>currentWorkingDirectoryPath (used by Path>>workingDirectory, > used by Metacello to resolve local paths) always answers '/' for me when > I drag the image onto the VM to open. I'm sure that's a "feature" of > macOS but it's very annoying. > In addition, FileLocator imageDirectory answers the correct > workingDirectory because it uses a primitive instead of the FFI call to > getCwd(). > > Is this a known issue? Should I open a new one? This is known behaviour. #imageDirectory and #workingDirectory are distinct concepts. #imageDirectory, obviously, is the location where the image resides, while #workingDirectory is the current working directory for the process. It's unfortunate that MacOS sets cwd to "/" when starting applications through the GUI. It sounds like you are already aware of this, but just to be clear: if you start Pharo from a shell you should see #workingDirectory return the same value as `pwd` in the shell. I'm not a Mac user, so I don't know what other applications typically do, but maybe wrap the startup in a script that changes to something more sensible (in your case above it sounds like changing to the directory where the image is located). But modifying #workingDirectory to answer the image directory isn't a good idea as it breaks lots of other use cases. Cheers, Alistair

March 8, 2019

#currentWorkingDirectoryPath is not correct on macOS when using drag and drop to open

by Max Leske

Hi, OSPlatform>>currentWorkingDirectoryPath (used by Path>>workingDirectory, used by Metacello to resolve local paths) always answers '/' for me when I drag the image onto the VM to open. I'm sure that's a "feature" of macOS but it's very annoying. In addition, FileLocator imageDirectory answers the correct workingDirectory because it uses a primitive instead of the FFI call to getCwd(). Is this a known issue? Should I open a new one? Max

March 8, 2019

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Peter Uhnak

> It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address). That's not the case, maybe you are confused by the latest handful of commits that I made directly. The rest is migrated with monty's mail; you can see "monty authored and peteruhnak committed", or look at the patch of any commit https://github.com/pharo-contributions/OrderPreservingDictionary/commit/e41… Associating the mail with a github account should be enough. Peter On Thu, Mar 7, 2019 at 11:06 PM Torsten Bergmann <astares(a)gmx.de> wrote: > Stef wrote: > > > Note that Peter seem to have converted already one of the projects the > XMLParser is dependent on: "OrderPreservingDictionary" > > > which lives at: > https://github.com/pharo-contributions/OrderPreservingDictionary > > > It has the full history - but no reference to your username (because I > guess Peter did not know your github name/mail address). > > > > Ah cool I was about to do it. > > From the history I guess Peter did it. > > But we should redo it once we know Monty's github user account name to > have him linked in the > history of commits and honour his authorship. > > @Monty: can you tell us your github account user name/ github home? > > Thx > T. >

March 8, 2019

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Torsten Bergmann

Stef wrote: > > Note that Peter seem to have converted already one of the projects the XMLParser is dependent on: "OrderPreservingDictionary" > > which lives at: https://github.com/pharo-contributions/OrderPreservingDictionary > > It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address). > > Ah cool I was about to do it. >From the history I guess Peter did it. But we should redo it once we know Monty's github user account name to have him linked in the history of commits and honour his authorship. @Monty: can you tell us your github account user name/ github home? Thx T.

March 7, 2019

[Pharo 8.0] Build #121: 2708-Deprecate-subscribesendto

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #121 was: FAILURE. The Pull Request #2711 was integrated: "2708-Deprecate-subscribesendto" Pull request url: https://github.com/pharo-project/pharo/pull/2711 Issue Url: https://pharo.fogbugz.com/f/cases/2708 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 7, 2019

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by ducasse

> On 7 Mar 2019, at 19:59, Torsten Bergmann <astares(a)gmx.de> wrote: > > Hi monty, > > yes - it is easy with https://github.com/peteruhnak/git-migration > > It would be good to make it available on the more general location: https://github.com/pharo-contributions > If you tell us your github name we can add you as member. > > Note that Peter seem to have converted already one of the projects the XMLParser is dependent on: "OrderPreservingDictionary" > which lives at: https://github.com/pharo-contributions/OrderPreservingDictionary > It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address). Ah cool I was about to do it. > > I guess we should also convert "Pastell" which is also helpful for XML processing and has XMLParser as dependency. > > I can also help converting - just contact me or Norbert on Discord. > > Thanks > Torsten (a.k.a "astares" on Discord) > > >> Gesendet: Donnerstag, 07. MÃ¤rz 2019 um 11:19 Uhr >> Von: "monty" <monty2(a)programmer.net> >> An: pharo-dev(a)lists.pharo.org >> Betreff: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ >> >> I will move it to github, if that makes things easier for everyone else. >> >> ___ >> montyos.wordpress.com >> >> >>> Sent: Wednesday, January 30, 2019 at 3:13 PM >>> From: "Sven Van Caekenberghe" <sven(a)stfx.eu> >>> To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >>> Cc: monty <monty2(a)programmer.net> >>> Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ >>> >>> >>> >>>> On 3 Oct 2018, at 07:43, monty <monty2(a)programmer.net> wrote: >>>> >>>> I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. >>> >>> Has there been any progress in this area ? >>> >>> It would be really great if this important project moved to GitHub. >>> >>> Sven >>> >>> >> >> >

March 7, 2019

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by ducasse

Thanks Monty I had on my todo to port OrderedPreserving. If you want I can do it because I wanted to integrate it in the collection of collections Iâm slowly building. So let me know. Stef > On 7 Mar 2019, at 11:19, monty <monty2(a)programmer.net> wrote: > > I will move it to github, if that makes things easier for everyone else. > > ___ > montyos.wordpress.com > > >> Sent: Wednesday, January 30, 2019 at 3:13 PM >> From: "Sven Van Caekenberghe" <sven(a)stfx.eu> >> To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> >> Cc: monty <monty2(a)programmer.net> >> Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ >> >> >> >>> On 3 Oct 2018, at 07:43, monty <monty2(a)programmer.net> wrote: >>> >>> I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. >> >> Has there been any progress in this area ? >> >> It would be really great if this important project moved to GitHub. >> >> Sven >> >> >

March 7, 2019

[Pharo 8.0] Build #120: 2771-Introduce-new-debuggers

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #120 was: FAILURE. The Pull Request #2772 was integrated: "2771-Introduce-new-debuggers" Pull request url: https://github.com/pharo-project/pharo/pull/2772 Issue Url: https://pharo.fogbugz.com/f/cases/2771 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 7, 2019

Re: [Pharo-dev] Migrating XML support to github/PharoContributions/

by Torsten Bergmann

Hi monty, yes - it is easy with https://github.com/peteruhnak/git-migration It would be good to make it available on the more general location: https://github.com/pharo-contributions If you tell us your github name we can add you as member. Note that Peter seem to have converted already one of the projects the XMLParser is dependent on: "OrderPreservingDictionary" which lives at: https://github.com/pharo-contributions/OrderPreservingDictionary It has the full history - but no reference to your username (because I guess Peter did not know your github name/mail address). I guess we should also convert "Pastell" which is also helpful for XML processing and has XMLParser as dependency. I can also help converting - just contact me or Norbert on Discord. Thanks Torsten (a.k.a "astares" on Discord) > Gesendet: Donnerstag, 07. MÃ¤rz 2019 um 11:19 Uhr > Von: "monty" <monty2(a)programmer.net> > An: pharo-dev(a)lists.pharo.org > Betreff: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > > I will move it to github, if that makes things easier for everyone else. > > ___ > montyos.wordpress.com > > > > Sent: Wednesday, January 30, 2019 at 3:13 PM > > From: "Sven Van Caekenberghe" <sven(a)stfx.eu> > > To: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > Cc: monty <monty2(a)programmer.net> > > Subject: Re: [Pharo-dev] Migrating XML support to github/PharoContributions/ > > > > > > > > > On 3 Oct 2018, at 07:43, monty <monty2(a)programmer.net> wrote: > > > > > > I am the principal maintainer of those projects, but any PharoExtras dev can contribute. And the blog below (which I plan on updating) provides additional information on them. > > > > Has there been any progress in this area ? > > > > It would be really great if this important project moved to GitHub. > > > > Sven > > > > > >

March 7, 2019

[Pharo 8.0] Build #119: 2766-RubScrolledTextMorphcanDiscardEdits-need-to-use-accessor-as-var-can-be-nil

by ci-pharo-ci-jenkins2＠inria.fr

There is a new Pharo build available! The status of the build #119 was: FAILURE. The Pull Request #2767 was integrated: "2766-RubScrolledTextMorphcanDiscardEdits-need-to-use-accessor-as-var-can-be-nil" Pull request url: https://github.com/pharo-project/pharo/pull/2767 Issue Url: https://pharo.fogbugz.com/f/cases/2766 Build Url: https://ci.inria.fr/pharo-ci-jenkins2/job/Test%20pending%20pull%20request%2…

March 7, 2019