🚀 go-pugleaf

In  <7054@sugar.hackercorp.com> (16 Nov),
Peter da Silva (peter@sugar.hackercorp.com) writes:
> In article <ben.3416@epmooch.UUCP> ben@epmooch.UUCP (Rev. Ben A. Mesander) writes:
|>  One more thing I'd like to inject into the pipe discussion is that the '+'
|>  mechanism is not unique to the 'run' command. [....]
>
> A good question, I hope, since I have RTFM and I still can't figure it out...
>
> How do you access the stuff the user types in after the +?

...and in  <36574@nigel.ee.udel.edu> (16 Nov),
Darren New (new@ee.udel.edu) replies:
>
> If I remember properly, you have to look directly at the command line,
> and the plusses are replaced by newlines of some sort (\r, \n, or whatever).
> That is, in Lattice you need to use _main instead of main. My machine is
> down right now, or I would double check this.    -- Darren

I did check, and that's right: with (Lattice) _main you get the COMPLETE
command input (minus the plusses, but plus the commandname itself).

On the same lines, I thought it would be cute to try for a prototype "PIPE"
command in ARexx.  Sure enough, if you do "parse args argin"/"say argin",
you nicely get the complete input text.

One problem... ARexx seems to have no concept of newlines!  I can find NO
way to parse argin into single lines.  Anyone know of one?

                                            -- Pete --