From 58105c6f9d0bd07e3c59fec2b2cf5846443eafc9 Mon Sep 17 00:00:00 2001 From: "Christoph J. Scherr" Date: Wed, 21 Feb 2024 16:26:57 +0100 Subject: [PATCH] readme --- README.md | 24 +++++++++++++++++++++++- 1 file changed, 23 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 947e0a1..0db8efd 100644 --- a/README.md +++ b/README.md @@ -1,3 +1,25 @@ # seep -print stdin to terminal, then pipe into next process +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: + +```bash +ls | seep | grep src +``` +(list files and dirs, show all with `seep`, show only containing "src")