public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Lee Maschmeyer" <lee_maschmeyer@wayne.edu>
To: <cygwin@cygwin.com>
Subject: Re: Who's using "CYGWIN=tty" and why?
Date: Tue, 10 May 2011 13:39:00 -0000	[thread overview]
Message-ID: <654F3CDDAF0546FB9A0BA923298D8183@cit.wayne.edu> (raw)
In-Reply-To: <20110509200524.GB10705@ednor.casa.cgf.cx>

Christopher wrote:

>Ok, it sounds like there is no need whatsoever to set CYGWIN=tty with
>brltty.  That is good news.

According to what Ken wrote, emacs won't work as well. This would be very 
distressing, though I haven't verified it personally.

>I'd be pretty surprised if it was the case since if CYGWIN=tty *was*
>required then it seems like mintty would work too since the difference
>between the ptys that mintty uses and CYGWIN=tty mode is very small.

According to one whole trial it's large enough to convince brltty not to 
deal with the window. This is suggestive but hardly conclusive. I'll try 
again...

>Has anyone tried running brltty without setting CYGWIN=tty?

Just now. So far I haven't noticed any problems but this is even less 
significant. I guess "notty" was meant to say that tty should not be 
mentioned at all in the $CYGWIN variable. I'll remove it and see what 
happens.

-- 
Lee Maschmeyer
Wayne State University Computing Center
5925 Woodward, #281
Detroit MI 48202
USA 


--
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

  parent reply	other threads:[~2011-05-10 13:39 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 [this message]
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     ` Edward Lam
2011-05-11 16:00     ` Andy Koppe

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=654F3CDDAF0546FB9A0BA923298D8183@cit.wayne.edu \
    --to=lee_maschmeyer@wayne.edu \
    --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).