Question 1

How does lla compare to exa?

Accepted Answer

lla shares similar features with exa, such as Git integration and multiple views, but adds a plugin system, interactive navigation like directory jumping, and built-in content search. However, lla's configuration is more involved, making it better for extensibility over simplicity.

Question 2

How to set up lla to always show Git status?

Accepted Answer

Use `lla -G` for Git view, or configure it in `~/.config/lla/config.toml` by adding Git-related fields to columns. You can also set defaults via `lla init` to include Git status in long format views.

Question 3

Can lla replace ls in all my scripts?

Accepted Answer

Not directly, as lla's output formats differ from `ls`, especially in machine-readable modes like JSON. For scripts, use `lla --json` or `--csv`, but ensure downstream tools can parse these formats instead of traditional `ls` output.

Question 4

How to search for text inside files with lla?

Accepted Answer

Use `lla --search 'pattern'` for content search, which supports regex with a 'regex:' prefix and includes syntax highlighting. It honors existing filters and can output results in JSON or CSV for further processing.

Question 5

What plugins are available for lla and how do I install them?

Accepted Answer

Plugins include file operations, metadata tools, and code analysis; install them via `lla install` for prebuilt releases or `lla install --git` for custom repos. Manage plugins interactively with `lla use`.

Question 6

Is lla faster than the standard ls command?

Accepted Answer

Built with Rust for performance, lla is fast for complex operations, but for basic listings, the feature overhead might make it slightly slower than minimal `ls` implementations, especially with plugins enabled.

lla

What is lla?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions