shame on me, I didn't know about it.
2009/10/1, matt :
> Tee part of the POSIX standard
>
> http://www.opengroup.org/onlinepubs/9699919799/utilities/tee.html
>
>
>
> hugo rivera wrote:
>
>
> > Great, thanks.
> > Looks like plan 9 guys have thought about everything useful ☺ (and
> > that I didn't
Tee part of the POSIX standard
http://www.opengroup.org/onlinepubs/9699919799/utilities/tee.html
hugo rivera wrote:
Great, thanks.
Looks like plan 9 guys have thought about everything useful ☺ (and
that I didn't do my homework).
2009/10/1, roger peppe :
2009/10/1 hugo rivera :
I'v
Great, thanks.
Looks like plan 9 guys have thought about everything useful ☺ (and
that I didn't do my homework).
2009/10/1, roger peppe :
> 2009/10/1 hugo rivera :
>
> > I've been wondering for a while if there's some way to multiplex (if
> > this is the correct term) stdout for a given program:
> I've been wondering for a while if there's some way to multiplex (if
> this is the correct term) stdout for a given program:
> % ls @ {grep regexp1 > file1 } @ {grep regexp2 > file2}
ls | tee >{grep regexp1 >file1} | grep regexp2 >file2
I'd like to make a "graphical shell" which could do this sort of thing, it
would also have a textual format for saving and suitable for editing.
I think it would be good to have an equivalent graphical tool for each command
line tool, as powerful as the original one; and an editable graphical
repr
2009/10/1 hugo rivera :
> I've been wondering for a while if there's some way to multiplex (if
> this is the correct term) stdout for a given program:
that's what tee does.
e.g.
ls | tee >{grep regexp1 > file1} >{grep regexp2 > file2}
