From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [Lars Bjørndal] Re: brltty problems with recent snapshots
Date: Thu, 14 Jul 2011 10:16:00 -0000 [thread overview]
Message-ID: <20110714101609.GF2125@calimero.vinschen.de> (raw)
In-Reply-To: <m3bowxtgt9.fsf@dalen.lamasti.net>
On Jul 14 10:19, Lars Bjørndal wrote:
> [Corinna Vinschen]
>
> > On Jul 13 15:37, Samuel Thibault wrote:
> >> Corinna Vinschen, le Wed 13 Jul 2011 15:05:50 +0200, a écrit :
> >> > On Jul 13 13:41, Lars Bjørndal wrote:
> >> > > I'm using a com-port, since Modular Evolution has USB2serial conversion.
> >> > >
> >> > > The latest cygwin1.dll that works for me, is 20110502.
> >> >
> >> > Hmm, it seems I introduced a bug into serial I/O afterwards.
> >> > Does brltty use blocking or nonblocking I/O?
> >>
> >> nonblocking.
> >
> > I just applied a patch which tries to handle nonblocking I/O better.
> > Can you give it a try, please?
>
> Thank you! It works perfectly.
>
> Now, back to the original problem, with c-x, c-c within Emacs.
>
> Running Emacs from bash shell, and pressing this sequence, the Emacs
> program exits, as expected. Witin a remote ssh session however, c-c get
> the session to exit with the messsage: "Killed by signal 2".
>
> Steps to reproduce:
>
> 1. Run cmd
>
> 2. bash --login -i
>
> 3. ssh user@host
>
> 4. c-c
Thanks for the report, fixed in CVS.
> 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"?
Corinna
--
Corinna Vinschen Please, send mails regarding Cygwin to
Cygwin Project Co-Leader cygwin AT cygwin DOT com
Red Hat
--
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:16 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 [this message]
2011-07-14 10:56 ` Lars Bjørndal
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=20110714101609.GF2125@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.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).