Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!cbatt!cbosgd!ihnp4!inuxc!pur-ee!uiucdcs!convex!ndm20!lvs
From: lvs@ndm20
Newsgroups: net.unix-wizards
Subject: Re: Problem with csh;request for fix (L
Message-ID: <28800007@ndm20>
Date: Thu, 10-Jul-86 15:54:00 EDT
Article-I.D.: ndm20.28800007
Posted: Thu Jul 10 15:54:00 1986
Date-Received: Sat, 12-Jul-86 07:11:08 EDT
References: <405@chinet.UUCP>
Lines: 31
Nf-ID: #R:chinet.UUCP:405:ndm20:28800007:37777777600:1044
Nf-From: ndm20!lvs    Jul 10 14:54:00 1986



> seems that csh can't deal with variable assignment when the value to assign
> to the variable has the meta characters [] or {} in it. However it seems
> that the bourne shell has no problems with it.  Reproduce with the following
> transcript of a csh session. My own comments are in ()'s and are not
> part of the xscript:
> [ various examples followed... ]

It's not a bug, it's a feature :-).  The c-shell does process the strings
for filename expansion, not when they are assigned, but when they are used
in a later expression, ie. echo.  The way to inhibit this activity is to use
the command
 
     set noglob

This will inhibit the c-shell from expanding filename metachars in your data.
To reenable the expansion, use

     unset noglob

That should be all you need.

Hope this helps,
Larry V. Streepy Jr.                        "Waiting is"
Nathan D. Maier Consulting Engineers

VOICE:  (214)739-4741
Usenet: {seismo!c1east | cbosgd!sun | ihnp4}!convex!infoswx!ndm20!lvs
CSNET:  ndm20!lvs@smu
ARPA:   ndm20!lvs%smu@csnet-relay.ARPA