DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:message-id:date:from:mime-version:to:subject
	:content-type:content-transfer-encoding; q=dns; s=default; b=bEe
	J2SQqLbJmeYPCz/4CttIutRwL96IMTPo+9/HQ35sEqy+kgflRk1B/bwxXjEaOp+7
	kYvY4HlZ/7Q0LE21M12qMCrjrBeSpy6n9QUQ4LI7Ywxo7Wyjn5zuDk3V7b7LYyHh
	fQB0TDJCXdSl7Z5Qwh1GXVd07DsV7gv0JGJD2x8A=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Message-ID: <51F1A863.8060403@etr-usa.com>
Date: Thu, 25 Jul 2013 16:36:19 -0600
From: Warren Young <warren@etr-usa.com>
User-Agent: Mozilla/5.0 (Windows NT 6.2; WOW64; rv:17.0) Gecko/20130620 Thunderbird/17.0.7
MIME-Version: 1.0
To: Cygwin-L <cygwin@cygwin.com>
Subject: BLODA extension: console interoperability
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I don't see any console programs on the BLODA.  Shouldn't it include 
programs that break under Cygwin due to things like the change from 
Windows console to mintty, or the pty (?) work that improves Linux/POSIX 
semantics?

Then there are the even older class of programs that didn't work right 
even in the cygwin.bat days.  I seem to recall that programs in this 
class failed because they knew too much about how the Windows console 
worked, and Cygwin couldn't intercept certain direct console accesses 
for some reason.

I ask only because I don't run into this sort of thing very often, so I 
didn't have any examples at hand when the issue came up in a question 
raised in another forum.  Ideally, I'd have been able to reference a 
program that comes with Windows.

The only program I currently use that I know has such problems is rather 
obscure, so it wasn't a suitable example.  I don't even know that it's 
popular enough to be listed in this proposed BLODA extension.  (It's 
fsharpi.exe from the F# command line toolchain. http://goo.gl/1GOK86 
I'm not even entirely sure what the problem was, since I switched to a 
Windows console for it over a month ago.  Something about it being 
un-Ctrl-C-able when it is in certain states.)

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