Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!helios!mtecv2!al158305
From: al158305@mtecv2.mty.itesm.mx (Gustavo Cordova Avila)
Newsgroups: comp.sys.amiga.tech
Subject: Re: PIPEs
Message-ID: <2641@mtecv2.mty.itesm.mx>
Date: 6 Nov 90 22:45:04 GMT
References: <1990Nov4.072423.408@agate.berkeley.edu> <1990Nov4.150403.28982@cbnewsc.att.com> <6990@sugar.hackercorp.com>
Organization: Instituto Tecnologico y de Estudios Superiores de Monterrey
Lines: 34

peter@sugar.hackercorp.com (Peter da Silva) writes:

>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?

   Well, then it doesn't expand! I'm using csh4.02a (I think), and if you
put something in quotes it doesn't do anything to it, it gets passed as-is,
and until now, I prefer it over any other shell, being it C= standard shell
(1.3), ash, ksh, etc. Nothing beaten it yet.

   And what's this about using + for piping comands?? Don't you know that
that's the char for indicating that the next is a command (in run's case)
or more arguments...
   '->'??? It's easier to type only one char, and by custom it's always
been '|'. Then again, I'm an old fashion guy, I remember when '=' was used
for renaming! (remember cp/m? :)

   Well, gotta go...

cu@the.mouse
-- 
************************** Gustavo Cordova Avila ***************************
* al158305@mtecv2.mty.itesm.mx      | Majoring in Electronics Systems Eng. *
* pl158305@tecmtyvm.mty.itesm.mx    | in Monterrey Tech, Mexico.           *
****************************************************************************