Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!think.com!barmar
From: barmar@think.com (Barry Margolin)
Newsgroups: comp.misc
Subject: Re: [] in Unix filenames
Message-ID: <1990Sep19.185857.23483@Think.COM>
Date: 19 Sep 90 18:58:57 GMT
References: <9009191420.AA10971@thep.lu.se>
Sender: news@Think.COM
Organization: Thinking Machines Corporation, Cambridge MA, USA
Lines: 21

In article <9009191420.AA10971@thep.lu.se> magnus@THEP.LU.SE (Magnus Olsson) writes:
>Is there really no way of telling the shell that I mean
>"all files that start with a [, followed by an arbitrary string,
>followed by a ], etc? Or is this a bug in the shell (we're using
>newcsh)?

I just created such a file, and then did:

	echo \[*\]*

in /bin/csh on a Sun-4 running SunOS 4.0.3 and it worked fine.

The problem may not be in the shell, but in the mved script.  I'm guessing
it replaces the "=" with "*" in order to find all the matching files; if it
doesn't requote the "[" and "]" then it will lose.

--
Barry Margolin, Thinking Machines Corp.

barmar@think.com
{uunet,harvard}!think!barmar