Discussion
@stibbons @djsundog Actual design request can the length of shell symbols correspond somewhat to how weakly they bind?
Like in particular, since pipes bind uniformally less strongly than path dividers, can they be a pair of characters? Like ` // ` rather than ` / `. (Or whatever character.) Especially since pipes don't repeat sequentially.
@djsundog @stibbons I think a simple goal is something like, to count votes and spit out any non-vote comments:
(This'll still have a lot of sh-isms, sorry. Mod out by those.)
```
cat votes.txt | teegrep -e:[yespipe] "^[Yy]" -e:[nopipe] "^[Nn]" -e:[commentpipe] "^." |:[teegrep]
[teegrep]:[yespipe]:| wc -l | prepend "Yes: "
[teegrep]:[nopipe]:| wc -l | prepend "No: "
[teegrep]:[commentpipe]:| colorline -c "yellow"
```
Install bonfire.cafe
Get the full app experience
@stibbons @djsundog EDIT:
Actually wait, new idea, what if there's some way to use "\" for this, with the idea that that's a shorthand for "1\1", that is, modding out fd1 from the first process and replacing it with fd1 from the second process.
So like a more complicated arrangement could be
"procA 1\3 2\1 2\2 procB", mapping a handful of things in a circle.
... I still don't like this. I want some better way of tossing ahead and picking up multiple output streams into, like, a non-trivial graph of different fd#s from the same process going to different processes.