Skip to content

Commit cf1a99e

Browse files
authored
Update managing-colors-in-rust.md
1 parent d7ec20b commit cf1a99e

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

src/managing-colors-in-rust.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -6,9 +6,9 @@ There are many Rust libraries for managing terminal colors. You *should* use [ow
66
* minimizes dependencies on global state
77
* involves zero allocations
88

9-
> Note: you *should not* use [termcolor](https://docs.rs/termcolor/latest/termcolor/) because it targets the deprecated Console APIs on Windows—and has a significantly more involved API as a result.
9+
> Note: you *should not* use [termcolor](https://docs.rs/termcolor/latest/termcolor/) because it targets the deprecated Console APIs on Windows—and has a significantly more complicated API as a result.
1010
>
11-
> Instead, use a library that just only supports ANSI color codes, and initialize support for them on Windows with [enable-ansi-support](https://crates.io/crates/enable-ansi-support).
11+
> Instead, you *should* use a library that just only supports ANSI color codes, and initialize support for them on Windows with [enable-ansi-support](https://crates.io/crates/enable-ansi-support).
1212
1313
There are two general ways with which color support can be handled. I'm going to call them the "immediate pattern" and the "stylesheet approach", respectively. **Library code that supports colors *should* use the stylesheet approach.** Code in a binary crate can use whichever pattern leads to simpler code.
1414

0 commit comments

Comments
 (0)