no_color VS Clipboard

This sounds like a really good pattern, and something that deserves to become a modern standard (like https://no-color.org/).

I feel like this should be made opt in somehow. If you are a noninteractive process and stdin is a tty then you probably shouldn't be swallowing input. I frequently blind-type the next command while a long running command is active, because well behaved noninteractive programs don't swallow input from stdin.

Does this support the environment variable for NO_COLOR too? https://no-color.org/

Some of us prefer tools which work best without them.

Allow me to repeat my plea for CLI developers to take a little time to read https://no-color.org and ensure their programs honor things like NO_COLOR, npm config set color false, TERM=dumb, INSIDE_EMACS etc.

https://news.ycombinator.com/item?id=35017940

Change: [#1908] Detects if terminal is VT100 capable and uses colors for the output, can be disabled using NO_COLOR.

Why not let termenv do the hard part of making this portable across terminals? It also supports lesser-known conventions like NO_COLOR.

And `cb` which works cross-platform, via https://github.com/Slackadays/clipboard

There's also CB which works with both X11 and Wayland.

I'm working on my C++ project here which is getting a special new feature soon. However, that feature is going to involve iterating over potentially hundreds of thousands of directories. So, to make sure it stays fast even on slow platforms, I decided to do some benchmarking on the slowest system you could conceivably run it on, the LicheePi with the sad little single core Allwinner D1 with the C906 CPU.