🚀 go-pugleaf

In article <1990Nov4.195838.25540@ux1.cso.uiuc.edu> lrg7030@uxa.cso.uiuc.edu (Loren  Rittle) writes:
+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...

Making the idiot user include whitespace or not seems to be an awkward way of
handling it, to me.  How do I remember if I should throw a space in, of if it
isn't allowed?  Just be a little flexible, come up wita a new symbol for
pipes (c'mon, guys... `->' is the way to go...), and stick with it.  Seems to
me that in any `modern' command-line interface, enforcing the amount of
whitespace between tokens is clumsy ("In columns 1-10 appear the command
name.  Column 12 contains the optional redirection symbol `<'.  If
present...")

+Loren J. Rittle

ken
-- 
     Ken Yarnall                 ///   yarnall@usceast.cs.scarolina.EDU
      Math Department, USC   \\\///   yarnall@ucseast.UUCP
       Columbia, S.C. 29208   \\\/   (803)777-5218
    `You'd better tie me up.' -- from the movie, "Tie Me Up, Tie Me Down"