Formats pipestatus output with signal names.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
ltdk e853588e3d Initial commit 5 months ago
src Initial commit 5 months ago
.gitignore Initial commit 5 months ago
CHANGELOG.md Initial commit 5 months ago
Cargo.lock Initial commit 5 months ago
Cargo.toml Initial commit 5 months ago
LICENSE.md Initial commit 5 months ago
Makefile Initial commit 5 months ago
README.md Initial commit 5 months ago
build.rs Initial commit 5 months ago
rustfmt.toml Initial commit 5 months ago

README.md

sigs

Formats pipestatus output with signal names.

License

Available via the Anti-Capitalist Software License for individuals, non-profit organisations, and worker-owned businesses.

Installation

Just build sigs and signals for your system and install them in /usr/bin.

Usage

sigs and signals both take command arguments with pipestatus-styled output and print out the exit statuses separated by pipe characters. They expect a series of decimal integers, separated by whitespace and/or pipe characters, potentially spread over multiple arguments, which represent the exit statuses of commands in a pipeline.

If all of the exit statuses are zero, both sigs and signals output nothing. Otherwise, they output the meaning of the exit codes, with sigs preferring shortened terms and signals preferring expanded terms. Those meanings are one of:

  • SUCCESS (shortened to T) for an exit status of 0
  • FAILURE (shortened to F) for an exit status of 1
  • SIGNAME (shortened to NAME) for an exit due to signal SIGNAME (example: SIGSEGV)
  • ENAME (shortened to ENAME) for failing to execute a command due to error ENAME (example: ENOENT)
  • ??? (shortened to ?) for an exit status which could not be parsed as a number

System support

Currently, unix-family systems (including Linux, Mac OS, and most BSDs), Windows, and WASI are supported.