Go to file
Sherman Hui 8b531c09bb
CONTRIBUTING, git-terminal: explain common contrib issues (#7107)
2021-10-27 14:51:53 -03:00
.github PULL_REQUEST_TEMPLATE: fix interline space (#6695) 2021-10-03 21:02:29 +08:00
.husky deps: upgrade husky to v7.0.1 (#6207) 2021-07-10 11:16:50 -03:00
contributing-guides CONTRIBUTING, git-terminal: explain common contrib issues (#7107) 2021-10-27 14:51:53 -03:00
images CONTRIBUTING, git-terminal: explain common contrib issues (#7107) 2021-10-27 14:51:53 -03:00
pages todo: merge page with examples from #7105 (#7231) 2021-10-27 18:47:29 +01:00
pages.ar newsboat: add Arabic translation (#7117) 2021-10-25 20:03:23 +02:00
pages.bn snap: add Bengali translation (#6988) 2021-10-19 17:56:04 +08:00
pages.bs/common *: add Bosnian translation for aliases (#6655) 2021-10-02 12:46:12 -03:00
pages.da/common replace `man.archlinux.org` with `manned.org` 2021-04-18 15:33:27 +01:00
pages.de pacman: add sudo and use long options (#7132) 2021-10-24 23:10:33 -03:00
pages.es snake4scores, ubuntu-bug, vipw: add Spanish translation (#7183) 2021-10-24 20:16:01 -03:00
pages.fa wall, watch, whereis, whiptail, wipefs, wmctrl, wodim: add link (#6784) 2021-10-05 00:35:50 -03:00
pages.fr cmus: add French translation (#7048) 2021-10-26 15:55:03 +08:00
pages.hi/common scp, ssh: add Hindi translation (#7062) 2021-10-23 16:27:17 -03:00
pages.id date: add Indonesian translation (#7121) 2021-10-24 09:35:03 -03:00
pages.it gocryptfs: add Italian translation (#6993) 2021-10-26 00:31:03 +01:00
pages.ja du: fix wrong byte units (#7131) 2021-10-21 17:34:54 -03:00
pages.ko echo: add Korean translation (#7045) 2021-10-23 16:26:57 -03:00
pages.ml/linux pacman: add sudo and use long options (#7132) 2021-10-24 23:10:33 -03:00
pages.nl du: fix wrong byte units (#7131) 2021-10-21 17:34:54 -03:00
pages.no/common lb: add Norwegian translation (#7171) 2021-10-23 16:32:01 -03:00
pages.pl/common ack: update polish translation (#6997) 2021-10-21 15:55:47 +08:00
pages.pt_BR python: add pt_BR translation (#7143) 2021-10-26 16:17:56 +08:00
pages.pt_PT spotify: added pt_PT translation. (#7068) 2021-10-21 01:13:48 +08:00
pages.ro/common todoist: add page (#6361) 2021-08-15 17:52:54 +02:00
pages.ru/common 7z, 7za, 7zr: update list of archive formats (#7079) 2021-10-18 18:10:17 -03:00
pages.sh/common bash, dash, fish, ksh, rbash, sh, zsh: refresh (#5714) 2021-04-14 16:07:21 +02:00
pages.sr/common cd, echo, git, link, mkdir: add Serbian translation (#6692) 2021-10-06 12:53:25 +02:00
pages.sv/common rm: add Swedish translation (#6981) 2021-10-19 17:58:44 +08:00
pages.ta *: sync more information links in translations (#6537) 2021-10-01 15:28:01 -03:00
pages.th/common change git to Git on missing pages 2021-01-08 13:09:54 +00:00
pages.tr pacman: add sudo and use long options (#7132) 2021-10-24 23:10:33 -03:00
pages.uk/common git-commit*: add Ukrainian translation (#6847) 2021-10-10 23:26:22 +08:00
pages.zh ab: update Chinese translation (#7148) 2021-10-26 15:41:07 +08:00
pages.zh_TW exit: add traditional Chinese translation (#7246) 2021-10-27 18:33:47 +08:00
scripts set-more-info-link.py, translation-templates/*: add bn, sr, uk translation tags (#7101) 2021-10-20 14:25:03 -03:00
.editorconfig Changed indent size for Python files. 2020-12-18 22:40:29 -05:00
.flake8 tooling: add black and flake8 for python formatting/linting (#6454) 2021-09-03 12:17:51 -03:00
.gitattributes Update .gitattributes to force GH linguist to recognize pages (#5663) 2021-04-01 14:32:17 -04:00
.gitignore Made an oopsie in the venv instructions. 2020-12-04 12:17:52 -05:00
.markdownlintrc markdownlint: increase maximum line length to 250 2019-05-07 10:08:35 +02:00
CLIENT-SPECIFICATION.md *: fix typos reported by Hunspell (#5848) 2021-05-20 16:13:41 -04:00
COMMUNITY-ROLES.md COMMUNITY-ROLES: fix typo (#5976) 2021-10-01 20:34:43 +01:00
CONTRIBUTING.md CONTRIBUTING, git-terminal: explain common contrib issues (#7107) 2021-10-27 14:51:53 -03:00
GOVERNANCE.md GOVERNANCE.md, CONTRIBUTING.md: add inclusive language blurb (#4516) 2020-11-03 19:12:50 +00:00
LICENSE.md docs: update references to 'main' branch 2021-05-01 20:10:05 +01:00
MAINTAINERS.md *: shellcheck and fix typos (#6526) 2021-09-16 00:32:13 -03:00
README.md README: add cheat.sh to similar projects (#6928) 2021-10-09 10:42:38 -03:00
bluetoothctl.md bluetoothctl: add Malayalam translation (#7060) 2021-10-21 01:23:49 +08:00
package-lock.json Update tldr-lint to 0.0.13 2021-10-14 09:28:22 -03:00
package.json Update tldr-lint to 0.0.13 2021-10-14 09:28:22 -03:00
requirements.txt requirements.txt: add requests dependency (#6469) 2021-09-03 17:13:07 -03:00

README.md

tldr-pages

Build status Gitter chat Merged PRs GitHub contributors license

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 are new to the command-line world? Or just a little rusty? Or perhaps you can't always remember the arguments to lsof, or tar?

It certainly doesn't help that the first option explained in man tar is:

-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 seems to be room for simpler help pages, focused on practical examples. How about:

animated svg of the tldr client displaying the tar command

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

How do I use it?

A popular and convenient way to access these pages on your computer is to install the Node.js client, which is supported by the tldr-pages project maintainers:

npm install -g tldr

You can also use the fully-featured official Python client which can be installed via pip3.

pip3 install tldr

That way you can write tldr tar in the terminal to show the tldr page for tar, just like you would write man tar to show its manpage.

However, if you just want to browse without installing anything, check out the PDF version.

There are also various other clients provided by the community, both for the command-line and for other platforms:

There is also a comprehensive list of clients in our Wiki.

How do I contribute?

  • Your favourite command isn't covered?
  • You can think of more examples for an existing command?

All tldr pages are kept as Markdown files right here in this repository, so you can edit them directly and submit your changes as pull requests.

All contributions are welcome! We strive to maintain a welcoming and collaborative community. 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 current progress of all translations.

Similar projects

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

  • Bro pages are a highly readable supplement to man pages. Bro pages show 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.

  • 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 supports also non-text files.

  • 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.

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

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

What does "tldr" mean?

TL;DR stands for "Too Long; Didn't Read". It originates in 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.