3 ms·
I've long wanted easy, trivial multichannel i/o with duplication I want to be able to route x independent input and y independent output trivially from the ter
by kristopolous 8mo ago
I've long wanted easy, trivial multichannel i/o with duplication
I want to be able to route x independent input and y independent output trivially from the terminal
Proper i/o routing
It shouldn't be hard, it shouldn't be unsolved, and it shouldn't be esoteric
- bmicraft 8mo agoThat's what named pipes do.
- direwolf20 8mo agoThey don't. They're single reader and, if I remember correctly, sequential single writer.
- kristopolous 8mo agoSome kind of elegant unixy syntax would be nice [ ... Inputs ] | command | [ ... Outputs ] Basically select(1) as a cli syntax. I've done quite a bit of unix historical work ... Not enough for a talk at the CHM but decent enough that I have interviewed dozens of people. I really think some basic stuff was just left in a hacky state and we never revisited the primitives right. I've been trying to do that in my own projects For instance I should be able to do something like Command || processor And not have processor hijack the input without hacky pty stuff. I am intentionally using || here. There's lots of use cases to this: llms are the best, logging, rendering text, readline, translation, accessibility, it'd be a very useful primitive and it's impossible to do without a full pty wrapper or some kind of voodoo heuristic wrangling. Currently you have to do things like this https://github.com/day50-dev/ESChatch/blob/main/eschatch.py#L245 https://github.com/day50-dev/ESChatch/blob/main/eschatch.py#... It should be easy I know that some esoteric shells do it but I want everything to be traditional with better i/o features