2 stable releases
2.0.1 | Jul 28, 2022 |
---|
#555 in Command-line interface
2,236 downloads per month
Used in ignoreit
45KB
1K
SLoC
MinColor
A stripped down fork of Colored, designed for no-std
environments, while maintaining ease of use!
"this is blue".blue();
"this is red".red();
"this is red on blue".red().on_blue();
"this is also red on blue".on_blue().red();
"you can use truecolor values too!".truecolor(0, 255, 136);
"background truecolor also works :)".on_truecolor(135, 28, 167);
"bright colors are welcome as well".on_bright_blue().bright_red();
"you can also make bold comments".bold();
println!("{} {} {}", "or use".cyan(), "any".italic().yellow(), "string type".cyan());
"or change advice. This is red".yellow().blue().red();
"or clear things up. This is default color and style".red().bold().clear();
"purple and magenta are the same".purple().magenta();
"and so are normal and clear".normal().clear();
"you can specify color by string".color("blue").on_color("red");
String::from("this also works!").green().bold();
format!("{:30}", "format works as expected. This will be padded".blue());
format!("{:.3}", "and this will be green but truncated to 3 chars".green());
How to use
Add this in your Cargo.toml
:
[dependencies]
mincolor = "2"
and add this to your lib.rs
or main.rs
:
extern crate mincolor; // not needed in Rust 2018+
use mincolor::*;
// test the example with `cargo run --example most_simple`
fn main() {
// TADAA!
println!("{} {} !", "it".green(), "works".blue().bold());
}
Features
- Safe rust, easy to use, minimal dependencies, complete test suite
- Respect the
CLICOLOR
/CLICOLOR_FORCE
behavior (see the specs) - Respect the
NO_COLOR
behavior (see the specs) - Works on Linux, MacOS, and Windows (Powershell)
Colors:
- black
- red
- green
- yellow
- blue
- magenta (or purple)
- cyan
- white
Bright colors: prepend the color by bright_
. So easy.
Background colors: prepend the color by on_
. Simple as that.
Bright Background colors: prepend the color by on_bright_
. Not hard at all.
Truecolors
Mincolor has support for truecolors where you can specify any arbitrary rgb value.
This feature will only work correctly in terminals which support true colors (i.e. most modern terminals).
You can check if your terminal supports true color by checking the value of the environment variable $COLORTERM
on your terminal. A value of truecolor
or 24bit
indicates that it will work.
Styles:
- bold
- underline
- italic
- dimmed
- reversed
- blink
- hidden
- strikethrough
You can clear color and style anytime by using normal()
or clear()
Advanced Control:
Dynamic color from str
As Color
implements FromStr
, From<&str>
, and From<String>
, you can easily cast a string into a color like that:
// the easy way
"blue string yo".color("blue");
// this will default to white
"white string".color("zorglub");
// the safer way via a Result
let color_res : Result<Color, ()> = "zorglub".parse();
"red string".color(color_res.unwrap_or(Color::Red));
Colorization control
If you want to disable any coloring at compile time, you can simply do so by
using the no-color
feature.
For example, you can do this in your Cargo.toml
to disable color in tests:
[features]
# this effectively enable the feature `no-color` of colored when testing with
# `cargo test --feature dumb_terminal`
dumb_terminal = ["mincolor/no-color"]
You can use have even finer control by using the
mincolor::control::set_override
method.
Build with Docker
Install Docker
Use the install instructions located here
Build the Docker image
docker build -t colored_image .
Build the library
docker run --rm -it -v "$PWD":/src -u `id -u`:`id -g` colored_image /bin/bash -c "cargo build"
Test the library
docker run --rm -it -v "$PWD":/src -u `id -u`:`id -g` colored_image /bin/bash -c "cargo test"
Todo
- More tests ?: We always welcome more tests! Please contribute!
Credits
This library wouldn't have been the same without the marvelous ruby gem colored.
Thanks for the ansi_term crate for providing a reference implementation, which greatly helped making this crate output correct strings.
License
Mozilla Public License 2.0. See the LICENSE file at the root of the repository.
In non legal terms it means that:
- if you fix a bug, you MUST give me the code of the fix (it's only fair)
- if you change/extend the API, you MUST give me the code you changed in the files under MPL2.
- you CAN'T sue me for anything about this code
- apart from that, you can do almost whatever you want. See the LICENSE file for details.
Contributors
- Juliette Cordor: @jewlexx
- Thomas Wickham: @mackwic
- Corey "See More" Richardson: @cmr
- Iban Eguia: @Razican
- Alexis "Horgix" Chotard: @horgix
- Keith Yeung: @KiChjang
- Kyle Galloway: @kylegalloway
- Luke Hsiao: @lukehsiao
- kurtlawrence: @kurtlawrence