Path: utzoo!utgpu!watserv1!watmath!att!att!linac!pacific.mps.ohio-state.edu!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: Wildcard types Message-ID: <7063@sugar.hackercorp.com> Date: 18 Nov 90 03:16:27 GMT References: <15517@cbmvax.commodore.com> <2439@trlluna.trl.oz> <15620@cbmvax.commodore.com> <1990Nov16.171451.5668@gtisqr.uucp> <1990Nov16.234820.14783@msuinfo.cl.msu.edu> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 17 In article <1990Nov16.234820.14783@msuinfo.cl.msu.edu> jap@convex.cl.msu.edu (Joe Porkka) writes: > 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) That's the fault of the command line passing syntax. > 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). VMS does this with [...]. In that case I use "find". Calling in pipelines isn't cheating. That way I can get all sorts of matching implemented without having to have all the programs support it... -- Peter da Silva. `-_-' .