From: Willy Tarreau <w@1wt.eu>
To: Chris Frey <cdfrey@foursquare.net>
Cc: Joe Peterson <joe@skyrush.com>,
Vegard Nossum <vegard.nossum@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: Visible Ctrl-C in latest kernels
Date: Mon, 25 Aug 2008 14:20:24 +0200 [thread overview]
Message-ID: <20080825122024.GA19337@1wt.eu> (raw)
In-Reply-To: <20080824010231.GA26030@foursquare.net>
On Sat, Aug 23, 2008 at 09:02:32PM -0400, Chris Frey wrote:
> On Sat, Aug 23, 2008 at 11:52:02AM -0600, Joe Peterson wrote:
> > Vegard Nossum wrote:
> > >> I've noticed that on my Debian stable system, I can now see Ctrl-C characters
> > >> when using an xterm. I've checked the stty settings and nothing seems
> > >> different.
> >
> > Vegard, thanks for forwarding this to me.
> >
> > Chris, yes, what you are now seeing on the newer kernel is correct.
>
> Thanks guys. I was not aware of this change before asking. The change
> makes sense. I wasn't having any problems with it, just wondering where
> it came from.
>
> Thanks for the enlightenment. :-)
I would not be surprized that it is what has caused delays for Ctrl-C
to take effect for some of us. As discussed in another thread on the
subject, the problem was relatively recent and not easy to reproduce.
Now we have a patch to try to revert if/when we finally get a reproducible
case.
Willy
next prev parent reply other threads:[~2008-08-25 12:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-22 20:15 Visible Ctrl-C in latest kernels Chris Frey
2008-08-23 9:53 ` Vegard Nossum
2008-08-23 17:52 ` Joe Peterson
2008-08-24 1:02 ` Chris Frey
2008-08-25 12:20 ` Willy Tarreau [this message]
2008-08-25 14:00 ` Joe Peterson
2008-08-25 14:13 ` Willy Tarreau
2008-08-25 14:29 ` Joe Peterson
2008-08-25 17:37 ` David Newall
2008-08-25 18:03 ` Joe Peterson
2008-08-26 1:08 ` Joe Peterson
2008-08-26 7:40 ` David Newall
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=20080825122024.GA19337@1wt.eu \
--to=w@1wt.eu \
--cc=cdfrey@foursquare.net \
--cc=joe@skyrush.com \
--cc=linux-kernel@vger.kernel.org \
--cc=vegard.nossum@gmail.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