Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn From: gwyn@brl-smoke.ARPA (Doug Gwyn ) Newsgroups: comp.unix.wizards Subject: Re: globbing in the shell Message-ID: <6787@brl-smoke.ARPA> Date: Fri, 4-Dec-87 12:35:06 EST Article-I.D.: brl-smok.6787 Posted: Fri Dec 4 12:35:06 1987 Date-Received: Wed, 9-Dec-87 03:53:40 EST References: <1257@boulder.Colorado.EDU> <6840002@hpcllmv.HP.COM> <9555@mimsy.UUCP> <890@russell.STANFORD.EDU> <9610@mimsy.UUCP> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB)) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 16 In article <9610@mimsy.UUCP> chris@mimsy.UUCP (Chris Torek) writes: > Yes master? rm a.out core *.o *.s * .i >would run `rm' with > "CMDLINE=rm a.out core *.o *.s *\t.i" >in its environment. What about rm `find . -name '*.o' -print` That wouldn't do a hell of a lot of good in CMDLINE. If you argue then that the "expanded" command line should be in CMDLINE, well, how does that differ from the argv array? Nope, the UNIX shell approach does this right. "User-friendly" interfaces can do what they want; as I've said before, it is unwise to try to make the UNIX shell environment into a naive-user interface.