Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
From:	"linda w \(cyg\)" <cygwin AT tlinx DOT org>
To:	<cygwin AT cygwin DOT com>
Subject:	unexpected control-c propagation to xterm children
Date:	Wed, 18 Dec 2002 18:00:57 -0800
Message-ID:	<000201c2a702$78ea0110$1403a8c0@sc.tlinx.org>
MIME-Version:	1.0
X-Priority:	3 (Normal)
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106
Importance:	Normal
X-MIME-Autoconverted:	from quoted-printable to 8bit by delorie.com id gBJ22wu22568

A problem, I notice with xterm's, I notice that if I start 'xterm&', then any control-c I press in the base window (running bash) is sent to all xterm children (but not grandchildren).  Control-c _in_ an xterm seems to only be sent to the window one typed control-c into (as would be normally expected).

Note that ^c pressed in a different 'bash' window doesn't have this
effect -- it is only a parent running bash that runs an xterm.
I tried io redirection before xterm (xterm </dev/null 2>&1 >/dev/null&),
to no effect.

When I run xterm I do get some warnings:

Warning: locale not supported by C library, locale unchanged
Warning: locale not supported by Xlib, locale set to C
Warning: X locale modifiers not supported, using default
Failed to open input method

I'm wondering if it is related to the "DISPLAY" env var being
set -- like in the ssh case, somehow setting DISPLAY interferes
with local controls, though 'vi[m]' has no problem intercepting control-c
normally.

-linda


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -