PIPECYCLE(1)

πŸ“¦ version 2024.12.07, in nixpkgs unstable

πŸ’… NAME πŸ’…

okay bestie, this is PIPECYCLE(1) β€” aka The pipecycle program β€” the manual page for pipecycle, which runs all the given commands in parallel via sh -c and loops their pipes around. πŸ’–

✨ SYNOPSIS ✨

pipecycle commandA [commandB ...]

🌸 DESCRIPTION 🌸

pipecycle runs all the commands you pass it in parallel via sh -c. all at once, no cap. ✨

Each command's stdout is connected to a pipe that is read as the next command's stdin. The last command writes to a pipe that is read by the first command. circular pipeline slay. πŸŒ€

pipecycle exits 0 when every command exits 0 (and when it encounters no errors of its own). βœ…

If any command exits nonzero or is killed by a signal, pipecycle exits the same way. If multiple commands exit nonzero or are killed by signals, one of them will be chosen arbitrarily as the exit status to be used. it's not gonna rank them for you, bestie. πŸ™ˆ

⚠️ Exception time: if a command is killed by SIGPIPE after the following command has already exited, that error is ignored. If that is the only error, pipecycle will exit 0; if there are other failures in other commands, one of the other failures will be used for pipecycle's exit status. πŸ’…

β€” source/version: The pipecycle program() Β· date: not listed on this page 🌈🫢

πŸ“¦ where this page comes from