tldr

tldr-pages活跃维护 有专家点评

社区协作维护的命令行速查表,用简短示例讲清常用命令的用法,省去翻 man 手册的时间。

Collaborative cheatsheets for console commands 📚.

v2.3发布于 2025-03-07 10:33 UTC64,189star +37 / 7 天5,646fork同步于 2026-11-10 23:19 UTC

专家点评

上手难度:入门更新于 2026-11-11

用示例页替代 man 手册的命令行速查表,装个客户端就能在终端里查

适用场景

  • 排查线上问题时临时忘了 tar 解压参数或 ss 过滤语法:tldr tar 直接给 3~5 条可复制示例,比 man 翻半屏选项快,比搜索引擎少一次切窗口
  • 写脚本或 Dockerfile 时确认某个命令的惯用写法:示例页给的是社区收敛过的常见用法,比凭记忆写再调试省一轮
  • 跨平台运维(Linux/macOS/BSD 混着用):同一命令在不同平台的差异在页面里分平台标注,不用分别记
  • 新人 onboarding 或离线环境:拉一份 PDF 或本地缓存,不依赖网络和 man 包完整性

踩坑

  • 仓库本身只是 Markdown 内容集合,客户端要单独装(pipx install tldr 等),只 clone 仓库不会得到可用的 tldr 命令
  • 客户端首次使用要联网拉页面或建本地缓存,内网/离线机器上会卡在这一步;issue 里出现过 Central Directory Signature 这类拉取失败报错被反复提出
  • 页面由社区贡献,冷门命令或新版本命令的示例可能缺失或滞后,别把它当权威语法参考,边界情况仍要回 man
  • 多客户端并存时行为不一致:README 自己说明 Node.js 客户端更新落后于其他官方客户端,选客户端时优先 Python/Rust 版

同类对比

同类有 cheat(cheat/cheat)和 navi,前者偏个人自定义 cheatsheet、后者偏交互式选择;需要团队私有速查内容时这两个比 tldr 更合适,tldr 的定位是公共通用命令。

怎么上手

由 README 提炼,执行前请确认
pipx install tldr
硬件要求按 README 说明

README 未说明,纯文本速查表与客户端对硬件无特殊要求

下载:源码 zip·GitHub Releases(安装包)本站不镜像安装包

项目说明

由 README 自动翻译提炼

社区维护的命令行速查表合集,用实用示例替代冗长 man 手册

社区协作维护的命令行速查表,用简短示例讲清常用命令的用法,省去翻 man 手册的时间。

核心能力

  • 用 Markdown 编写常见命令的实用示例页
  • 覆盖 UNIX、Linux、macOS、Windows、Android 等多平台命令
  • 提供 Python、Rust、Node.js 官方客户端
  • 支持多语言翻译,可查看各语言翻译进度
  • 提供 PDF 版本,无需安装客户端即可查阅

容易踩的坑

客户端需另行安装,本仓库只是页面内容集合;Node.js 客户端更新已落后于其他官方客户端;使用前需联网获取或本地缓存页面数据

内容由模型根据 README 生成,可能不完整或不准确,以官方文档为准。看原文 README

最近发版

5 个版本v2.3
  1. v2.3Client specification v2.3: Option placeholders and old asset website deprecation date最新正式版2025-03-07 · 2025-03-07 10:33 UTC

    Attention maintainers!

    We have released a new client specification. In this release we are adding a new client-side syntax to allow the clients to show either shortform or longform options. This should remove a lot of clutter. It would also allow power users to view shortform options by default while showing longform options to new users. The syntax is backwards compatible so there is no need to rush support.

    [!IMPORTANT] The old https://tldr.sh domain will stop providing assets at the end of this year.

    Changelog

    • Added longform/shortform specifications (#15253) (by @Managor)
    • Specify common as a supported platform option (#15855) (by @kbdharun)
    • Add the date of removal of the old asset website (#15862) (by @acuteenvy)
    • Various grammar fixes

    Option placeholders

    Previously we have used a basic placeholder such as {{-h|--help}} to show both the short and long options to the user. While this gave the user more information, it also caused a lot of clutter and reduced the pasteability of the commands. The new option placeholder adds single square brackets inside the placeholder ({{[-h|--help]}}) where clients are allowed to pick which one to show. It is recommended for the clients to show only longform options by default, but if a client wants to brand itself as a power user tool they can default to showings shortform options. There is also a backwards compatible presentation style for showing both, which is just the curly braces removed ([-h|--help]).


    Style guide improvements

    If you are a contributor to the tldr pages, do check out the style guide. We have made several improvements and restructuring to it such as standardizing keypress notation, adding instructions for disambiguation and grouping pages, instructing to avoid using = in option arguments whenever possible, example.com clarification, and much more.

  2. v2.2Client specification v2.2: New cache asset URLs, 10 years of TLDR pages2024-03-20 · 2024-03-20 15:44 UTC
    查看更新说明

    Calling all maintainers of both clients and tldr alike!

    Since the previous v2.1 release, a lot of work has been going on behind the scenes to improve tldr and how we publish and distribute assets.

    [!IMPORTANT] With this release, we are introducing a newer version of client specification with a major change to the asset URLs to use GitHub releases (to replace the existing method of providing assets via the https://tldr.sh domain).

    Changelog 📜

    • Removed redirect text from the caching section (#12133) (thanks @sbrl)
    • Updated asset URLs to use GitHub releases (#12158) (thanks @acuteenvy)
    • Add requirement to disambiguate triple-brace placeholders (#12158) (thanks @acuteenvy)
    • Add notice to deprecate the old asset URLs (#12452) (thanks @acuteenvy)

    Change in Asset URLs

    Previously, we distributed assets via GitHub pages hosted in a combined Git repository for both the website and the assets artifacts. Which introduced multiple issues with maintenance and size constraints, after multiple discussions like #12048, we concluded that GitHub releases are the ideal candidate to publish the ZIP, PDF and checksum assets in a rewriteable way.

    This client specification release requires all clients to update their cache URLs to the new GitHub release URLs. The updated caching section is attached below for reference:

    If appropriate, it is RECOMMENDED that clients implement a cache of pages. If implemented, clients MUST download the entire archive either as a whole from https://github.com/tldr-pages/tldr/releases/latest/download/tldr.zip or download language-specific archives in the format https://github.com/tldr-pages/tldr/releases/latest/download/tldr-pages.{{language-code}}.zip (e.g. https://github.com/tldr-pages/tldr/releases/latest/download/tldr-pages.en.zip). The English archive is also available from https://github.com/tldr-pages/tldr/releases/latest/download/tldr-pages.zip.

    [!CAUTION] Prior to version 2.2, the client specification stated that clients MUST download archives from https://tldr.sh/assets. This method is now deprecated, and will be removed in the future.

    Caching SHOULD be done according to the user's language configuration (if any), to not waste unneeded space for unused languages. Additionally, clients MAY automatically update the cache regularly.


    10 years of TLDR pages 🎉

    We're thrilled to announce that the TLDR pages project celebrated its tenth anniversary this past December, marking a decade since @rprieto's initial commit. What began with a focus on osx (macOS) has blossomed over the years into a comprehensive resource spanning multiple platforms, with thousands of pages added.

    With its expanding reach across the FOSS scene, TLDR Pages owes its success to the countless contributors and maintainers who have dedicated their time and expertise to the project. Thank you for your invaluable contributions. Here's to another ten years of making knowledge accessible and empowering command-line users globally!

  3. v2.1Client specification v2.1: Escaping placeholder syntax and automatic platform detection2023-11-30 · 2023-11-30 18:08 UTC
    查看更新说明

    Calling all maintainers of both clients and tldr alike!

    Since the previous v2.0 release, substantial work has been going on behind the scenes to improve tldr, spanning from new platform additions to adding l10n support for tldr book.

    With this minor release, we are introducing a newer version of client specification with multiple fixes to existing sections.

    Changelog 📜

    • Add requirement to support escaping the placeholder syntax in certain pages (#10730) (thanks @acuteenvy)
    • Add suggestion to detect new platforms added to the relevant pages directory automatically (#11523) (thanks @kbdharun)

    Updates

    Platform additions: BSD 💻

    We have added support for FreeBSD, NetBSD and OpenBSD platforms to the pages directory. Currently, it contains a small subset of package manager commands. If you use any BSD platform-specific commands, we suggest creating a PR to add them to the subdirectories. (thanks @mrusme, @acuteenvy)

    PDF changes

    Tldr book is now available in your language 🎉

    We have added support for generating tldr book PDFs for translations in our CI with a new build-pdfscript (#10969). The default font of the pages was updated to Noto Sans to support additional languages.

    The PDF files contain rendered tldr pages from your pages.<locale> directory sorted platform-wise. They are available here and are also visible on our website at https://tldr.sh/assets/tldr-book-<locale>.pdf.

    [!Note] Tldr book PDFs will not be available in a few languages due to rendering issues upon generation.

    Platform-specific PDF creation

    We have added support to create platform-specific PDF pages in the render.py script. (https://github.com/tldr-pages/tldr/pull/11195) (thanks @kbdharun)

    General Updates

    • There have been numerous improvements throughout our test suite and action workflows. (thanks to @sebastiaanspeck)
    • We have added a symlink for pages directory to pages.en. (#11139) (thanks @acuteenvy)

    For more updates, check out the tracker issue.


    Last month we had a successful hacktoberfest, with more than 400+ PRs merged from dozens of contributors.

    Thanks to all the contributors and maintainers for their contributions.

  4. v2.0Client specification v2.0: Introducing individual translation archives and other changes2023-09-10 · 2023-09-10 17:47 UTC
    查看更新说明

    Calling all maintainers of both clients and tldr alike!

    Since the v1.5b release, the master branch was removed. The clients that haven't updated got moved to a dedicated section in the wiki. If you are a user of any of these clients, we highly recommend migrating to a supported community client or one of our official clients.

    Client authors

    Changelog

    This version of the CLIENT SPECIFICATION introduces the following changes:

    Requiring support for long options

    Clients will be required to add support for long options for commands along with short options for a more uniform experience.

    Introducing caching support for individual translation archives for each language

    Addressing the community's requests, we have added support for individual language-specific translation archives in https://github.com/tldr-pages/tldr/pull/10555 (thanks @adamazing). If your client displays pages based on the user's language configuration from the cache, now you can include the selected language along with English as a fallback to save space from unused languages.

    Complete translation archives will still be available for clients using it.

    tldr maintainers

    Dependabot alerts and CodeQL analysis got enabled on compatible repositories org-wide.

    Community updates

    Last year's Hacktoberfest was one of the biggest for tldr-pages, with more than 700 PRs merged from 240+ contributors🎉 . We are excited for this year's Hacktoberfest next month.

    Thanks to all the contributors and maintainers for their contributions.

  5. v1.5b`master` → `main` branch renaming2021-05-01 · 2021-05-01 19:38 UTC
    查看更新说明

    Calling all maintainers of both clients and tldr alike!

    The master branch has now been renamed to main.

    Client authors

    While a new mirror branch master that reflects main has been created, please update your clients if required to default to main instead of master. In the future the master mirror branch will be deleted.

    Note though that it is RECOMMENDED that you download our tldr.zip instead of cloning this repository, as per our client specification if appropriate.

    tldr maintainers

    All existing PRs and branch protection rules have been updated.

    Please watch out for new PRs that merge against master, as I have been unable to create a branch protection rule on master that doesn't also block GitHub Actions from pushing to it.

用户点评

登录用户的真实使用记录,可按版本和硬件筛选
共 0 条

    还没有人点评。第一个说出真实体验的人最有价值。

    README 原文

    未翻译

    Build status Matrix chat Merged PRs GitHub contributors license Mastodon

    What is tldr-pages?

    The tldr-pages project is a collection of community-maintained help pages for command-line tools, that aims to be a simpler, more approachable complement to traditional man pages.

    Maybe you're new to the command-line world. Perhaps you're just a little rusty or can't always recall the arguments for commands like lsof, or tar?

    It certainly doesn't help that, in the past, the first option explained in man tar was:

    $ man tar
    ...
    -b blocksize
       Specify the block size, in 512-byte records, for tape drive I/O.
       As a rule, this argument is only needed when reading from or writing to tape drives,
       and usually not even then as the default block size of 20 records (10240 bytes) is very common.
    ...
    

    There is room for simpler help pages focused on practical examples. How about:

    This repository is just that: an ever-growing collection of examples for the most common UNIX, Linux, macOS, FreeBSD, NetBSD, OpenBSD, SunOS, Android, Windows, Cisco IOS, and DOS command-line tools.

    How do I use it?

    [!TIP] For browsing without installing a client on your computer, see the web client at https://tldr.inbrowser.app (with offline support using PWA).

    There are several official clients available.

    Python client

    The official Python client can be installed from PyPI via pipx (or other package managers):

    pipx install tldr
    

    Rust client

    Linux and Mac users can also install the official Rust Client using Homebrew, Cargo (or other package managers on other operating systems):

    brew install tlrc
    
    cargo install tlrc --locked
    

    Windows users can also install the official Rust Client using Winget (or other package managers on other operating systems):

    winget install tldr-pages.tlrc
    

    Node.js client

    Alternatively, you can also use the official Node.js client, although it has fallen behind in updates:

    npm install -g tldr
    

    Then you have direct access to simplified, easy-to-read help for commands, such as tar, accessible through typing tldr tar instead of the standard man tar.

    If you don't want to install any software, check out the PDF version instead.

    [!NOTE] PDFs for translations are available for most languages. You can find them in the release assets of the latest release.

    There are also various other clients provided by the community, both for the command-line and for other platforms. For a comprehensive list of clients, head over to our Wiki.

    How do I contribute to tldr-pages?

    All contributions are welcome!

    Some ways to contribute include:

    • Adding your favorite command that isn't covered.
    • Adding examples or improving the content of an existing page.
    • Adding requested pages from our issues with the help wanted label.
    • Translating pages into different languages.

    All tldr pages are written in Markdown so that they can be edited quite easily and changes can be submitted in pull requests here using Git on the command-line or using the GitHub web interface.

    We strive to maintain a welcoming and collaborative community. If it's your first time contributing, have a look at the contributing guidelines, and go ahead!

    If you'd like to contribute to translations, you can visit https://lukwebsforge.github.io/tldri18n/ to see the overall progress of all translations, and which translations are missing or outdated.

    You are also welcome to join us on the matrix chatroom and the matrix space that contains all tldr related chatrooms!

    Similar projects

    • cheat.sh Aggregates cheat sheets from multiple sources (including tldr-pages) into 1 unified interface.

    • devhints Rico's cheatsheets are not just focused on the command-line and include a plethora of other cheatsheets related to programming.

    • eg provides detailed examples with explanations on the command-line. Examples come from the repository, but eg supports displaying custom examples and commands alongside the defaults.

    • kb is a minimalist command-line knowledge base manager. kb can be used to organize your notes and cheatsheets in a minimalist and clean way. It also supports non-text files.

    • navi is an interactive cheatsheet tool, which allows you to browse through specific examples or complete commands on the fly.

    • Cheat allows you to create and view interactive cheatsheets on the command-line. It was designed to help remind Unix system administrators of options for commands that they use frequently, but not frequently enough to remember.

    • Command Line Interface Pages allows you to write standardized help pages for CLI, directories, and configs.

    • bropages (deprecated) are a highly readable supplement to man pages. It shows concise, common-case examples for Unix commands. The examples are submitted by the user base, and can be voted up or down; the best entries are what people see first when they look up a command.

    What does "tldr" mean?

    TL;DR stands for "Too Long; Didn't Read". It originated as Internet slang, where it is used to indicate that a long text (or parts of it) has been skipped as too lengthy. Read more in How-To Geek's article.