Xref: utzoo comp.unix.questions:32246 comp.unix.shell:2440
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!uunet!unisoft!greywolf
From: greywolf@unisoft.UUCP (The Grey Wolf)
Newsgroups: comp.unix.questions,comp.unix.shell
Subject: Re: Is my shell broken or what?
Message-ID: <3528@unisoft.UUCP>
Date: 18 Jun 91 21:39:01 GMT
References: <1991Jun7.045124.26811@ux1.cso.uiuc.edu> <1991Jun7.115837.8545@mp.cs.niu.edu> <1991Jun7.140828.20332@prl.dec.com>
Reply-To: greywolf@unisoft.UUCP (The Grey Wolf)
Organization: Foo Bar and Grill
Lines: 40

/* <1991Jun7.140828.20332@prl.dec.com> by boyd@prl.dec.com (Boyd Roberts)
 * In article <1991Jun7.115837.8545@mp.cs.niu.edu>, rickert@mp.cs.niu.edu (Neil Rickert) writes:
 * > rickert 2> echo ${test2}
 * > Variable syntax.
 * 
 * Don't you just hate it when the syntax is `variable' :-)

That C shell bug is pretty prevalent -- no version doesn't do that right.
(I could probably hack up a fix, but it'd have to wait for BSD 4.4)...

My shell tells me:
Your variable has an identity crisis.

 * 
 * Avoid C shell, use `rc':
 *

Is rc publicly available?  I seem to remember seeing it fly around...

 *     ; '{([<*>])}2' = stuff

..exCUSE me?

 *     ; echo $'{([<*>])}2'
 *     stuff

Eeyagh.

 *     ;
 * 
 * Variable names?  No problem.
 * 
 * 
 * Boyd Roberts			boyd@prl.dec.com
 * 
 * ``When the going gets wierd, the weird turn pro...''

As is evidenced above by the (ab)use of rc above.

Beats the hell out of any other shell I've seen!