X-Spam-Check-By: sourceware.org Date: Tue, 23 May 2006 00:05:23 -0700 From: Yitzchak Scott-Thoennes To: cygwin@cygwin.com Subject: Re: Reading Term::ReadKey support for ActiveState Perl and Cygwin Message-ID: <20060523070523.GA756@efn.org> References: <85a409ca0605211622q7acb3708v897b20652c7c31d0@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.1i 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 On Sun, May 21, 2006 at 09:39:16PM -0400, Igor Peshansky wrote: > On Mon, 22 May 2006, Paul Dorman wrote: > > > Hi all, > > > > I've been racking my brains trying to read keystrokes in a Cygwin > > shell with ActiveState Perl. Has anyone worked out how to read > > individual keystrokes with a Perl script running in a Cygwin shell or > > SSH session? We have standardized on ActiveState perl here (as not all > > servers are actually running Cygwin). > > Windows applications (like ActivePerl) are mostly off-topic on this list, > especially since there's a perfectly good Cygwin alternative available > (which, BTW, comes with Term::ReadKey). > > However, you do realize that "a Perl script running in a Cygwin shell or > SSH session" may not even be running in a terminal as ActivePerl > understands it, right? Hence his question, I believe. I'd think ways of making a windows app happy with pty stdin/stdout would be on-topic (though in most cases, changes to the windows app seem to be not an option, so there's not much to talk about.) Paul, can you show what you've tried, and what exactly is the trouble spot? If people really think it's not appropriate to discuss here, perhaps you could ask at: http://perlmonks.org/?node=Seekers+of+Perl+Wisdom. -- 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/