Le 29/04/2016 18:22, Peter Uhnák a écrit :
Welp apparenty GitFileTree has already switched to
OSSubprocess… which
means that since I use Moose I can no longer commit my code… which is
fun. -_-
I suspected this was the problem.
I can setup GitFileTree so that it may either use OSProcess /
OSSubprocess depending on what is already installed. Would that solve
your problem?
Thierry
There is a method to try to disable OSProcess… which
does work in fresh
Moose image, just not mine apparently…
As for the points, it seems strange to me that a user would have to take
explicit action to decide just because the underlying mechanism is poor.
As an end-user, even though a developer, this is not a good solution.
How do other systems do this? In python I can use X different commands
and libraries… os, subprocess, popen2… and I don't need to care about
some super-low-level semaphores between several libraries.
If we want to deprecate OSProcess I really don't see why it should be
the primary subsystem…
Well... I think there could be an easy way, but that may involve
either hacks/overrides or code change in OSProcess.
What's wrong with making code changes to OSProcess?
Peter