Re: Interrupts in xterm windows

Article View: comp.windows.x

Article #24969

#24969

From: chris
Date: Sun, 22 Feb 1987 19:56

9 lines
965 bytes

Ed,

  That fix (reseting SIGINT and SIGQUIT) belongs in xterm, not uwm.  You don't
want random processes started by uwm to start catching ^C's in the window uwm
was started in (if it was started from an xterm window), but you do want xterm
shells to work regardless of whether the user has hacked on their copy of uwm,
right?  The Korn shell exhibits the same problem as /bin/sh does.

							Chris

Technical Details

Message-ID: <8702221956.AA13915@columbia.edu>

Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!COLUMBIA.EDU!chris

References: <2584@jade.BERKELEY.EDU>

Show Full Headers

Complete Article Headers

Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: arc1-ca.pugleaf.net!utzoo!utgpu!water!watnot!watmath!clyde!cbatt!ucbvax!COLUMBIA.EDU!chris
From: chris@COLUMBIA.EDU.UUCP
Newsgroups: comp.windows.x
Subject: Re: Interrupts in xterm windows
Message-ID: <8702221956.AA13915@columbia.edu>
Date: Sun, 22-Feb-87 14:56:08 EST
Article-I.D.: columbia.8702221956.AA13915
Posted: Sun Feb 22 14:56:08 1987
Date-Received: Wed, 25-Feb-87 06:40:15 EST
References: <2584@jade.BERKELEY.EDU>
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 9

Reply to Parent Message