Hi, 18.07.2026 23:57:18 umbraticus via 9fans <[email protected]>:
>> Extending the current capabilities only >> slightly, one could have a cascade of plumbers. > > Again, pretty sure the capabilities are already there. > > data matches passmeon > plumb start rc plumb -p /mnt/luigi/send -w $wdir $data > > It would be nice to be able to > > bind /mnt/plumb/mario /mnt/luigi/send > > but invoking plumb(1) is probably good enough. > > If you want interactive plumbing you could write something > that listens on a port and when it gets a plumb message > raises its window and prompts for how to redirect. > Seems to defeat the point to me, but not the first time > the desire for this kind of thing has been expressed. Turns out, I built something like that some time ago when I did more image editing and added the imageedit channel: http://shithub.us/sirjofri/plumbto/HEAD/info.html This tool does not forward to a different plumber though, only to different channels of the same plumber. > Could probably also do stuff with src and attr to achieve > certain ends. Slightly offtopic, but related: I built a small notification system around the plumber, that allows you to plumb a notification to the notify channel that may contain another plumb message. Imagine a longer process (e.g. rendering a video) that finishes and pushes a notification. The notification program lists that notification, and you can interact with it. Then, the payload plumb message is fed back into the plumber, which could cause that video to open. Link: http://shithub.us/sirjofri/notif/HEAD/info.html Note that I didn't use both tools in a while, so there could be some bitrot. sirjofri ------------------------------------------ 9fans: 9fans Permalink: https://9fans.topicbox.com/groups/9fans/Tc15b39be3656afe0-Mb1bc219ad4ac289f97b5e875 Delivery options: https://9fans.topicbox.com/groups/9fans/subscription
