From: "Lars Bjørndal" <lars@lamasti.net>
To: cygwin@cygwin.com
Subject: Re: [Lars Bjørndal] Re: brltty problems with recent snapshots
Date: Thu, 14 Jul 2011 10:56:00 -0000 [thread overview]
Message-ID: <20110714105621.GJ2853@lamasti.net> (raw)
In-Reply-To: <20110714101609.GF2125@calimero.vinschen.de>
On Thu, Jul 14, 2011 at 12:16:09PM +0200, Corinna Vinschen wrote:
> On Jul 14 10:19, Lars Bjørndal wrote:
[...]
> > There is also some issues when navigating in an emacs buffer with
> > cursoring keys. A beep is produced every time the cursor moves over a
> > line break. Try also to type a tab character and then use left arrow.
> > You'll then hear a beep. Also spaces generates beeps if you navigate
> > between them, but I'm not sure if that happens all the time.
>
> I can't reproduce this. Is your TERM variable set to something
> other than "cygwin"?
Sorry. It turned out that this beeps came from a GUI screen reader,
Window-Eyes running, with speech and braill deactivated while in cmd.
One problem is left, which I'm not sure if it's a BRLTTY or cygwin
problem:
BRLTTY has a cut & paste facility. It sometimes doesn't paste all
characters inside cygwin. Pasting an att sign into a shell prompt, the
terminal beeps, and no character is written. Doing the same thing
after exiting bash, but still with BRLTTY running and in a cmd
session, the att sign is printed.
I'm not sure if you can cut & paste with BRLTTY without a braille
display. Let's ask Samuel.
Thanks and regards,
Lars
--
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
next prev parent reply other threads:[~2011-07-14 10:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-13 11:42 Lars Bjørndal
2011-07-13 12:35 ` Lars Bjørndal
2011-07-13 13:07 ` Corinna Vinschen
2011-07-13 15:37 ` Christopher Faylor
2011-07-13 13:06 ` [Lars Bjørndal] " Corinna Vinschen
2011-07-13 13:37 ` Samuel Thibault
2011-07-13 19:01 ` Corinna Vinschen
2011-07-13 19:25 ` Lars Bjørndal
2011-07-13 20:00 ` Corinna Vinschen
2011-07-14 8:20 ` Lars Bjørndal
2011-07-14 10:16 ` Corinna Vinschen
2011-07-14 10:56 ` Lars Bjørndal [this message]
2011-07-14 12:42 ` Samuel Thibault
2011-08-19 2:38 ` Issue with inserting '@' at the command prompt Samuel Thibault
2011-08-19 2:45 ` Samuel Thibault
2011-08-19 11:50 ` Corinna Vinschen
2011-08-19 13:15 ` Samuel Thibault
2011-08-19 13:51 ` Corinna Vinschen
2011-08-19 14:07 ` Samuel Thibault
2011-08-19 15:09 ` Corinna Vinschen
2011-08-19 15:16 ` Samuel Thibault
2011-08-19 15:33 ` Corinna Vinschen
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=20110714105621.GJ2853@lamasti.net \
--to=lars@lamasti.net \
--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).