public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: cygwin@cygwin.com
Subject: Re: Emacs and removal of CYGWIN=tty
Date: Thu, 30 Jun 2011 16:01:00 -0000	[thread overview]
Message-ID: <20110630160101.GU4471@const.bordeaux.inria.fr> (raw)
In-Reply-To: <iui6dc$j2j$1@dough.gmane.org>

Andrew DeFaria, le Thu 30 Jun 2011 08:57:32 -0700, a écrit :
> On 06/30/11 04:54, Samuel Thibault wrote:
> >Ken Brown, le Thu 30 Jun 2011 07:49:42 -0400, a écrit :
> >>On 6/30/2011 3:58 AM, Lars Bjørndal wrote:
> >>>I've heard that the value of the CYGWIN environment variable 'tty' will
> >>>be unsupported for the next release of cygwin. I use emacs a lot from
> >>>within
> >>>cygwin, and if not CYTWIN=tty is set prior to starting bash, the
> >>>control-c
> >>>character outputs control-g. C-c, c-x is therefore wrongly interpreted
> >>>by emacs. Is there other ways to get emacs works as expected, if the
> >>>variable is removed?
> >>
> >>The problem only occurs in a Windows console, such as the one you get by
> >>using the Cygwin desktop shortcut. Use a different terminal emulator,
> >>such
> >>as mintty, instead.
> >
> >This is not an option, as mintty is not accessible from brltty.
> What's a "brltty"?

The screen reader that blind people use to access cygwin's shell. Only
the windows consoles provide the ReadConsoleOutputCharacter interface.

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-06-30 16:01 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-30  7:59 Lars Bjørndal
2011-06-30 11:49 ` Ken Brown
2011-06-30 11:54   ` Samuel Thibault
2011-06-30 14:09     ` Corinna Vinschen
2011-07-06  7:04       ` Lars Bjørndal
2011-07-06  7:20         ` Corinna Vinschen
2011-07-06  8:03           ` Lars Bjørndal
2011-07-06  8:54             ` Corinna Vinschen
2011-07-06 11:09               ` Lars Bjørndal
2011-07-06 15:29                 ` Christopher Faylor
2011-07-07  7:32                   ` Lars Bjørndal
2011-07-11  0:09                     ` brltty problems with recent snapshots (was Re: Emacs and removal of CYGWIN=tty) Christopher Faylor
2011-07-11  0:11                       ` Samuel Thibault
2011-07-11  0:31                         ` Christopher Faylor
2011-07-11 14:45                           ` Samuel Thibault
2011-07-11 14:58                             ` Christopher Faylor
2011-07-11 19:12                               ` brltty problems with recent snapshots Lars Bjørndal
2011-07-12  7:38                                 ` Corinna Vinschen
2011-07-12 12:45                                   ` Samuel Thibault
     [not found]                                     ` <m37h7m7dnd.fsf@dalen.lamasti.net>
2011-07-13 13:05                                       ` Samuel Thibault
2011-07-13 15:32                                         ` Christopher Faylor
2011-07-13 15:52                                           ` Samuel Thibault
2011-06-30 15:58     ` Emacs and removal of CYGWIN=tty Andrew DeFaria
2011-06-30 16:01       ` Samuel Thibault [this message]

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=20110630160101.GU4471@const.bordeaux.inria.fr \
    --to=samuel.thibault@ens-lyon.org \
    --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).