From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 23181 invoked by alias); 26 Jul 2013 15:29:54 -0000 Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm Precedence: bulk List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@cygwin.com Mail-Followup-To: cygwin@cygwin.com Received: (qmail 23156 invoked by uid 89); 26 Jul 2013 15:29:54 -0000 X-Spam-SWARE-Status: No, score=3.2 required=5.0 tests=AWL,BAYES_50,RCVD_IN_DNSWL_NONE,RCVD_IN_HOSTKARMA_YE,RDNS_NONE,TO_NO_BRKTS_PCNT autolearn=no version=3.3.1 Received: from Unknown (HELO mho-02-ewr.mailhop.org) (204.13.248.72) by sourceware.org (qpsmtpd/0.84/v0.84-167-ge50287c) with ESMTP; Fri, 26 Jul 2013 15:29:53 +0000 Received: from pool-173-48-46-190.bstnma.fios.verizon.net ([173.48.46.190] helo=cgf.cx) by mho-02-ewr.mailhop.org with esmtpa (Exim 4.72) (envelope-from ) id 1V2jxh-0003TQ-M9 for cygwin@cygwin.com; Fri, 26 Jul 2013 15:29:45 +0000 Received: from localhost (ednor.casa.cgf.cx [192.168.187.5]) by cgf.cx (Postfix) with ESMTP id 8E1E760141 for ; Fri, 26 Jul 2013 11:29:44 -0400 (EDT) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1/uUh0LBt+BefHRpsvZiOnT Date: Fri, 26 Jul 2013 16:22:00 -0000 From: Christopher Faylor To: cygwin@cygwin.com Subject: Re: BLODA extension: console interoperability Message-ID: <20130726152944.GD4495@ednor.casa.cgf.cx> Reply-To: cygwin@cygwin.com Mail-Followup-To: cygwin@cygwin.com References: <51F1A863.8060403@etr-usa.com> <51F1AF90.3080409@cygwin.com> <51F1F7B4.4060202@etr-usa.com> <003601ce89f8$c3845f10$4a8d1d30$%fedin@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <003601ce89f8$c3845f10$4a8d1d30$%fedin@samsung.com> User-Agent: Mutt/1.5.20 (2009-06-14) X-SW-Source: 2013-07/txt/msg00585.txt.bz2 On Fri, Jul 26, 2013 at 04:07:55PM +0400, Pavel Fedin wrote: > Hello! > >> I don't think that's fair, since such apps were designed for the >> Windows console, without being aware of Cygwin's pipe-based ptys. And >> unfortunately that list would be very long anyway: basically anything >> interactive that hasn't been explicitly adapted to Cygwin ptys > > Let me also drop my 5 cents into this... >We should be very careful about this. At least there is one case where >difference between Cygwin console and real Windows console plays a key >role: ncurses. Normal Windows console is very basic and does not >understand 90% of control sequences. As a result, ncurses has been >extended with 'terminal drivers', which redirect certain control >functions to OS (Windows in our case) API calls. Which, of course, >work only with real Windows console. The "console" that a Cygwin program sees is not just the raw Windows console. Hopefully the Cygwin version of ncurses understands that Cygwin extends the functionality of the console so that a big subset of standard control sequences will just work. cgf -- 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