Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!yale!cmcl2!dasys1!jpr From: jpr@dasys1.uucp (Jean-Pierre Radley) Newsgroups: comp.unix.questions Subject: Re: # not honored? Message-ID: <1990Apr11.213725.9361@dasys1.uucp> Date: 11 Apr 90 21:37:25 GMT References: <3099@auspex.auspex.com> <12465@smoke.BRL.MIL> <3106@auspex.auspex.com> Reply-To: jpr@dasys1.UUCP (Jean-Pierre Radley) Organization: TANGENT Lines: 19 In article <3106@auspex.auspex.com> guy@auspex.auspex.com (Guy Harris) writes: > some of >Larry Wall's scripts open with a command that does one thing on "sh" and >another on "csh", and if it detects it's running under "csh" it >resubmits itself to "sh": >PATH='.:/bin:/usr/bin:/usr/local/bin:/usr/ucb:/usr/local:/usr/lbin:/etc' >export PATH || (echo "OOPS, this isn't sh. Desperation time. I will feed myself to sh."; sh $0; kill $$) Which never worked for me. I use csh most of the time. Both on the Tandy 6000, and in SCO 386 Xenix, it turns out that /bin/csh completey invert the meaning of '&&' and '||'. -- Jean-Pierre Radley jpr@jpradley.uucp New York, NY 72160.1341@compuserve.com