From 117371bafb22da03a19bf5c774523d96a14c2a67 Mon Sep 17 00:00:00 2001 From: PlexSheep Date: Wed, 21 Feb 2024 23:05:33 +0100 Subject: [PATCH] fancier readme --- README.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/README.md b/README.md index 33ccbfd..f6a23f1 100644 --- a/README.md +++ b/README.md @@ -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