[](https://github.com/eza-community/eza/actions/workflows/unit-tests.yml)
eza is a modern, maintained replacement for the venerable file-listing command-line program ls that ships with Unix and Linux operating systems, giving it more features and better defaults.
It uses colours to distinguish file types and metadata.
It knows about symlinks, extended attributes, and Git.
And it’s small, fast, and just one single binary.
By deliberately making some decisions differently, eza attempts to be a more featureful, more user-friendly version of ls.
eza features not in exa (non-exhaustive):
If you already have Nix setup with flake support, you can try out eza with the nix run command:
nix run github:eza-community/eza
Nix will build eza and run it.
If you want to pass arguments this way, use e.g. nix run github:eza-community/eza -- -ol.
eza is available for macOS and Linux.
If you already have a Rust environment set up, you can use the cargo install command:
cargo install eza
Cargo will build the eza binary and place it in $HOME/.local/share/cargo/bin/eza.
If you already have a Rust environment set up, you can use the cargo install command in your local clone of the repo:
git clone https://github.com/eza-community/eza.git
cd eza
cargo install --path .
Cargo will build the eza binary and place it in $HOME/.cargo.
Eza is available in the AUR.
Eza is available from Nixpkgs.
For nix profile users:
shell
nix profile install nixpkgs#eza
For nix-env users:
shell
nix-env -i eza
Eza is available from deb.gierens.de. The GPG public key is in this repo under deb.asc.
To install eza from this repo use:
bash
wget -qO- https://raw.githubusercontent.com/eza-community/eza/main/deb.asc | sudo tee /etc/apt/trusted.gpg.d/gierens.asc
echo "deb http://deb.gierens.de stable main" | sudo tee /etc/apt/sources.list.d/gierens.list
sudo apt update
sudo apt install -y eza
Click sections to expand.
eza’s options are almost, but not quite, entirely unlike ls’s.
.gitignorePass the --all option twice to also show the . and .. directories.
These options are available when running with --long (-l):
--git, --git-repos, --git-repos-no-status)Some of the options accept parameters:
eza is written in Rust. You will need rustc version 1.56.1 or higher. The recommended way to install Rust for development is from the official download page, using rustup.
Once Rust is installed, you can compile eza with Cargo:
cargo build
cargo test
The just command runner can be used to run some helpful development commands, in a manner similar to make.
Run just --list to get an overview of what’s available.
If you are compiling a copy for yourself, be sure to run cargo build --release or just build-release to benefit from release-mode optimisations.
Copy the resulting binary, which will be in the target/release directory, into a folder in your $PATH.
/usr/local/bin is usually a good choice.
To compile and install the manual pages, you will need pandoc.
The just man command will compile the Markdown into manual pages, which it will place in the target/man directory.
To use them, copy them into a directory that man will read.
/usr/local/share/man is usually a good choice.
eza depends on libgit2 for certain features.
If you’re unable to compile libgit2, you can opt out of Git support by running cargo build --no-default-features.
If you intend to compile for musl, you will need to use the flag vendored-openssl if you want to get the Git feature working.
The full command is cargo build --release --target=x86_64-unknown-linux-musl --features vendored-openssl,git.
If you have a working Nix installation with flake support, you can use nix to manage your dev environment.
nix develop
The Nix Flake has a few features:
- Run nix flake check to run treefmt on the repo.
- Run nix build and manually test ./results/bin/eza -- <arguments> for easy debugging.
- Run nix build .#test to run cargo test via the flake.
- Run nix build .#clippy to lint with clippy (still work in progress).
eza uses Vagrant to configure virtual machines for testing.
Programs such as eza that are basically interfaces to the system are notoriously difficult to test. Although the internal components have unit tests, it’s impossible to do a complete end-to-end test without mandating the current user’s name, the time zone, the locale, and directory structure to test. (And yes, these tests are worth doing. I have missed an edge case on many an occasion.)
The initial attempt to solve the problem was just to create a directory of “awkward” test cases, run eza on it, and make sure it produced the correct output. But even this output would change if, say, the user’s locale formats dates in a different way. These can be mocked inside the code, but at the cost of making that code more complicated to read and understand.
An alternative solution is to fake everything: create a virtual machine with a known state and run the tests on that. This is what Vagrant does. Although it takes a while to download and set up, it gives everyone the same development environment to test for any obvious regressions.
First, initialise the VM:
host$ vagrant up
The first command downloads the virtual machine image, and then runs our provisioning script, which installs Rust and eza’s build-time dependencies, configures the environment, and generates some awkward files and folders to use as test cases. Once this is done, you can SSH in, and build and test:
host$ vagrant ssh
vm$ cd /vagrant
vm$ cargo build
vm$ ./xtests/run
All the tests passed!
Of course, the drawback of having a standard development environment is that you stop noticing bugs that occur outside of it.
For this reason, Vagrant isn’t a necessary development step — it’s there if you’d like to use it, but eza still gets used and tested on other platforms.
It can still be built and compiled on any target triple that it supports, VM or no VM, with cargo build and cargo test.