eza

What I find weird about Powershell is that there's no "fixed-width column" parser, which is a widely used format for Unix-style CLI tools. I don't know if NuShell has it, I haven't tried. In any case, it's much better for tools to output more-parseable data in the first place. Whitespace-delimited columns are fine of course, but not so much when the data can contain whitespace, as in the output from `ps`. I don't see much reason why JSONLines (https://jsonlines.org/) / NDJSON (https://ndjson.org/) can't be a standard output format from most tools, in addition to tables. As for the reason of removal: any language that can interact with json output can use readdir(3) and stat(2). Ugh. Any language of course can do it. But that's basically telling users that they need to reimplement ls(1) themselves if they want to use any of its output a

> it's very hard to salvage the work into a maintained fork. Sometimes, perhaps, but https://github.com/eza-community/eza looked pretty easy, and they even had push access to change the exa repository to point to it.

the community fork "eza" is not is it? https://github.com/eza-community/eza

> https://github.com/eza-community/eza/releases/tag/v0.11.0 > A new minor release, and the first minor release in the lifetime of eza. Why a minor release? Because we just landed windows support, that's why! Windows support, woohoo!

I love exa but that grid bug was bugging me - its fixed in the fork! See here: https://github.com/eza-community/eza