DEdenysonique·Oct 26, 2026Submission
Tldr-pages: Collaborative cheatsheets for console commands
1 points · Open discussiontldr-pages
tldr
Markdown2014–2026
tldr-pages / tldr
tldr
Collaborative cheatsheets for console commands 📚.
78Distinct people
83Mentions
3Explicit recommenders
64.2KGitHub stars
What to know before exploring
What it is
Collaborative cheatsheets for console commands 📚.
GitHub
Where it is used
No documented product use was verified in the last source check.
What people are saying
I love tldr for this https://github.com/tldr-pages/tldr
lrobinovitch used a recommendation phrase. 3 indexed comments match. This is a phrase match, not a verdict.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- tealdeer-rs/tealdeer · linked in 3 of the same discussions
- chubin/cheat.sh · linked in 2 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year83 dated mentions
Observed mentions: 2014-01-26 09:30:53 UTC to 2026-10-26 16:25:09 UTC.
* An incomplete calendar period is marked with an outlined bar. Its count is not directly comparable with a full period.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2014 | 2014-01-01 00:00:00 UTC | 2015-01-01 00:00:00 UTC | 2 | 1 | 1 |
| 2015 | 2015-01-01 00:00:00 UTC | 2016-01-01 00:00:00 UTC | 4 | 1 | 3 |
| 2016 | 2016-01-01 00:00:00 UTC | 2017-01-01 00:00:00 UTC | 6 | 1 | 5 |
| 2017 | 2017-01-01 00:00:00 UTC | 2018-01-01 00:00:00 UTC | 5 | 3 | 2 |
| 2018 | 2018-01-01 00:00:00 UTC | 2019-01-01 00:00:00 UTC | 7 | 0 | 7 |
| 2019 | 2019-01-01 00:00:00 UTC | 2020-01-01 00:00:00 UTC | 9 | 4 | 5 |
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 11 | 0 | 11 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 7 | 1 | 6 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 13 | 2 | 11 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 8 | 0 | 8 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 3 | 0 | 3 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 5 | 1 | 4 |
| 2026 (partial) | 2026-01-01 00:00:00 UTC | 2027-01-01 00:00:00 UTC | 3 | 1 | 2 |
What Hacker News says
83 sourcesI've found tldr to be useful
https://github.com/tldr-pages/tldr
In Git commands I run before reading any codeI like everything about tldr except for the fact that every way to use it is an Internet-dependent client for some reason. Looking at how it works again, I’m half-tempted to write a converter from their dialect of Markdown to roff and run it against https://github.com/tldr-pages/tldr so I can do `man tldr ffmpeg`.
In Notes on Clarifying Man PagesNice, the `qq` part reminds me of this project: https://github.com/tldr-pages/tldr
That said, I rather use claude in headless mode https://code.claude.com/docs/en/headless
In Show HN: qqqa – A fast, stateless LLM-powered assistant for your shellis this not just `tldr`? https://github.com/tldr-pages/tldr
In Show HN: Greppers – fast CLI cheat sheet with instant copy and shareable searchBefore LLMs there existed quite a few tools to try to help with understanding CLI options; off the top of my head there are https://github.com/tldr-pages/tldr and explainshell.com
LLMs are both more general and more useful than those tools. They're more flexible and composable, and can replace those tools with a small wrapper script. Part of the reason why the LLMs can do that though is because it has those other tools as datasets to train off of.
In AI Coding and the Peanut Butter and Jelly ProblemUseful examples could be added to
tldr ffmpeg
See [1]. Regarding security concerns: agreed! We should generate one-shot jails before firing up 'curl | sh' or 'llm CLI'.
[1] https://github.com/tldr-pages/tldr/blob/main/pages/common/ff...
In Show HN: LLMpegYou might like (contributing to) https://github.com/tldr-pages/tldr, I'm sure your notes would be helpful to me and others! Not sure if they've got a section for specific editor packages, yet.
In Emacs: Contextual Interfaces in Casual CalcMaybe this already helps: https://github.com/tldr-pages/tldr
In Ask HN: Is there a GUI for bash shell?A bit of an aside, but I really like "guides to things we otherwise take for granted". So few man pages are built around example use cases, but those are often what make the case for a tool!
A similar spirit to projects like https://github.com/tldr-pages/tldr/ , but this has a lot more useful detail.
The ripgrep author has a blog post on performance and benchmarking that is an interesting read in itself: https://blog.burntsushi.net/ripgrep/
In Try / Ripgrep in Y MinutesLooks like bro pages is archived and they recommend https://github.com/tldr-pages/tldr or https://github.com/cheat/cheat
In Should you add screenshots to documentation?There's also tldr: https://github.com/tldr-pages/tldr
It lets you check the most commonly used options from your terminal, for example "tldr badblocks".
In Making Hard Things Easy> Along those lines, a quick way to drive adoption could be a huge "how do i do x" or recipes page to Ctrl+F through. If I have to search the internet for how to do x in nushell/fish/etc, I might as well stick to arcane bash - at least you know someone has had the same problem before.
https://github.com/tldr-pages/tldr
In The case for NushellTIL that `dig` does not have TLDR page https://github.com/tldr-pages/tldr
In Why is DNS still hard to learn?Showing the 15 most recent of 83 sources. Enable JavaScript to search and browse every indexed mention.