atty VS bottom

That said, there's a recent question about maintenance status and a fork with some changes, so you could switch to that if you're worried.

Maybe start with the atty crate? Ultimately this is an OS question more than a Rust question, and it depends on what you mean by "any stdout was piped". For example, do you want to be able to tell the difference between

That likely only works on a Windows console. For tools like this, you also want to handle cygwin, and that requires crazy hacks: https://github.com/softprops/atty/blob/7b5df17888997d57c2c1c8f91da1db5691f49953/src/lib.rs#L116-L154

bottom

I'd suggest Bottom as a TUI alternative to the in-built task managers - https://github.com/ClementTsang/bottom

It works on Windows also.

If anyone is looking for a "top" like, written in Rust, might have a look at https://github.com/ClementTsang/bottom

Looks like bottom with another theme

bottom - A cross-platform graphical process/system monitor with a customizable interface and a multitude of features.

As a macOS user, it boils my brain whenever I've to type in something like ~/Library/Application Support/org.rust-lang.Cargo/config.toml. macOS users have been begging CLI tools to support XDG variables on macOS too. Setting defaults is a strong indication to the community what should be the "preferred" locations. The defaults defined in your article will invariably lead to some authors saying that if that path is good enough for cargo, then it is good enough for their tool. Even the latest draft RFC acknowledges that macOS should use XDG variables too. I've written more about this here.