public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Lee Maschmeyer <lee_maschmeyer@wayne.edu>
Cc: cygwin@cygwin.com, dave@mielke.cc
Subject: Re: Who's using "CYGWIN=tty" and why?
Date: Mon, 09 May 2011 17:52:00 -0000	[thread overview]
Message-ID: <20110509175205.GA5069@const.famille.thibault.fr> (raw)
In-Reply-To: <CCD7B66B83144FC29DC158B10C564CC0@cit.wayne.edu>

Lee Maschmeyer, le Mon 09 May 2011 13:40:57 -0400, a écrit :
> And, truth to tell, I've been around here for a good long time and
> never heard of CYGWIN=notty.

As I understand it, notty is already the default, so unless you have an
explicit CYGWIN=tty, it's already notty.

brltty does not touch at the cygwin tty layer. It just uses
native win32 interfaces to access the consoles (AttachConsole,
ReadConsoleOutputCharacterW) and simulate keypresses
(WriteConsoleInputW), consoles need to be windows console, but that's
all.

Samuel

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

  reply	other threads:[~2011-05-09 17:52 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 [this message]
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     ` 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=20110509175205.GA5069@const.famille.thibault.fr \
    --to=samuel.thibault@ens-lyon.org \
    --cc=cygwin@cygwin.com \
    --cc=dave@mielke.cc \
    --cc=lee_maschmeyer@wayne.edu \
    /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).