Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!zaphod.mps.ohio-state.edu!van-bc!
From: lphillips@lpami.wimsey.bc.ca (Larry Phillips)
Newsgroups: comp.sys.amiga.tech
Subject: Re: PIPEs
Message-ID: <2203@lpami.wimsey.bc.ca>
Date: 9 Nov 90 19:49:13 GMT
Lines: 35
Return-Path: <lpami!lphillips>
To: van-bc!rnews

In <1990Nov6.190147.10534@opusc.csd.scarolina.edu>, yarnall@opusc.csd.scarolina.edu (Ken Yarnall) writes:
>
>But, I view the pipe symbol (and others like it) as a separator, too.  I
>realize I'm being picky, here, but I don't see this as an `obvious' place for
>whitespace.
>
>If we use |, and require whitspace, then 
>
>ls -l usr:big/ole/dir|more
>
>and
>
>ls -l usr:big/ole/dir | more
>
>are two completely different fish kettles.  Confusion reigns.  I like
>
>ls -l usr:big/ole/directory->more (which = ls -l usr:big/ole/dir -> more)
>
>much better, and since it builds on previous syntax, I don't think it's
>overkill.

And you don't see using two characters when one would do as overkill? You don't
mind having Yet Another Restriction On Filenames? (yes, I have a few filenames
with '->' in them).

-larry

--
It is not possible to both understand and appreciate Intel CPUs.
    -D.Wolfskill
+-----------------------------------------------------------------------+ 
|   //   Larry Phillips                                                 |
| \X/    lphillips@lpami.wimsey.bc.ca -or- uunet!van-bc!lpami!lphillips |
|        COMPUSERVE: 76703,4322  -or-  76703.4322@compuserve.com        |
+-----------------------------------------------------------------------+