Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!princeton!caip!lll-crg!seismo!ut-sally!utah-cs!utah-gr!thomas
From: thomas@utah-gr.UUCP (Spencer W. Thomas)
Newsgroups: net.unix
Subject: Re: sh, csh, and special execution environments
Message-ID: <1741@utah-gr.UUCP>
Date: Fri, 13-Jun-86 09:15:07 EDT
Article-I.D.: utah-gr.1741
Posted: Fri Jun 13 09:15:07 1986
Date-Received: Tue, 17-Jun-86 07:46:49 EDT
References: <931@uwvax.UUCP> <1913@osu-eddie.UUCP> <143@prairie.UUCP> <107@ora.UUCP> <941@uwvax.UUCP> <1220@ncoast.UUCP>
Reply-To: thomas@utah-gr.UUCP (Spencer W. Thomas)
Organization: University of Utah CS Dept
Lines: 18

In article <1220@ncoast.UUCP> allbery@ncoast.UUCP (Brandon Allbery) writes:
>Quoted from <941@uwvax.UUCP> ["Re: Gripes about /bin/sh AND /bin/csh"], by pfeiffer@uwvax.UUCP...
>+---------------
>| I have given up on creating "executable variables" in a form acceptable to both
>| rsh AND csh.  
>+---------------
>Advice:  Give up.  sh and csh just ain't compatible.

You missed.  Since when does rsh use sh?  It has always used csh for
me.  The problem that pfeiffer was complaining about has to do with
quoting variable expansions so that they occur properly whether the
command is being run remotely or locally.  You have to supply an extra
level of quoting for remote commands (to deal with remote file expansion
&c).  This is especially nasty if you have `!'s in your string
somewhere.

-- 
=Spencer   ({ihnp4,decvax}!utah-cs!thomas, thomas@utah-cs.ARPA)