Path: utzoo!utgpu!cunews!bnrgate!bwdls58!bwdlh417!dbscoop2
From: dbscoop2@bwdlh417.BNR.CA (Las Lovas)
Newsgroups: comp.sys.amiga.introduction
Subject: Re: Wildcards in the CLI
Message-ID: <6512@bwdls58.bnr.ca>
Date: 19 Apr 91 13:28:35 GMT
References: <1991Apr16.155231.18782@ux1.cso.uiuc.edu> <7384@munnari.oz.au>
Sender: news@bwdls58.bnr.ca
Reply-To: dbscoop2@bwdlh417.BNR.CA (Las Lovas)
Distribution: world
Organization: Bell-Northern Research Ltd.
Lines: 25

In article <7384@munnari.oz.au>, rjlov@ecr.mu.oz.au (Richard James
LOVEJOY) writes:
|>
|>	In article <1991Apr16.155231.18782@ux1.cso.uiuc.edu>,
grmg6820@uxa.cso.uiuc.edu (Geoffrey R. Mason) writes:
|>> I would like to know what wildcards I can use when opening a new CLI with
|>> the workbench Shell command...  For example, I know that I can use the "?"
|>> as a single character wildcard, but how about a string?  Also, are
there any
|>> PD programs that would allow me to make is so that I could type
something like
|>> 	DELETE *.TXT
|>> to remove all files with extension .txt?
|>
|>	The CLI uses the # to mean "any number of the next character". So 
|>#? means "any number of" "any character". Thus, you can use "delete #?.txt"
|>to remove all files with extension .txt.
            
If you get ARP, you can use the * wildcard.  All the arp commands and
associated library routines understand it.  Under 2.0, you can run a
program called "starburst" which sets some bit which allows the use of
the * wildcard.  The problem stems from the fact that C= (in their
infinite wisdom) decided to use * to refer to the console device
(STDIO), so they had to have a different convention for wildcards than
the "standard" UNIX and (dare I day it...) Messydos conventions.