From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Who's using "CYGWIN=tty" and why?
Date: Mon, 09 May 2011 16:34:00 -0000 [thread overview]
Message-ID: <20110509163408.GK27739@calimero.vinschen.de> (raw)
In-Reply-To: <f5bzkmv6e1d.fsf@calexico.inf.ed.ac.uk>
On May 9 17:21, Henry S. Thompson wrote:
> Corinna Vinschen writes:
>
> > Chris and I are wondering how many people are using the Windows console
> > as local console window in CYGWIN=tty mode and why.
>
> I am one such.
>
> > Here's why we ask:
> >
> > We are both not sure why anybody would use it voluntarily, given that
> > it's I/O is extremly slow, compared to using a Windows console window in
> > the default CYGWIN=notty mode or, even better, mintty. Actually, we
> > only keep the console tty mode up because it was "always there", 14
> > years or so.
>
> Um, history is sticky, is I guess the answer. When I started using
> cygwin (a _long_ time ago), CYGWIN=tty was the recommended setting
> (and isn't it still there in cygwin/cygwin.bat ?). So I have
No, it's not the default, and it never was, actually.
> faithfully copied that into my Windows environment initialisation ever
> since. Is it time to remove it? I do use a windows console
> occasionally for pure Windows activities---what change(s) will I see?
I don't quite understand, if you use the Windows console for pure
Windows stuff, why do you use tty mode at all? And what do you use
to run Cygwin apps?
Many native Windows tools don't work well in tty mode anyway. For
non-Cygwin tools, the default notty mode is the most compatible one.
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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
next prev parent reply other threads:[~2011-05-09 16:34 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 16:11 Corinna Vinschen
2011-05-09 16:21 ` Henry S. Thompson
2011-05-09 16:34 ` Corinna Vinschen [this message]
2011-05-09 17:37 ` Henry S. Thompson
2011-05-10 8:56 ` Corinna Vinschen
2011-05-10 1:42 ` rifter rifter
2011-05-09 16:32 ` Andrew Schulman
2011-05-09 16:40 ` Edward Lam
2011-05-09 17:03 ` Ken Brown
2011-05-09 20:00 ` Christopher Faylor
2011-05-09 20:06 ` Christopher Faylor
2011-05-09 17:41 ` Lee Maschmeyer
2011-05-09 17:52 ` Samuel Thibault
2011-05-09 20:05 ` Christopher Faylor
2011-05-09 20:23 ` Samuel Thibault
2011-05-10 14:09 ` Corinna Vinschen
2011-05-10 14:59 ` Andy Koppe
2011-05-10 13:39 ` Lee Maschmeyer
2011-05-10 15:36 ` Charles Wilson
2011-05-10 16:45 ` Lee Maschmeyer
2011-05-09 21:14 ` Karl M
2011-05-09 21:39 ` Jeremy Bopp
2011-05-09 22:27 ` Thomas Wolff
2011-05-09 23:18 ` Christopher Faylor
2011-05-10 2:30 ` Claude Sylvain
2011-05-10 8:29 ` Csaba Raduly
2011-05-10 9:02 ` Corinna Vinschen
2011-05-10 13:38 ` Buchbinder, Barry (NIH/NIAID) [E]
2011-05-10 17:19 ` Christopher Faylor
2011-05-10 17:50 ` Christopher Faylor
2011-05-10 22:12 ` Buchbinder, Barry (NIH/NIAID) [E]
2011-05-10 22:17 ` Christopher Faylor
2011-05-10 14:51 ` Bernhard Ege
2011-05-10 14:58 ` Jeremy Bopp
2011-06-08 19:30 ` Christopher Faylor
2011-05-10 21:18 Len Giambrone
2011-05-11 6:35 ` Corinna Vinschen
2011-05-11 10:12 ` David Antliff
2011-05-11 15:02 ` Edward Lam
2011-05-11 15:40 ` Christopher Faylor
2011-05-11 16:00 ` Andy Koppe
2011-05-11 16:00 ` Edward Lam
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=20110509163408.GK27739@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@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).