which indicates to me that it should be or become the default recommended terminal coloring crate for Rust.

It might, but termcolor's API is quite inconvenient compared to other terminal coloring APIs, and this is mostly because it handles Windows console coloring correctly, which is necessary for pre-Windows 10 support. If you only care about supporting Windows 10 or newer, then you have a lot more choices.

For discoverability, should termcolor move to a separate repository?

Not sure. The issue volume for termcolor is quite low. The reason why it (and the other crates) are in the ripgrep repo is because it simplifies maintenance for me, which I attach a lot of value to.

I'm not sure that there's too much else left to do for termcolor anyway. It will never grow beyond very basic color/styling support. It's probably ripe for a 1.0 release.

I was using ripgrep on the default powershell terminal which has a blue background. The red with blue doesn't work well. It got me thinking that term colors for error / warning / good probably don't work well for some colorblind users. It would be pretty cool if we could somehow support colorblind cli tools out of the box. Anyway maybe this is an argument for terminal coloring being separated so functionality like that can be solved in one place?

@gilescope Huh? termcolor is already a separate crate. It's just in this repo. Please see the ripgrep documentation on how to change the colors.

This issue should be about process and maintenance. Specific features are entirely orthogonal.

Good point. And the more I think of color blindness support, the more I think its better solved once at the OS level like iOS/Android do.

I've moved termcolor to its own repository: https://github.com/BurntSushi/termcolor

My intent is to release 1.0 imminently.