tldr-pages/tldr

Remove `=` where ever it's possible

Open

#16,827 opened on Jun 11, 2025

View on GitHubContributor guide
 (5 comments) (0 reactions) (0 assignees)Markdown (5,377 forks)batch import
help wanted

Repository metrics

Stars
 (63,410 stars)
PR merge metrics
 (Avg merge 7d 5h) (321 merged PRs in 30d)

Description

As the style guide instructs, pages should prefer --option argument instead of --option=argument. https://github.com/tldr-pages/tldr/blob/main/contributing-guides/style-guide.md#option-syntax

If you feel like helping out, you can run grep -r = | grep \` in a page folder and start testing which of the = characters can be replaced. Some options require =, so they need to be individually tested.

Contributor guide

Research direction
Scan the directory using 'grep r = | grep \` ' to find occurrences of '=' in option syntax. For each candidate, test the actual command to see if the '=' is required (e.g., some options like ' format=json' require '=', while ' force' can be written as ' force' without '='). If not required, replace ' option=argument' with ' option argument' in the markdown file. Verify the change produces correct output by running the command.
Tech stack
None
Domain
documentation
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
Clear
Prerequisites
GitCommand line
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85