Martin von Zweigbergk 66723276fc cli: make crossterm not respect NO_COLOR ... The `NO_COLOR` spec says that user-specified config is supposed to override the `$NO_COLOR` environment variable, and we do correctly use the `ColorFormatter` when `ui.color= "always"` is set in the user's config. However, it turns out that `NO_COLOR=1` still resulted in no color because `crossterm` also respects the variable, so the color codes the `ColorFormatter` requested had no effect. Since `crossterm` doesn't know about our user configs, it cannot decide whether to respect `$NO_COLOR`, so let's tell `crossterm` to always use the colors we tell it to use.		2024-12-06 17:37:10 -08:00
..
examples	conflicts: add "ui.conflict-marker-style" config	2024-11-23 08:28:47 -06:00
src	cli: make crossterm not respect NO_COLOR	2024-12-06 17:37:10 -08:00
testing	style: inline variables into format strings	2024-10-04 22:29:13 +02:00
tests	cli: make crossterm not respect NO_COLOR	2024-12-06 17:37:10 -08:00
build.rs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
Cargo.toml	completion: suggest file paths incrementally	2024-12-01 11:06:36 +01:00
docs	build: fix cargo publish by symlinking cli/docs->docs	2024-11-05 17:37:14 -08:00
LICENSE	cargo: add LICENSE file to each crate we publish	2023-09-22 21:48:28 -07:00