On 09/28/2015 04:13 PM, Ferlicot D. Cyril wrote:
Le 28/09/2015 23:54, Levente Uzonyi a écrit :
If there are so many windows users, then how can it be that none of them
managed to explain what the actual problem with stdio handling is. I had
asked about the problem a while ago, but I still haven't got an answer:
http://forum.world.st/Google-Code-Shutdown-tt4814760.html#a4840937 .
Levente
The problem is that gitfiletree use OSProcess and OSProcess use Stdio to
get the state or the exit value of a command for example.
But in Windows Stdio is just an ugly hack. It doesn't use the stdio but
create 3 files (stdin, stderr' stdout) in the working directory and
write/read this files. But as Windows doesn't use that we can't
communicate with the system.
I tried to have some look at it but I don't even know if it is a vm or
an image problem. Some says that the dll for that is wrong, some says
that this is an image problem. I don't have the knowledge and the time
to go deeper on that problem.
So in order to fix a lot of problem on windows we need to fix the Stdio
but we need someone who have the time and the knowledge and we do not
have a lot of developers that can manage stdio on windows even if we
have users.
+1 ... yeah the stderr is not fun ... I did add some bash error traps
(see my other message about using Git Bash on windows as part of GitHub
Desktop for Windows) so that I could at least arrange to have stderr
dumped to stdout on an error ...
Dale
