Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!seismo!husc6!cmcl2!brl-adm!brl-smoke!gwyn From: gwyn@brl-smoke.ARPA (Doug Gwyn ) Newsgroups: comp.unix.questions Subject: Re: ksh question Message-ID: <6112@brl-smoke.ARPA> Date: Sun, 12-Jul-87 17:20:12 EDT Article-I.D.: brl-smok.6112 Posted: Sun Jul 12 17:20:12 1987 Date-Received: Mon, 13-Jul-87 04:57:21 EDT References: <190@ttrdd.UUCP> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB)) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 16 Keywords: noclobber In article <190@ttrdd.UUCP> mellman@ttrdd.UUCP (Thomas Mellman) writes: >How do people in the ksh world do without noclobber? Noclobber is not a general solution. Like many other Berkeleyisms, it helps human users who work in accordance with its usage model but gets in the way of others. I for one do not WANT this feature. Perhaps it is wise to develop the habit of pausing to review each command before typing RETURN. >But sometimes I forget to put the second > at the end of my cat > calendar ... >Isn't there something I can do? Sure. Set up a bunch of shell functions for all the things like this that you frequently do; once you have them debugged you'll not have any problems remembering just what to type at the shell syntax level -- you'll be using a single mnemonic word to invoke the entire function.