From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin-talk@cygwin.com
Subject: Re: Who's using "CYGWIN=tty" and why?
Date: Wed, 11 May 2011 16:19:00 -0000 [thread overview]
Message-ID: <20110511161902.GB23628@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4DCAB14F.5000506@cwilson.fastmail.fm>
On Wed, May 11, 2011 at 11:54:55AM -0400, Charles Wilson wrote:
>On 5/11/2011 11:36 AM, Christopher Faylor wrote:
>> On Wed, May 11, 2011 at 11:02:40AM -0400, Edward Lam wrote:
>>> Personally, when I first ran into this problem, I never realized that
>>> CYGWIN=tty would fix it. I did notice that there was a change in the
>>> behavior between Cygwin B20 and the Cygwin 1.X releases but I only
>>> realize now that this was probably the reason.
>>
>> Ding, ding ding!
>>
>> A B20 reference! B20 was da bomb!
>
>I realize this is sacrilege, but...somewhere in my archives I have an
>old copy of full.exe from B20.1 (as well as the ancient cygutils add-on
>packages; while the webpages for B20-era cygutils still exist at
>http://cygutils.fruitbat.org/OBSOLETE/B20/index.html, the tarballs do
>not. I still have 'em somewhere...)
>
>I ought to install it on XP or Vista and see just how awful it really
>is, compared to modern versions. [/bad sacrilegious Chuck. No cookie!]
Wasn't B20 auto-adaptable to new versions of Windows? I suspect that,
if you just let it sit for a while, it will probably figure out how
to run on XP or Vista.
cgf
prev parent reply other threads:[~2011-05-11 16:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110510211800.CCBDF9D5A21@mail2.intersystems.com>
[not found] ` <20110511063433.GD28594@calimero.vinschen.de>
[not found] ` <4DCAA510.9000909@sidefx.com>
2011-05-11 15:36 ` Christopher Faylor
2011-05-11 15:55 ` Charles Wilson
2011-05-11 16:19 ` Christopher Faylor [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20110511161902.GB23628@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--cc=cygwin-talk@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).