I don't have a strict idea of "done" for ut. But, I am not keen on adding increasing complex things to it either. It's purpose is convenience not exhaustiveness.
The point of ut is not to replace or invent new tooling. It is meant to be a set of tools that are simple, self exploratory and work out of the box with sane defaults. So, essentially, something that you don't have to remember syntax for or go through help/man pages everytime you want to use it.
Which BusyBox, toybox, and coreutils commands fail with data larger than RAM? Has that been part of the spec yet?
Just realized `LC_COLLATE=C sort` must be specified if you don't want it to ignore leading underscores in sorting due to LC_COLLATE=en_US.utf8 being the default these days.
This looks awesome, thanks! The best thing about this imo is that I can remember the url instead of having to dig through pages to find the official pinout pdf.
And the nice thing is it's usually at the top of search results since it's been a high quality, simple resource for years (maybe even a decade at this point?). Definitely the canonical reference (outside of the official docs, which aren't quite as user friendly).
I wanted to start using golinks in my workflow and I am a fan of the duckduckgo bangs. So, I built a Rust based web server that can act can act as your default search engine and handle bangs and go links for you.