Re: "read" bug in Cygwin 1.5.16?

[Peter Farley <pjfarley3 at yahoo dot com>]

Thanks Brian, but I don't think support on earlier
versions of cygwin is going to be an issue.  There's
only one other person who tried and found this same
bug, so we're somewhat "rara avis" (rare birds).

If the snapshot fix works, I can wait for the release
to come out.  It isn't that urgent, since my
workaround is just to run in a console window instead
of an xterm.

Thanks again for the help.

Peter

--- Brian Dessent <brian@dessent.net> wrote:
> 
> Christopher Faylor wrote:
> 
> > There was a problem with setting VMIN == VTIME ==
> 0 on ttys/ptys.  I've
> > just checked in a fix.  It will be in today's
> snapshot, when it shows
> > up: http://cygwin.com/snapshots/ .
> 
> Peter Farley wrote:
> 
> >     kbattr.c_cc[VMIN] = 0;
> >     kbattr.c_cc[VTIME] = 0;
> 
> If you're always using select() to read, you could
> set VMIN = 1 as a workaround if you need to support 
> versions of Cygwin prior to the above fix.
> 
> Brian


__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/