The OSProcess implementation for Windows is incomplete. I recommend
Levente's ProcessWrapper (http://www.squeaksource.com/ProcessWrapper/) as
an alternative for Windows.

Dave


> Thanks for the links. Unfortunately none of these really explain what the
> problem with OSProcess is. I see there were attempts to try using
> ProcessWrapper instead of OSProcess on windows, but there's no feedback
> on that thread, so there may be a solution out there, but no one is using
> it.
>
> Levente
>
> On Mon, 3 Aug 2015, Peter Uhnák wrote:
>
>> On Mon, Aug 3, 2015 at 7:14 PM, Levente Uzonyi <[email protected]> wrote:
>>       On Mon, 3 Aug 2015, Peter Uhnák wrote:
>>
>>
>>                   but the git user experience under Windows has to be
>> improved if we want to use efficiently the other
>> functionalities of github (pull requests, commit,
>> branches,…).
>>
>>
>>             Well some of the experience can be mitigated with tools like
>> GitHub for Windows, but the main problem is that git with
>> Pharo is incredibly unstable on Windows and crashes
>> constantly.
>>             That's our experience
>>             with it so my colleague had to switch to pure filetree out
>> of frustration.
>>             This however is NOT problem of git, it's problem of
>> OSProcess. But it does render it almost unusable for now.
>> (At least for us.)
>>
>>
>>       What's the problem with OSProcess on windows?
>>
>>
>> http://forum.world.st/Gitfiletree-unstable-on-Windows-td4816354.html
>> http://forum.world.st/gitfiletree-metadata-td4838970.html
>> http://forum.world.st/Git-gitfiletree-on-Pharo-vs-Windows-td4806791.html
>>
>>



Reply via email to