Utilities

Excellent Utilities: exa – replacement for ls

In Operation

Here’s the output generated running exa with the long view, showing the files, metadata, including permission bits, file sizes, and timestamps.

exa

You’ll notice the software offers an attractive color scheme, helpfully making sense of the information you’re presented with. The screen image only shows some of the goodness available. For example, it doesn’t show that exa highlights different file types such as image files, video files, documents, music, archives, cryptography, and much more.

exa lists file sizes using decimal prefixes by default: bytes, kilobytes, megabytes, gigabytes, and so on. Having human readable sizes by default is one of the many differences between exa and ls. The only (initial) downsize is that you need to inspect the suffix to interpret the file size.

One of the tool’s strengths is its long grid view making optimum full use of your monitor. The software displays as many columns as possible with full permissions information.

exa grid view
Click for full size image

As an aside, you’ll notice the README and README.md files are coloured differently. These are known as ‘immediate’ files. ‘Immediate’ files are files that are useful files to read or run first. Think of them as your starting point.

You can have directories displayed first with the long ISO time style with the command:

$ exa -l –time-style=long-iso –group-directories-first

There’s also a useful tree view available which is analogous to the tree command. The tree displays sub-directories inside the listing of their parent directories, helping visualize the directory structure and see which files are where.

exa tree view
Click for full size image

Next page: Page 3 – Summary

Pages in this article:
Page 1 – Introduction / Installation
Page 2 – In Operation
Page 3 – Summary


Complete list of articles in this series:

Excellent Utilities
AbricotineMarkdown editor with inline preview functionality
AnanicyShell daemon created to manage processes’ IO and CPU priorities
brootNext gen tree explorer and customizable launcher
cheat.shCommunity driven unified cheat sheet
crocSecurely transfer files and folders from the command-line
DeskreenLive streaming your desktop to a web browser
dufDisk usage utility with more polished presentation than the classic df
exaA turbo-charged alternative to the venerable ls command
Extension ManagerBrowse, install and manage GNOME Shell Extensions
fdWonderful alternative to the venerable find
fkillKill processes quick and easy
fontpreviewQuickly search and preview fonts
horcruxFile splitter with encryption and redundancy
LanguageToolStyle and grammar checker for 30+ languages
Liquid PromptAdaptive prompt for Bash & Zsh
lnavAdvanced log file viewer for the small-scale; great for troubleshooting
lsdLike exa, lsd is a turbo-charged alternative to ls
McFlyNavigate through your bash shell history
mdlessFormatted and highlighted view of Markdown files
OCRmyPDFAdd OCR text layer to scanned PDFs
PaperworkDesigned to simplify the management of your paperwork
PDF Mix ToolPerform common editing operations on PDF files
pecoSimple interactive filtering tool that's remarkably useful
ripgrepRecursively search directories for a regex pattern
scrcpyDisplay and control Android devices
tldrSimplified and community-driven man pages
tmuxA terminal multiplexer that offers a massive boost to your workflow
TuskAn unofficial Evernote client with bags of potential
UlauncherSublime application launcher
WatsonTrack the time spent on projects
Whoogle SearchSelf-hosted and privacy-focused metasearch engine
Share this article

4 comments

  1. I cringe when I read about CLI utilities written in Rust. That exa binary is over 800KB! (see the exa debian amd64 package)

      1. And you should remember that “software bloat always expands to make use of all the memory available” ;+}

      2. It is not a discovery for me, but will be for some, as there are deliberate attempts to cover up how bloated rust-created binaries are. For example, the description here packages.debian.org/sid/exa: “and it is small, fast, and one single binary”. of course, “small” is relative. ‘ls’ is about 145KB. Does some colour-coding, extra columns and git compatibility justify the extra 600KB? I am old-school, probably these days the younger generation of programmers don’t care about the bloat, just the coding conveniences — I have to have a bit of a grumble about it though.

Share your Thoughts

This site uses Akismet to reduce spam. Learn how your comment data is processed.