-
-
Notifications
You must be signed in to change notification settings - Fork 4.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
improve tldr tldr
with information how tldr should be updated
#824
Comments
@matkoniecz thanks for raising this issue. This is something we've considered in the past but haven't made a decision yet. The documentation for this option was added in #744 and in that PR we discussed making the contents of the tldr tldr output a formal requirement for clients to be featured in our README, but we didn't reach consensus. This issue is probably a good place to finalize that discussion and move forward. May I ask what client you're using? python, node?... |
I am using python (I see tldr in |
Back-reference: #744 |
So does this mean that this issue can be closed? I think we can close this issue now. |
Hrm, I'm not sure @daylightbrightledlight. The thing is that although each client is has the same basic similarities, they also all have their own flags and options. I suspect that this is a case of that. I wonder if there's a formal spec for 'official' tldr clients? Perhaps @waldyrious or @agnivade would know. |
We do have a minimal page here - https://github.com/tldr-pages/tldr/wiki/Minimum-specifications-for-TLDR-command-line-clients Some more thoughts here - #1065 But yes, I agree this is a client specific thing. I would say we should remove the |
I wanted to update tldr so I checked
tldr tldr
( http://www.ostera.io/tldr.jsx/#/tldr?_k=fk6knt )I tried
tldr --update
what resulted inSo I tried
tldr -o linux --update
what also resulted inThe text was updated successfully, but these errors were encountered: