Re: why does control-4 generate SIGQUIT in X?

To: debian-user@lists.debian.org
Subject: Re: why does control-4 generate SIGQUIT in X?
From: Chris Davies <chris-usenet@roaima.co.uk>
Date: Thu, 24 May 2012 15:59:45 +0100
Message-id: <[🔎] 10v199x2pt.ln2@news.roaima.co.uk>
Reply-to: chris@roaima.co.uk
References: <[🔎] 20120521222855.GA14666@localhost> <[🔎] jpgiiq$isf$16@dough.gmane.org> <[🔎] 20120522194214.GF1583@tal> <[🔎] enet89x4r6.ln2@news.roaima.co.uk> <[🔎] 20120523160520.GA2523@tal>

Chris Bannister <cbannister@slingshot.co.nz> wrote:
> start an xterm, type 
> stty quit ""<return>
> stty -a shows quit as "<UNDEF>"

Exactly my point. So ^\ no longer works at all (in that xterm).
Chris

Reply to:

References:
- why does control-4 generate SIGQUIT in X?
  - From: Eric Cooper <ecc@cmu.edu>
- Re: why does control-4 generate SIGQUIT in X?
  - From: Camaleón <noelamac@gmail.com>
- Re: why does control-4 generate SIGQUIT in X?
  - From: Chris Bannister <cbannister@slingshot.co.nz>
- Re: why does control-4 generate SIGQUIT in X?
  - From: Chris Davies <chris-usenet@roaima.co.uk>
- Re: why does control-4 generate SIGQUIT in X?
  - From: Chris Bannister <cbannister@slingshot.co.nz>

Prev by Date: Re: ssh error - Write failed: Broken pipe
Next by Date: Re: wheezy: non-free latex fonts no longer work
Previous by thread: Re: why does control-4 generate SIGQUIT in X?
Next by thread: Kernel Oops when closing the lid on Dell XPS 14z
Index(es):
- Date
- Thread