Re: read bug in Cygwin 1.5.16?

2005-05-03 Thread Peter Farley
I tried the 20050501 snapshot today. The bug has been squashed. Both the test program and hercules operate correctly in an xterm window with the snapshot version of cygwin1.dll. Thank you for the fix. I will let the hercules list know that the bug will be resolved in the next release.

Re: read bug in Cygwin 1.5.16?

2005-05-03 Thread Peter Farley
I tried the 20050501 snapshot today. The bug has been squashed. Both the test program and hercules operate correctly in an xterm window with the snapshot version of cygwin1.dll. Thank you for the fix. I will let the hercules list know that the bug will be resolved in the next release.

Re: read bug in Cygwin 1.5.16?

2005-05-02 Thread Peter Farley
Thanks Chris. I will try to test the snapshot soon, but I may have some RL events interrupting me before I can do so. I'll report back after testing. Peter --- Christopher Faylor [EMAIL PROTECTED] wrote: On Sun, May 01, 2005 at 04:56:13PM -0700, Peter Farley wrote: Hi all, I tried to

Re: read bug in Cygwin 1.5.16?

2005-05-02 Thread Peter Farley
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,

read bug in Cygwin 1.5.16?

2005-05-01 Thread Peter Farley
Hi all, I tried to forward this message to the main cygwin list yesterday, but had a little trouble getting it there, probably because I mentioned xterm in the subject. I'm trying again in case this is NOT an X problem but a base cygwin problem. I have attached the test program xtermbug.c

Re: read bug in Cygwin 1.5.16?

2005-05-01 Thread Christopher Faylor
On Sun, May 01, 2005 at 04:56:13PM -0700, Peter Farley wrote: Hi all, I tried to forward this message to the main cygwin list yesterday, but had a little trouble getting it there, probably because I mentioned xterm in the subject. I'm trying again in case this is NOT an X problem but a base

Re: read bug in Cygwin 1.5.16?

2005-05-01 Thread Brian Dessent
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