exa VS visidata

that's exa instead of ls there, cbonsai, and dt's shell color scripts, pipes-rs

exa

I finally got tired of not having directories first on macOS, and - for me - something like exa <https://the.exa.website/> was overkill. So I dug into the source code, hunted down the missing BSD-licensed headers, figured out how to work around the APSL headers, and smoothed out the rough edges.

Very much a personal itch-scratching exercise and only a couple hours worth of work, but maybe it'll be useful for someone else.

Exa (alternative for ls)

exa: serve como alternativa ao “ls”; e

"exa" -- A modern replacement for "ls" with proper formatting, color highlighting, and git awareness.

You can also use exa with the --icons option

Both LSD and exa are replacements for the ls command. They both look gorgeous with nice colors and icons and have features like headers, sorting, tree views, and so on. Exa is a bit faster than LSD for tree views and can show the Git status of files and folders. I prefer exa due to the Git support and faster tree views. I have set up my ls alias to use exa by default. Both can be configured to show custom columns and sorting behaviors.

In fact ls -A don't work because is a alias to 'exa'.

VisiData is an awesome terminal spreadsheet tool. edbrowse for internet browsing.

If you are a command-line user, try visidata[0]

[0] https://github.com/saulpw/visidata

Help Sarah find the family holiday tapestry before her father notices it's missing! Sharpen your SQL/Python/VisiData skills with Hanukkah of Data.

Have you heard of Visidata

One of my common use cases is for parallelizing ad-hoc REST API on large batch data by using it in conjunction with cURL (or one-off Python or PHP scripts), jq and VisiData.

I've also incorporated it into VisiData so if you use that, you can look forward in the next version (should be released in the next week or two) to just browsing online .zip files like it's nobody's business.

Sweet. Here’s my open issue with VisiData about this: https://github.com/saulpw/visidata/issues/1398

There’s a sample file at the end of that thread.

Would you be open to filing an issue with these details? https://github.com/saulpw/visidata/issues/new?assignees=&lab...

We do not have anyone who is deeply familiar with USV spec details on the team, and could use your help to understand what needs to be fixed.