Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!usc!julius.cs.uiuc.edu!ux1.cso.uiuc.edu!uxa.cso.uiuc.edu!lrg7030
From: lrg7030@uxa.cso.uiuc.edu (Loren  Rittle)
Newsgroups: comp.sys.amiga.tech
Subject: Re: PIPEs
Message-ID: <1990Nov4.195838.25540@ux1.cso.uiuc.edu>
Date: 4 Nov 90 19:58:38 GMT
References: <53407.657565922@atronx.UUCP> <1990Nov3.073201.8227@agate.berkeley.edu> <6977@sugar.hackercorp.com>
Sender: news@ux1.cso.uiuc.edu (News)
Organization: University of Illinois at Urbana
Lines: 16

Peter da Silva writes:
> The version 6 shell and the version 7 (bourne) shell use either '|' or '^'
> as a pipe character. I understand that at least one Amiga shell requires
> pipes to have white-space around them. The use of '^' might be a better
> alternative, even if it will break c-shell history (which is something
> I want, weird though that might sound to some of you).

The shell of which you speak is the WShell v1.2 (highly recommended :-).
It does indeed ``force'' you to have white-space on the leading edge of
the pipe symbol, which defaults to `|', but can be changed via the
WShell-config file to be any symbol you desire.  Because Bill enforces
the white-space before pipe symbol rule in the WShell, there is no 
way it could be mixed up with AmigaOS pattern matching.
Have your burger, your way, some might say...

Loren J. Rittle