🚀 go-pugleaf

In article <910784101snz@wash.demon.co.uk>, John Washington
<john$@wash.demon.co.uk> writes
[snip]
>I constantly find myself typing things like:
>
>        grep foobar *.c
>        [pause to eyeball result]
>        edit thisfile.c thatfile.c tother.c yafile.c etc.c
>
>And that really bugs me.  The damn computer knows which files
>I want already.  I could even have used the -l option in grep
>to get a little list of them.
It knew the files which measured up before you threw the information
away. tee may be useful. Unfortunately, doze does not have a true pipe
capability. e.g. command1 | command2 is roughly equivalent to
command1 > tmpfile
command2 < tmpfile
del        tmpfile

Consequence is that none of the results of command2 comes out before
command 1 finishes. 
[snip]

In Unix, I solve such problems with a script which takes arguments of a
searchstring and a filespec. find generates filelist; grep -l filters
it; $VISUAL (elvis, vim or vi) edits each file in turn. It took me ages
to appreciate I REALLY needed such a tool. It might be possible to right
your own piping code to exchange the problems with gates code for your
own.
-- 
Walter Briscoe