print stdin to terminal, then pipe into next process
Go to file
Christoph J. Scherr 58105c6f9d
cargo devel CI / cargo CI (push) Successful in 25s Details
readme
2024-02-21 16:26:57 +01:00
.gitea/workflows it works 2024-02-21 13:06:09 +01:00
.github/workflows it works 2024-02-21 13:06:09 +01:00
scripts add template for rust 2024-02-21 12:21:57 +01:00
src append newline to tty when done 2024-02-21 14:47:32 +01:00
.gitignore it works 2024-02-21 13:06:09 +01:00
Cargo.toml it works now 2024-02-21 14:09:46 +01:00
LICENSE add template for rust 2024-02-21 12:21:57 +01:00
README.md readme 2024-02-21 16:26:57 +01:00

README.md

seep

Print stdin to terminal, then pipe into next process.

seep (short for see pipe) has the purpose of letting you peek at what you're piping.

Usage

On Unix like systems, you can pass the output (stdout) of one process to the other as input, like this: echo "foo" | hexdump. In some cases, the output of the first command might contain information that a user might want to look at.

When the second process does not show the information it received, the user cannot see the information produced by the first program. This is where seep comes useful:

To look at the output of process one, we pipe it to seep and then pipe the output of seep to process two. seep will show us what information it receives and pass it over to process two:

ls | seep | grep src

(list files and dirs, show all with seep, show only containing "src")