delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm |
List-Subscribe: | <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com> |
List-Archive: | <http://sourceware.cygnus.com/ml/cygwin/> |
List-Post: | <mailto:cygwin AT sourceware DOT cygnus DOT com> |
List-Help: | <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs> |
Sender: | cygwin-owner AT sourceware DOT cygnus DOT com |
Delivered-To: | mailing list cygwin AT sourceware DOT cygnus DOT com |
From: | Dtcohen AT aol DOT com |
Message-ID: | <95.95f94d16.25ab9bca@aol.com> |
Date: | Mon, 10 Jan 2000 15:32:10 EST |
Subject: | getc() problem with Cygwin v1.0 |
To: | cygwin AT sourceware DOT cygnus DOT com |
CC: | Dtcohen AT aol DOT com |
MIME-Version: | 1.0 |
X-Mailer: | Unknown (No Version) |
For Cygwin v1.0, getc() returns after every key is typed, instead of waiting for the carriage return. This is incorrect behavior. With Cygwin B20.1 it correctly waits for the carriage return. Does anyone know how this can be fixed? Any pointers to the source of the problem are also appreciated. Many thanks, Jim Grishaw dtcohen AT aol DOT com See also my previous posting: "Blocking I/O with Cygwin v1.0", 1/4/00 -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |