Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!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: PIPEs Message-ID: <6990@sugar.hackercorp.com> Date: 5 Nov 90 13:14:52 GMT References: <1990Nov4.072423.408@agate.berkeley.edu> <1990Nov4.150403.28982@cbnewsc.att.com> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 19 In article <1990Nov4.150403.28982@cbnewsc.att.com> gregg@cbnewsc.att.com (gregg.g.wonderly) writes: > I find the UN*X shells' quoting conventions to be quite adequate at > avoiding the need to require a SPACE anywhere. If you want something which > contains meta characters to become part of a parameter-word, you quote it. The problem is that in this case you have two sets of metacharacters conflicting at the shell level. Think about the following: list lformat=%s #?.c|#?.h | zoo ... Now if you quote that: list lformat=%s "#?.c|#?.h" | zoo ... How does list know whether to expand it or not? What if you're using a shell that does expansion? -- Peter da Silva. `-_-' .