X-Spam-Check-By:	sourceware.org
To:	cygwin AT cygwin DOT com
From:	Andrew DeFaria <Andrew AT DeFaria DOT com>
Subject:	Re: Reading Term::ReadKey support for ActiveState Perl and Cygwin
Date:	Mon, 22 May 2006 07:57:29 -0700
Lines:	37
Message-ID:	<e4sjgq$gdh$1@sea.gmane.org>
References:	<85a409ca0605211622q7acb3708v897b20652c7c31d0 AT mail DOT gmail DOT com> <Pine DOT GSO DOT 4 DOT 63 DOT 0605212133300 DOT 21697 AT access1 DOT cims DOT nyu DOT edu> <85a409ca0605211855r63e15d59o3db1f55e3a321be2 AT mail DOT gmail DOT com> <Pine DOT GSO DOT 4 DOT 63 DOT 0605212202020 DOT 21697 AT access1 DOT cims DOT nyu DOT edu>
Mime-Version:	1.0
User-Agent:	Thunderbird 1.5.0.2 (Windows/20060308)
In-Reply-To:	<Pine.GSO.4.63.0605212202020.21697@access1.cims.nyu.edu>
X-IsSubscribed:	yes
Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT cygwin DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sourceware.org/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com

Igor Peshansky wrote:
> On Mon, 22 May 2006, Paul Dorman wrote:
>> 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.
> Huh? Cygwin does have STDIN and STDOUT -- they are just not bound to a 
> console, and ActivePerl doesn't like that.
>> I don't mind Cygwin Perl at all, but here we must use the ActiveState 
>> implementation (by policy).
> And what would the crucial difference be between an ActiveState 
> implementation's behavior and Cygwin's? I mean, can't you simply run 
> the Perl script using Cygwin's perl? Then you get the best of both 
> worlds...
I believe Paul said 1) the policy of the company was to use ActiveState 
Perl and 2) not all servers have Cygwin installed. I've hit this stuff 
too. Best you can do is 1) point out the deficiencies of Active State 
(this problem and try calling setsid! IIRC signals were messy and 
unreliable too) and 2) just ignore policy and go around and install 
Cygwin as you need it.
>> 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...
> Most likely not -- Cygwin uses ptys (pipes, essentially) to simulate 
> ttys for processes that can't be bound to a Windows console, and there 
> may be real restrictions (e.g., Windows limitations) for not being 
> able to implement what you're asking for without breaking existing 
> Cygwin functionality. However, if it is really important to your 
> company, you can try looking into funding some research on this 
> (either via a Cygwin support contract with Red Hat, or via direct 
> donations to a private
> developer).
Paul's probably hitting problems with ActiveState due to ptys that you 
get when remotely logging in or when using things like rxvt. Try it from 
a locally logged in DOS box.
-- 
Andrew DeFaria <http://defaria.com>
If you think nobody cares about you, try missing a couple of payments.


--
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/

- Raw text -