Date: Fri, 13 Apr 2012 10:43:08 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Cc: muis AT ui DOT ac DOT id
Subject: Re: Problem with reading nonblocking /dev/com in 1.7.10 and up
Message-ID: <20120413144308.GA25389@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com, muis AT ui DOT ac DOT id
References: <4F847921 DOT 8020506 AT ui DOT ac DOT id> <20120410193503 DOT GA26267 AT ednor DOT casa DOT cgf DOT cx>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20120410193503.GA26267@ednor.casa.cgf.cx>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Precedence: bulk
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com

Ping?

On Tue, Apr 10, 2012 at 03:35:03PM -0400, Christopher Faylor wrote:
>On Wed, Apr 11, 2012 at 01:17:05AM +0700, Abdul Muis wrote:
>>I have notice that I could not read serial device (/dev/com4 or
>>/dev/ttyS3) with non blocking mode since 1.7.10 and up.
>
>Out of curiosity, is it broken in the 2011-10-22 snapshot?
>
>Be careful if you install it since there may be added stuff added to the
>Cygwin API which would stop a more modern bash or mintty from working so,
>if possible, just test from a cmd window.
>
>http://cygwin.com/snapshots/

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