`--system-protected` option is ignored when used with `-a` or `-A`
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 16.2k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
`lsd --system-protected` works as expected but `lsd --system-protected -a` or `lsd --system-protected -A` acts like `--system-protected` isn't there. This is a problem for people like me who setup aliases to always use `-A` or `-a`
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the issue with `lsd --system-protected`, then with `lsd --system-protected -a` and `lsd --system-protected -A`, and compare the results. Trace the command-line option handling from the CLI entry point; done means both combined forms honor `--system-protected` while preserving the expected `-a` or `-A` behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100