Awesome

<h1 align="center"> <img height="128px" src="https://raw.githubusercontent.com/pls-rs/pls/main/readme_assets/pls.svg"/> <p align="center"> <a href="https://github.com/pls-rs/pls/blob/main/LICENSE"> <img src="https://img.shields.io/github/license/pls-rs/pls?logo=gnu" alt="GPL-3.0"/> </a> <a href="https://pypi.org/project/pls/"> <img src="https://img.shields.io/badge/platforms-macOS,_Linux-blue" alt="Platforms"/> </a> <a href="https://github.com/pls-rs/pls/actions/workflows/ci.yml"> <img src="https://github.com/pls-rs/pls/actions/workflows/ci.yml/badge.svg" alt="CI status"/> </a> <a href="https://pls.cli.rs/"> <img src="https://img.shields.io/badge/docs-pls.cli.rs-blue" alt="Documentation"/> </a> <a href="https://pls.cli.rs/guides/get_started"> <img src="https://img.shields.io/github/v/tag/pls-rs/pls?label=rel" alt="Release" /> </a> </p> </h1>

pls is a prettier and powerful ls(1) for the pros. The "p" stands for

pretty: pls output is cleaner, friendlier and more colorful.
powerful: pls provides more features than the competition.
performant: pls is speedy and performant (written in Rust).
practical: pls has sensible defaults and an effortless interface.
petite: pls is a small, single-file, binary executable.
pliable: pls can be extensively tweaked by power users and pros.
personable: pls prioritises consumption by humans over scripts.

Pick whichever adjective helps you remember the command name.

For more information, see the documentation.