Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Posting-Version: version B 2.10.2 9/18/84; site brl-tgr.ARPA Path: utzoo!watmath!clyde!bonnie!akgua!sdcsvax!sdcrdcf!hplabs!hao!seismo!brl-tgr!tgr!Doug Gwyn (VLD/VMB)From: Doug Gwyn (VLD/VMB) Newsgroups: net.unix-wizards Subject: Re: Survey on use of \";\" \"&&\" \"||\" to separate shell commands. Message-ID: <6400@brl-tgr.ARPA> Date: Thu, 6-Dec-84 14:47:08 EST Article-I.D.: brl-tgr.6400 Posted: Thu Dec 6 14:47:08 1984 Date-Received: Sun, 9-Dec-84 03:26:58 EST Sender: news@brl-tgr.ARPA Organization: Ballistic Research Lab Lines: 5 I use && and || a lot. I NEVER expect any command to fail except via a nonzero exit code. Any significant task I do with a shell script, and if signals etc. matter then I intercept them. Things like "a && (b ; c)" work very nicely but one rarely requires them. I think too much ado is being made over this issue.