X-Spam-Check-By: sourceware.org Message-ID: <85a409ca0605211855r63e15d59o3db1f55e3a321be2@mail.gmail.com> Date: Mon, 22 May 2006 13:55:24 +1200 From: "Paul Dorman" To: cygwin@cygwin.com Subject: Re: Reading Term::ReadKey support for ActiveState Perl and Cygwin In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Disposition: inline References: <85a409ca0605211622q7acb3708v897b20652c7c31d0@mail.gmail.com> X-IsSubscribed: yes Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Delivered-To: mailing list cygwin@cygwin.com Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by delorie.com id k4M1tZff016239 Yes, I've done some more research and experimentation and determined the lack of STDIN and STOUT in Cygwin makes it impossible to do what I would like with ActiveState Perl. I don't mind Cygwin Perl at all, but here we must use the ActiveState implementation (by policy). Is this situation likely to improve in the future? Could a real terminal be created for Cygwin complete with STDIN and STDOUT? I imagine it's a pretty difficult thing to implement... Thanks for your reply. Rgds, Paul -- 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/