Re: Visible Ctrl-C in latest kernels

["Vegard Nossum" <vegard.nossum@gmail.com>]

On Fri, Aug 22, 2008 at 10:15 PM, Chris Frey <cdfrey@foursquare.net> wrote:
> Hi,
>
> A fairly user-level question here.
>
> I recently upgraded from 2.6.24.3 to 2.6.26.3.
>
> 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.

That is a feature which was introduced in

commit ec5b1157f8e819c72fc93aa6d2d5117c08cdc961
Author: Joe Peterson <joe@skyrush.com>
Date:   Wed Feb 6 01:37:38 2008 -0800

    tty: enable the echoing of ^C in the N_TTY discipline

    Turn on INTR/QUIT/SUSP echoing in the N_TTY line discipline (e.g.  ctrl-C
    will appear as "^C" if stty echoctl is set and ctrl-C is set as INTR).

    Linux seems to be the only unix-like OS (recently I've verified this on
    Solaris, BSD, and Mac OS X) that does *not* behave this way, and I really
    miss this as a good visual confirmation of the interrupt of a program in
    the console or xterm.  I remember this fondly from many Unixs I've used
    over the years as well.  Bringing this to Linux also seems like a good way
    to make it yet more compliant with standard unix-like behavior.

    [akpm@linux-foundation.org: coding-style fixes]
    Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>
    Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
    Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>

Are you experiencing a problem related to this?


Vegard

-- 
"The animistic metaphor of the bug that maliciously sneaked in while
the programmer was not looking is intellectually dishonest as it
disguises that the error is the programmer's own creation."
	-- E. W. Dijkstra, EWD1036