delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/2009/07/05/16:21:10

X-Recipient: archive-cygwin AT delorie DOT com
X-Spam-Check-By: sourceware.org
Date: Sun, 5 Jul 2009 16:20:47 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Re: popup consoles on Windows 7
Message-ID: <20090705202047.GA32479@ednor.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
References: <416096c60906270139y33e2888cq148430eebb744b71 AT mail DOT gmail DOT com> <20090628103010 DOT GT30864 AT calimero DOT vinschen DOT de> <af075b00907020941i666bed61vc450315c662b757a AT mail DOT gmail DOT com> <20090702174425 DOT GC9839 AT ednor DOT casa DOT cgf DOT cx> <af075b00907030218p54b606ds813e824422de04fa AT mail DOT gmail DOT com> <20090703104423 DOT GA18746 AT calimero DOT vinschen DOT de> <20090703150212 DOT GA26858 AT ednor DOT casa DOT cgf DOT cx> <20090704161431 DOT GB11034 AT ednor DOT casa DOT cgf DOT cx> <20090705001152 DOT GA2510 AT ednor DOT casa DOT cgf DOT cx> <416096c60907050233q344d37cds41859c611c7ab660 AT mail DOT gmail DOT com>
MIME-Version: 1.0
In-Reply-To: <416096c60907050233q344d37cds41859c611c7ab660@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
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

I forgot to answer two questions here.

On Sun, Jul 05, 2009 at 10:33:47AM +0100, Andy Koppe wrote:
>Now what's the right way to check for this workaround being present in
>the Cygwin DLL, so that MinTTY can skip its workaround depending on
>that? Should I parse version string from /proc/version? (I intend to
>throw out MinTTY's workaround altogether when going 1.7-only, but for
>the moment it needs to stay.)

I'd add a compile time flag which allows different behavior depending on
whether you're building for 1.7 or 1.5 (assuming that you don't have one
already).  Then when there's a new version of 1.7 you can make a new
version of mintty.  Problem solved there since there is no need to
support old versions of 1.7.

>>I keep saying that I want to fix this and I recently found some public
>>domain code which purports to allow using consoles as "pipes".  I hope
>>I'll have time to look into adding this to Cygwin after 1.7 is
>>released.
>
>Oh, interesting, could you post a link to it?

I didn't save a link but I have pointed at console2 on sourceforge (the
project link seems to be down now) as something which does something
similar.

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019