On 5/8/2011 5:43 PM, Ingo Koch wrote:
>
>> CR/LF - very windows specific
>> LF - is very common on other platforms (*nix)
>> CR - Mac specific I think
>>
>> Without checking is it possible that you are receiving just the LF
>> which you should be able to parse on with stdout output.  If there is
>> no CR/LF,LF, or CR then I think one of these would be considered a
>> reasonable enhancement to Fossil.  It just may that the right choice
>> isn't CR/LF.
> The modification I've made is to add a '\n' to the prompt. So it is
> sufficient to add a LF even on the Windows platform.

Right, as Ingo said, just the '\n' should be sufficient, no need to
worry about CR/CRLF/LF platform specifics. The reason it is necessary, I
believe (I could be wrong), for a parent process, Windows doesn't
actually notify the parent process of the stdout data until a newline is
hit. So, if you spawn a process and monitor the child's stdout/stderr
streams, you don't get that data until a '\n' is sent by the child.
Which is why Ingo needs this change in Fossil in order to write a
wrapper around it.
_______________________________________________
fossil-users mailing list
[email protected]
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to