Alexander Kunde

Hi, Im working on getting[ the color-term gnu test](https://github.com/coreutils/coreutils/blob/master/tests/ls/color-term.sh) for coreutils `ls`. And it present the following obstacle: ``` # rust version ~/coreutils/debug/target/ls --color=always exe # c version ls --color=always...

Please see https://github.com/nushell/nu-ansi-term/issues/41 it will enable a LS fix

another behavior that is ignored by lscolors crate right now, at least for nu-ansi-term, is reset styling `re=xx`.

MacOS test is failing since macOS does not correctly support "LS_COLORS" env variable and the mac env var LSCOLORS is not supported by underlying crate -> https://github.com/sharkdp/lscolors/issues/55

I already did some work on nu-ansi-term and lscolors has an open PR to support gnu legacy Mode aka double digit styles and reset before apply. Once it's done we...

nu-ansi and lscolors updates are close to done, im workinh on implementing youre suggestions now and will try to geg the gnu test green.

thank you, it turned out that lscolors and nu-ansi-term were incredible helpful with the changes there and we got this going in a much better way than initially thought. I...

> > Beware, they need to be either run with cargo test -- --test-threads=1 or cargo nextest run otherwise all test will change the env variables at the same time...

The test mentioned is also the one I worked on to succeed. btw, it wont since nu-ansi-term seems to not keep the color codes ordered.

Hi @ckulinsk, thank you for the workaround, but wouldn't it be preferable to not have to use additional functions to implement this with the data field? Best, Alexander