Path: utzoo!utgpu!watserv1!watmath!att!att!emory!swrinde!elroy.jpl.nasa.gov!ncar!midway!msuinfo!convex.cl.msu.edu!jap
From: jap@convex.cl.msu.edu (Joe Porkka)
Newsgroups: comp.sys.amiga.tech
Subject: Re: Wildcard types
Message-ID: <1990Nov16.234820.14783@msuinfo.cl.msu.edu>
Date: 16 Nov 90 23:48:20 GMT
References: <15517@cbmvax.commodore.com> <2439@trlluna.trl.oz> <15620@cbmvax.commodore.com> <1990Nov16.171451.5668@gtisqr.uucp>
Sender: news@msuinfo.cl.msu.edu
Organization: Michigan State University
Lines: 24

rick@gtisqr.uucp (Hendrik Groeneveld) writes:

>In article <15620@cbmvax.commodore.com> andy@cbmvax.commodore.com (Andy Finkel) writes:
>>In article <2439@trlluna.trl.oz> aduncan@rhea.trl.oz (Allan Duncan) writes:


>Adding wildcard expansion as a DOS call is an improvement, but
>expansion is the shells job. If I don't want somthing expanded
>by the shell, I'll quote it. IMHO, if the shell doesn't do wildcard
>expansion, it's a *bug*, not a feature. :-(

What happens when your wildcard matches 5000 files? makes for an
awful LONG command line. (/bin/csh in UNIX simply complains
about line to long and aborts)

What do you do when you want to match * */* */*/* ..... without
knowing how deep you need to go? (this can be fixed by doing something
like */.../* I suppose - but it aint done now).

If the command does it, it can interpret the ALL keyword.

In general its better for the command to handle expansion since it
"knows" which args are filenames. If you don't like it then
you are free to use a different shell.