Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!mips!apple!bionet!parc!news
From: Lovstrand@EuroPARC.Xerox.COM (Lennart Lovstrand)
Newsgroups: comp.sys.next
Subject: Disabling cmd-q in Terminal
Message-ID: <1991Jun2.235028.21517@parc.xerox.com>
Date: 2 Jun 91 23:50:28 GMT
Sender: news@parc.xerox.com
Organization: Rank Xerox EuroPARC, Cambridge, UK
Lines: 24

$&#(@&%#!  I just managed to nuke all my Terminal windows again for
the umpteenth time by accidently hitting cmd-q with the wrong input
focus.  It's incredibly how easy it can happen when switching between
development work in a terminal window and test running a new app.
Boom, there went all my remote login sessions and random stopped jobs!

So... Anyone know how to disable cmd-q in Terminal -- preferrably, but
not necessarily, without patching the app?  Wouldn't mind getting rid
of cmd-w at the same time.  At second best (and for possible future
releases), a way of persuading Terminal to ask for confirmation before
closing a window with a live shell would be a real win.

OS 2.1, /NextApps/Terminal dated 30 Oct 1990

Feel free to suggest "use Stuart instead" if that will make me happier.
(Or "tie lead around your fingers", although not quite so appreciated.)

Thanks,
--Lennart (don't read me wrong, I really do love my NeXT box, seriously)
--
--Lennart <Lovstrand@EuroPARC.Xerox.COM>		R   _A _  N_   K
Rank Xerox EuroPARC, 61 Regent St, Cambridge, UK	\/ |_ |_) | | \/
Heart-of-Gold, NeXTcube at EuroPARC, NeXT Mach 2(1)	/\ |_ | \ |_| /\
TOPS-20 Command processor 7(109)-8 [alpha]		E u r o  P A R C