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: Mon, 09 May 2011 17:41:00 -0000	[thread overview]
Message-ID: <CCD7B66B83144FC29DC158B10C564CC0@cit.wayne.edu> (raw)
In-Reply-To: <20110509161028.GJ27739@calimero.vinschen.de>

Hi all,

At the risk of exciting the contempt avalanche all too pervasive in this 
list (never at any time by Corinna--THANKS):

I'm not sure I understand the difference between the DOS console and the 
Windows console. And, truth to tell, I've been around here for a good long 
time and never heard of CYGWIN=notty. However:

BRLTTY is a screen reading system that enables the use of refreshable 
braille devices (see below). It works on Linux and other unixes both in 
console mode and as an adjunct to the Unix GUI screen reader (Orca). It also 
works at the DOS command prompt, and gloriously beautifully in Cygwin. I 
tried mintty once and brltty would not read that window. Whether this can be 
changed by the developers I don't know. I've sporadically tried things like 
rxvt and when they didn't work right off the bat I didn't bother anymore 
since brltty is really splendid. For what it's worth, here's my cygwin.bat. 
Exactly how much of it is necessary and what the costs of what changes might 
be I don't know:

@echo off

c:
chdir c:\cygwin\bin
set HOME=c:\cygwin\home\<me>
set LANG=en_US.UTF-8
set CYGWIN=tty notitle glob
bash --login -i

The rest of this message is for the merely curious:

What's a refreshable braille device: It's a box that has a smooth wire 
screen on the top. There are pins below the holes in this wire screen. The 
pins can be pushed up through the holes (these are dots) or pulled down 
below them (these are non-dots). These pins are in eight rows corresponding 
to the eight rows of dots in a braille cell (eight on the computer, six for 
standard paper braille). There are from 18 to 84 of these 8-dot cells across 
the length of the wire screen, and there are buttons on the braille device 
to move this 18-to-84 character window around on the screen.

What's "splendid" about brltty in Cygwin? Other Windows screen readers have 
braille, but frequently it skips blank lines for reasons I don't begin to 
comprehend. Brltty doesn't skip them. So it's much easier to tell the screen 
layout in brltty than with the braille from a Windows screen reader. Brltty 
is also more responsive and more accurate (it doesn't spuriously underline 
letters, one of the problems with braille in other screen readers). While 
the Windows screen reader I use (JAWS) can see the Cygwin text, not all can. 
Narrator is a part of the Windows OS; it's on every Windows computer. It 
can't see the text in Cygwin at all.

I've included the brltty developers on this message and will send them 
Corinna's original so you may hear from somebody who knows what they're 
talking about. :-)

Castigation, Mastication and Denigration cheerfully accepted,

-- 
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-09 17:41 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 [this message]
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=CCD7B66B83144FC29DC158B10C564CC0@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).