Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!sdd.hp.com!uakari.primate.wisc.edu!dali.cs.montana.edu!milton!uw-beaver!cornell!rochester!pt.cs.cmu.edu!zardoz.club.cc.cmu.edu!ddj From: ddj@zardoz.club.cc.cmu.edu (Doug DeJulio) Newsgroups: comp.sys.next Subject: Re: unwanted Terminal shutdown Summary: easy fix with NIB files Keywords: Terminal nib Message-ID: <12075@pt.cs.cmu.edu> Date: 24 Feb 91 04:58:58 GMT References: <1991Feb14.070958.12057@evax.arl.utexas.edu> <1991Feb22.004254.11244@wuphys.wustl.edu> Organization: Castle Anthrax, Pittsburgh Lines: 20 In article <1991Feb22.004254.11244@wuphys.wustl.edu> petcher@wuphys.UUCP (Donald N. Petcher) writes: >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. My solution was to use one of the many NIB file extracting/combining tools to make a new version of terminal (/LocalApps/MyTerm on my machine), and just remove the little 'q' from the quit option in the main menu. Works like a charm. -- DdJ ddj@zardoz.club.cc.cmu.edu Brought to you by Super Global Mega Corp .com