Xref: utzoo comp.arch:21177 comp.os.misc:1611 Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!lavaca.uh.edu!menudo.uh.edu!sugar!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.arch,comp.os.misc Subject: Re: shell architecture (to glob or not to glob) Message-ID: <0IS9YFC@xds13.ferranti.com> Date: 28 Feb 91 16:27:52 GMT References: <1991Jan14.013815.11419@ims.alaska.edu> <11314@lanl.gov> Followup-To: comp.os.misc Organization: Xenix Support, FICC Lines: 15 In article , kenw@skyler.arc.ab.ca (Ken Wallewein) writes: > As a trivil but amusing example, the other day I had a file whose name > started with '-'. There was no way to tell programs which expects shell > globbing that "this is not a command option; this is a filename". command options-and-arguments -- filenames-only If the command wasn't written to support this syntax, blame that particular program: this has been a standard for years. There are badly written programs in program-does-globbing systems too. -- Peter da Silva. `-_-' peter@ferranti.com +1 713 274 5180. 'U` "Have you hugged your wolf today?" Making programs do globbing is like making them handle expose events.