📚 Collaborative cheatsheets for console commands

Agniva De Sarker 72461cfd7d Replacing service name by directly mentioning port num 8 years ago
pages 72461cfd7d Replacing service name by directly mentioning port num 8 years ago
scripts 2a9060aef4 Add script to post Travid build errors on PRs (#1138) 8 years ago
.editorconfig f1d3e87069 Travis CI integration: automatic linting, rebuilding index.json, building pages archive, and little other improvements 9 years ago
.gitignore 2a9060aef4 Add script to post Travid build errors on PRs (#1138) 8 years ago
.lgtm 30ffa864b1 allow non-standalone LGTM. 8 years ago
.markdownlintrc 72196b030d Use NodeJS NPM package markdownlint instead of Ruby gem mdl 9 years ago
.travis.yml 2a9060aef4 Add script to post Travid build errors on PRs (#1138) 8 years ago
CONTRIBUTING.md cab0111b17 CONTRIBUTING: streamline token guidelines (#1161) 8 years ago
LICENSE.md a1da10550a license: mention contributors 8 years ago
MAINTAINERS 82c2fc4ff5 add @agnivade to the list of maintainers 8 years ago
README.md 2df0d27495 readme: update URL for the elixir client 8 years ago
package.json 2a9060aef4 Add script to post Travid build errors on PRs (#1138) 8 years ago
screenshot.png 007ae49340 Updating screenshot (#957) 8 years ago

README.md

tldr

Build status Gitter chat Merged PRs Issue stats GitHub contributors 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 / OSX / 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! 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.

What does "tldr" mean?

TL;DR stands for "Too Long; Didn't Read". It originates in Internet slang, where it is used to indicate parts of the text skipped as too lengthy. Read more in the TLDR article on Wikipedia.