PlexSheep/seep
1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages 1 Wiki Activity Actions

fancier readme
All checks were successful
cargo devel CI / cargo CI (push) Successful in 30s
Details

Browse source
This commit is contained in:
Christoph J. Scherr 2024-02-21 23:05:33 +01:00
parent e80f2cd2d0
commit 117371bafb
No known key found for this signature in database
GPG key ID: 7CDD0B14851A08EF
1 changed files with 12 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

12
README.md
View file

@ -1,10 +1,22 @@
# seep
![Project badge](https://img.shields.io/badge/language-Rust-blue.svg)
![Crates.io License](https://img.shields.io/crates/l/seep)
![Gitea Release](https://img.shields.io/gitea/v/release/PlexSheep/seep?gitea_url=https%3A%2F%2Fgit.cscherr.de)
![Gitea language count](https://img.shields.io/gitea/languages/count/PlexSheep/seep?gitea_url=https%3A%2F%2Fgit.cscherr.de)
[![cargo checks and tests](https://github.com/PlexSheep/seep/actions/workflows/cargo.yaml/badge.svg)](https://github.com/PlexSheep/seep/actions/workflows/cargo.yaml)
Print `stdin` to terminal, then pipe into next process.
`seep` (short for see pipe and also to describe leaks in real pipes) has the
purpose of letting you peek at what you're piping.
* [Original Repository](https://git.cscherr.de/PlexSheep/seep)
* [GitHub Mirror](https://github.com/PlexSheep/seep)
* [crates.io](https://crates.io/crates/seep)
* [docs.rs](https://docs.rs/crate/seep/)
## Usage
On Unix like systems, you can pass the output (`stdout`) of one process to the