From COMMUNITY-ROLES.md:

Specifically: once a repository collaborator has merged at least 10 PRs (see https://github.com/tldr-pages/tldr/commits?committer=<username>) and submitted at least 5 non-trivial reviews to PRs (see https://github.com/tldr-pages/tldr/pulls?q=reviewed-by:<username>), which can overlap with t

Hi, I've found the following cheatsheet :

In the README you explain that there must be an edit button in the page and a github button to access the sheet but as you can see it doesn't appear here.

Thx ;)

When one hits ctrl-c during execution of tldr command it displays a traceback caused by KeyboardInterrupt. We should consider catching that exception.

Search a nonexisting command could take 5 seconds, like tldr 2077
This could be worse in some poor-network.

https://github.com/tldr-pages/tldr-cpp-client/blob/9b23d268548d3324581997c07df453542b302d51/src/tldr.c#L160-L164
https://github.com/tldr-pages/tldr-cpp-client/blob/9b23d268548d3324581997c07df453542b302d51/src/parser.c#L214-L221

Expect

• Add prompt for friendly

fpri

Sorry to bother again, but I have updated to the newest tldr.el (melpa package tldr-20191006.1059) and now I don't get a loop but still the zip file is shown in a buffer and not on disk:

This will be nontrivial. The JSON file at https://tldr.sh/assets/index.json should be downloaded and stored in the .tldr folder. This file will be the source of truth for finding commands instead of attempting to read a page by making a request or checking the cache. We can find the location of a page by searching through the JSON file. It would probably need to be converted to a format that i

This was first suggested in tldr-pages/tldr#1380 (comment).

Ideally the error messages would be more human-friendly. Currently they look like this:

The build for this PR has failed with the following message:

pages/linux/calc.md:10: TLDR103 Command example is missing its closing backtick