>
> It may be a real problem and I appreciate your attempts to track it
> down but since this seems to be working fine for the vast majority of
> things which use the pty, I don't think I'll be fixing it any time soon.
>
> If someone else would like to take a stab at this (hah?) that would be
> swell.
>
Attached is the half-hearted patch against 1.1.5-4 (relative to
winsup/cygwin). The problem happens when someone reads from master side of pty
using 1 byte buffer and onlcr is enabled. In this case read gets CR and
appears to hang after that before it gets NL. It looks, like it "hangs" at the
end of line. The same problem seems to be with select after CR was read - it
thinks, no input is available.
Forgive me my horrible c++; I still do not quite understand all these
inheritance isuues. But the patch appears to work.
-andrej
cygwin-select.diff
--
Want to unsubscribe from this list?
Send a message to [EMAIL PROTECTED]
