From: Karl M <karlm30@hotmail.com>
To: <cygwin@cygwin.com>
Subject: RE: Who's using "CYGWIN=tty" and why?
Date: Mon, 09 May 2011 21:14:00 -0000 [thread overview]
Message-ID: <col102-w43D78509B9FA84B2B6886BB5840@phx.gbl> (raw)
In-Reply-To: <20110509161028.GJ27739@calimero.vinschen.de>
> Date: Mon, 9 May 2011 18:10:28 +0200
> From: corinna
> Subject: Who's using "CYGWIN=tty" and why?
>
> Hi,
>
> Chris and I are wondering how many people are using the Windows console
> as local console window in CYGWIN=tty mode and why.
>
> 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.
>
> So, if you're using a console in tty mode, why are doing that? Did you
> ever notice that it's much slower? Did you ever consider to switch to
> mintty or any other terminal emulator instead? If not, why? Would
> anybody really *miss* the CYGWIN=tty mode? If so, why? What does this
> mode have which isn't covered by notty mode or another terminal
> emulator?
>
> Please enlighten us, otherwise we will just rip out this terminal mode
> for good.
>
I use CYGWIN=tty, and have used it forever. Back in the dark ages, I recall
that there were reasons that I chose it...control character handling or
formatting? It made something I cared about work properly and four M$ operating
systems later...
I did try rxvt and didn't like the way it looked, so I stayed with a console
window and CYGWIN=tty.
Thanks,
...Karl
--
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 21:14 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
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 [this message]
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=col102-w43D78509B9FA84B2B6886BB5840@phx.gbl \
--to=karlm30@hotmail.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).