Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!elroy.jpl.nasa.gov!usc!wuarchive!wuphys!petcher
From: petcher@wuphys.wustl.edu (Donald N. Petcher)
Newsgroups: comp.sys.next
Subject: unwanted Terminal shutdown
Message-ID: <1991Feb22.004254.11244@wuphys.wustl.edu>
Date: 22 Feb 91 00:42:54 GMT
References: <3448@gmuvax2.gmu.edu> <1991Feb13.080815.19892@evax.arl.utexas.edu> <SCOTT.91Feb13155857@erick.gac.edu> <1991Feb14.070958.12057@evax.arl.utexas.edu>
Reply-To: petcher@wuphys.UUCP (Donald N. Petcher)
Organization: Physics Dept, Washington U. in St Louis
Lines: 18

I recently got a NeXT slab for my daily workstation, and I must say 
I have been very pleased in general.  However there is one annoying 
thing about which I would like to ask about a way to prevent.  
The generic way of exiting a program is to use Command-q.  Since I 
primarily work in csh running under Terminal, I use this normally when I 
jump out to look something up in the manual or so.  However, 
occasionally I don't notice that the Terminal program is the 'current' 
program (meaning the one governed by the active menu - I haven't yet 
learned 'NeXTese' so I don't know if this is correct parlance) and I hit 
Command-q intending to close up some other program, and ALL MY csh 
PROCESSES GET KILLED without so much as an inquiry.  Is there a flag to 
set that at least allows this to be vetoed when I make a mistake? It has 
happened a little too often to be just annoying.

thanks,
Don Petcher
petcher@wuphys.wustl.edu
petcher@ebenezer.wustl.edu


Brought to you by Super Global Mega Corp .com