From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: CYGWIN=tty round 2
Date: Tue, 24 May 2011 06:22:00 -0000 [thread overview]
Message-ID: <20110524062212.GA13144@ednor.casa.cgf.cx> (raw)
In-Reply-To: <4DDAEBEC.6030704@ece.cmu.edu>
On Mon, May 23, 2011 at 07:21:16PM -0400, Ryan Johnson wrote:
>On 22/05/2011 10:53 PM, Yaakov (Cygwin/X) wrote:
>>On Sun, 2011-05-22 at 17:19 -0400, Christopher Faylor wrote:
>>>I don't think we saw anyone step forward with a valid reason why they
>>>needed to use CYGWIN=tty over something like "mintty".
>>>
>>>I've summarized the thread where Corinna asked why people used
>>>CYGWIN=tty over CYGWIN=notty below.
>>>
>>>I don't see any showstoppers here so unless people can provide specific
>>>examples of how this change would cause hardwhip, we'll be removing
>>>CYGWIN=tty in a snapshot near you soon.
>>I could add XWin:
>>
>>http://sourceware.org/bugzilla/show_bug.cgi?id=9763
>>
>>And once again, using mintty is a solution.
>>
>>Since mintty is the solution to so many of these scenarios, shouldn't
>>we make it the default terminal (IOW add mintty to Base and replace the
>>Cygwin.bat shortcut with mintty's)? The status quo just encourages
>>people to use a deficient terminal without any idea that a better one
>>exists.
>I would be happy to see mintty as the default. Since discovering it I
>essentially stopped using X because xterm was my main reason for firing
>it up.
>
>However... isn't there some dire warning that gdb only will ever work
>properly (some of the time) from within a vanilla console window?
>Something to do with ^C handling?
>
>Mind you, I'd love that restriction to be lifted, but it sounded pretty
>hard and fast the last few times the topic came up. On the other hand,
>most casual cygwin users won't be needing gdb often, if ever, so that
>might not be enough reason to keep the console over mintty.
Can we PLEASE stay on topic?
This has nothing to do with CYGWIN=tty. If gdb didn't work in mintty it
wouldn't work with CYGWIN=tty either.
--
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-24 6:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-22 21:19 Christopher Faylor
2011-05-23 2:53 ` Yaakov (Cygwin/X)
2011-05-23 6:02 ` Christopher Faylor
2011-05-23 17:27 ` Christopher Faylor
2011-05-23 11:49 ` Andy Koppe
2011-05-23 15:40 ` Corinna Vinschen
2011-05-23 23:21 ` Ryan Johnson
2011-05-24 6:22 ` Christopher Faylor [this message]
2011-05-24 9:54 ` Ryan Johnson
2011-05-23 9:36 ` Sven Köhler
2011-05-23 11:13 ` David Sastre
2011-05-23 21:24 Angelo Graziosi
2011-05-23 21:41 ` Fahlgren, Eric
2011-05-23 22:27 ` Christopher Faylor
2011-05-23 22:01 Angelo Graziosi
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=20110524062212.GA13144@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@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).