📚 Collaborative cheatsheets for console commands
Go to file
2019-06-12 10:26:07 +01:00
.github style-guide and PR template: add web link guidelines to checklists (#3030) 2019-05-18 17:43:29 +02:00
contributing-guides style guide: update wording of the page link (#3060) 2019-05-30 22:07:00 +02:00
pages hyperfine: fix typo (#3104) 2019-06-12 10:26:07 +01:00
pages.it/common ab: fix typo. 2019-06-10 00:35:02 +01:00
pages.pt-BR mvn: add pt-BR translation (#3045) 2019-05-28 15:48:45 -03:00
pages.ta/common cp,ls,mkdir,mv,rm,rmdir: add translations [Tamil] (#2512) 2018-11-05 22:46:16 +00:00
pages.zh 7z: apply standard syntax for options (#2935) 2019-04-19 14:15:07 +02:00
scripts [chore] fix use of doublequotes and $(...) notation in deploy script (#3048) 2019-05-23 14:27:29 +01:00
.editorconfig Travis CI integration: automatic linting, rebuilding index.json, building pages archive, and little other improvements 2015-12-04 16:54:05 +02:00
.gitignore Update macOS references 2017-07-28 21:13:30 +05:30
.markdownlintrc markdownlint: increase maximum line length to 250 2019-05-07 10:08:35 +02:00
.travis.yml TravisCI: don't clean build dir needed for deployment. 2019-02-04 23:15:37 +05:30
CLIENT-SPECIFICATION.md clieent spec: Add messaage to page resolution section 2019-04-01 20:24:42 +01:00
COMMUNITY-ROLES.md COMMUNITY-ROLES: fix usage of angle brackets (#2911) 2019-04-15 13:07:25 +01:00
CONTRIBUTING.md Contributing: simplify translation guidelines. 2019-01-15 15:32:58 +00:00
GOVERNANCE.md GOVERNANCE.md: link to the maintainer's guide 2018-11-27 17:34:47 +05:30
LICENSE.md unwrap copyright notice 2017-03-18 09:13:03 +00:00
MAINTAINERS.md Mark @andrik & @Aracki as current collaborators (#3053) 2019-05-26 02:59:02 +02:00
package.json package.json: lint all pages with markdownlint 2019-05-07 10:08:35 +02:00
README.md Add vscode extension 2019-05-06 19:13:18 +00:00
screenshot.png Optimize screenshot size (#2866) 2019-04-29 22:44:01 +02:00

tldr

Build status Gitter chat Merged PRs Issue stats GitHub contributors Number of files license

A collection of simplified and community-driven man pages.

Install it with npm install -g tldr or try the web client.

What is tldr?

New to the command-line world? Or just a little rusty? Or perhaps you can't always remember the arguments to lsof, or tar?

Maybe it 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.

Surely people could benefit from simplified man pages focused on practical examples. How about:

tldr screenshot

This repository is just that: an ever-growing collection of examples for the most common UNIX / Linux / macOS / SunOS commands.

Clients

You can access these pages on your computer using one of the following clients:

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

Contributing

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

Contributions are most welcome! We strive to maintain a welcoming and collaborative community. Have a look at the contributing guidelines, and go ahead!

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.

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

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 Wikipedia's TL;DR article.