Pascal Hertleif

More advanced/obscure: - If the tool is meant to be consumed by other tools (instead of/in addition to humans), provide specified, machine readable output (e.g., `--message-formate=json` which prints one JSON...

Two aspects here are what crates to recommend when people look into this, and how to document which signals an app supports. I'll assign this to me but will ping...

Hey, I'm about to write the signal chapter for the book, based on the info in this issue. Thanks again for the great summary, @uazu! The [ctrlc](https://crates.io/crates/ctrlc) crate seems to...

Oh, very interesting! Thanks! I'll probably need to make this more CLI-related but I might end up stealing that example as it's the next logical step to use this with...

## Alternative proposal Introduce `render_to` which accepts a `W: Write`r directly instead of allocating a string internally. ```rust for man in gen_manuals(&app) { let path = PathBuf::from(env!("CARGO_PKG_NAME")).push(man.path()); man.render_to(fs::File::create(&path)?)?; } ```...

From the etherpad: - file path handling - `..`, `..`, `//` not being auto- handled - windows gotchas, like long file paths (which require extended-length paths aka "verbatim paths" as...

Maybe also relevant (also from the etherpad): - streaming - how to thread progress computation through chained readers - handling different archive formats (this may be specific to me but...

Ideally, this will also mention https://github.com/killercup/convey once it becomes more stable!

Relevant internals thread: https://internals.rust-lang.org/t/terminal-platform-abstraction/6746

We discussed the API proposed here in #30 and I noticed that I don't fully agree with it. The main issue for me is that `.exit_status` does two things. See...