Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!uunet!cbmvax!jesup From: jesup@cbmvax.commodore.com (Randell Jesup) Newsgroups: comp.arch Subject: Re: shell architecture (to glob or not to glob) Message-ID: <19062@cbmvax.commodore.com> Date: 18 Feb 91 04:33:09 GMT References: <1991Jan14.013815.11419@ims.alaska.edu> <11314@lanl.gov> <5340@idunno.Princeton.EDU> <1991Jan14.170115.17178@Think.COM> <360@bria> <1991Jan17.185527.9824@Neon.Stanford.EDU> <365@bria> <378@bria> Sender: Reply-To: jesup@cbmvax.commodore.com (Randell Jesup) Followup-To: Distribution: Organization: Commodore, West Chester, PA Keywords: In article kenw@skyler.arc.ab.ca (Ken Wallewein) writes: > Ever notice that all Unix commands that support globbing only allow it at >the end of the command, and only allow one (possibly list) argument to be >globbed? That's why you can't say > > mv here/* there/* The classic problem with shell-provided globbing (and causes you to have to use escapes to avoid the shell globbing things that aren't filenames). If you have a richer expression space (ala regexp), you end up having to do a LOT of quoting. -- Randell Jesup, Keeper of AmigaDos, Commodore Engineering. {uunet|rutgers}!cbmvax!jesup, jesup@cbmvax.commodore.com BIX: rjesup The compiler runs Like a swift-flowing river I wait in silence. (From "The Zen of Programming") ;-)