human-panic
human-panic copied to clipboard
rust-cli
Panic messages for humans.
**Choose one:** this is a 🙋 feature This resolves #77 by adding a `repository` field to the `Metadata` struct and a corresponding "Repository: ..." line to the message that gets...
**Choose one:** this is a 🐛 bug report A number of this crate's dependencies no longer compile on Rust 1.36.0, meaning this crate is no longer usable on Rust 1.36.0....
**Choose one:** is this a 🙋 feature request ## Expected Behavior When the Cargo.toml parameter `repository` is present and `homepage` is absent, no URL is included in the message. If...
**Choose one:** is this a 🐛 bug report Missing docs are a bug, right? :laughing: So what I am missing is just a short explanation where to call the `setup_panic!()`...
If possible, please add the following sentence to the [human-panic](https://crates.io/crates/human-panic). > It only displays a human-friendly panic message in release mode: >```sh >$ cargo run --release >``` Thank you.
This is a work-in-progress tracking issue for a `2.0` release of `human-panic`, set in motion because of #45 ## New Features - [x] Show message only to humans (#48 |...
This is a 🐛 bug report. ## Expected Behavior The changelog should contain entries for all released versions. ## Current Behavior As of tag v1.0.3, [the changelog](https://github.com/rust-cli/human-panic/blob/v1.0.3/CHANGELOG.md) only mentions the...
tests
As per #15, we should probably setup some tests. @killercup made a good suggestion that we could use https://github.com/assert-rs/assert_cli for that.
The panic information is now saving in a temp file. However, if the machine reboot, the file will be lost, and also, we want to use the regular path, so...
It would be nice to be able to specify a custom error printer, for cases where stderr is not used. For example, with a graphical application, one could use https://lib.rs/crates/msgbox.