public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andy Koppe <andy.koppe@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Who's using "CYGWIN=tty" and why?
Date: Tue, 10 May 2011 14:59:00 -0000	[thread overview]
Message-ID: <BANLkTikaf1ONji9XxET87YH0rAKuB3J1CA@mail.gmail.com> (raw)
In-Reply-To: <20110510140819.GS27739@calimero.vinschen.de>

On 10 May 2011 15:08, Corinna Vinschen wrote:
> Samuel,
>
> On May  9 22:23, Samuel Thibault wrote:
>> Christopher Faylor, le Mon 09 May 2011 16:05:24 -0400, a écrit :
>> > Has anyone tried running brltty without setting CYGWIN=tty?
>>
>> I never set the CYGWIN variable nowadays, actually, and brltty works
>> fine in that case.
>
> do you happen to know why brltty doesn't work with mintty?  Is there
> a chance to make this work?

On 9 May 2011 18:40, Lee Maschmeyer wrote:
> 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.

I've had a quick look at the brltty source and documentation, in
particular the chapter on supported screen drivers at [1]. Brltty
requires access to the full screen buffer of a console or terminal.

The Cygwin and native Windows versions of brltty default to using the
Windows console API to access the screen buffer of console windows.
Mintty, rxvt, and others of course aren't based on Windows consoles,
so that method won't work there. And since there's no documented or
otherwise obvious way for third party programs to implement the
Windows console API, this is a dead end.

However, brltty also has a driver for cooperating with GNU Screen,
which can be enabled with the option '-x sn' . This requires a patch
to Screen though that makes its screen buffers available to brltty via
shared memory. With that, it ought to be possible to make brltty work
with any terminal emulator, plus you'd get the added features of
Screen.

Andy

[1] http://mielke.cc/brltty/doc/Manual-BRLTTY/English/BRLTTY-11.html

--
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-10 14:59 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 [this message]
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=BANLkTikaf1ONji9XxET87YH0rAKuB3J1CA@mail.gmail.com \
    --to=andy.koppe@gmail.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).