Path: utzoo!utgpu!watserv1!watmath!att!att!emory!swrinde!zaphod.mps.ohio-state.edu!ub!uhura.cc.rochester.edu!rochester!kodak!uupsi!njin!limonce From: limonce@pilot.njin.net (Tom Limoncelli) Newsgroups: comp.sys.amiga.tech Subject: Re: Wildcard types Message-ID: Date: 16 Nov 90 23:45:10 GMT References: <15517@cbmvax.commodore.com> <2439@trlluna.trl.oz> <15620@cbmvax.commodore.com> <1990Nov16.171451.5668@gtisqr.uucp> Organization: Drew University/NJIN Lines: 40 In article <1990Nov16.171451.5668@gtisqr.uucp> rick@gtisqr.uucp (Hendrik Groeneveld) writes: > Adding wildcard expansion as a DOS call is an improvement, but > expansion is the shell's 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. :-( ...and before someone else posts it: ALL THE WORLD IS NOT UNIX! (SETQ SARCASM-MODE ON) "Hello God?" "Yes my worshiper." "I've found a computer that doesn't do everything exactly like UNIX." "That's horrid! *ZAAAAAP*! There, there. It won't bother you any more." "Thanks." (SETQ SARCASM-MODE OFF) What are you talking about? There is no required place for wildcard expansion. This topic comes up every so often. There benefits and problems with both. For example, you claim that if you don't want something expanded you'll quote it. You've now make everything-in-the-world-except- files into a special case. How dare you assume that most of my commands deal with files. Let's end this topic or take it to alt.religion.computers where it belongs. ALL THE WORLD IS NOT UNIX! ALL THE WORLD IS NOT UNIX! ALL THE WORLD IS NOT UNIX! ALL THE WORLD IS NOT UNIX! ALL THE WORLD IS NOT UNIX! -Tom -- tlimonce@drew.edu Tom Limoncelli "Flash! Flash! I love you! tlimonce@drew.bitnet +1 201 408 5389 ...but we only have fourteen tlimonce@drew.uucp limonce@pilot.njin.net hours to save the earth!"