eza-community/eza

feat: work as a drop-in ls replacement

Open

#736 opened on Dec 20, 2023

View on GitHub
 (20 comments) (4 reactions) (0 assignees)Rust (439 forks)batch import
Argumentsarea: argumentsarea: sortinggood first issuetype: feature

Repository metrics

Stars
 (21,783 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Currently, exa doesn't support the -t flag in the same way as ls, so it won't work as a drop in replacement. That is, ls -ltra works, but exa -ltra won't work.

An issue existed at the exa repository for this: https://github.com/ogham/exa/issues/519

I also wrote a patch fixing this: https://github.com/ogham/exa/commit/fa76a335fd40d1f81b656b3d602309e7d39bed2f

I tried cherry-picking this, but some conflicts seem non-trivial. I'd appreciate hearing some feedback on the patch first, and if it looks good, I'll like to incorporate it into eza. Notably:

  • When -t is specified with arguments, it behaves much like exa -t X.
  • When -t is specified without arguments, it behaves like ls.

Contributor guide

Research direction
Review the existing patch at the linked commit, understand the conflicts when cherry picking, and incorporate the ` t` flag logic into eza's argument parsing and sorting. Ensure compatibility with `ls` behavior and existing `exa` flags.
Tech stack
rust
Domain
cli
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
RustGit
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60