Closed ShrykeWindgrace closed 3 weeks ago
That's unfortunate, I imagined only one client with executable named tldr
. Yes we should clarify this somehow.
--render
seems more portable, I have pushed that fix to master.
Also --tldr should get more of a mention somewhere in the manual I guess, currently it only appears at https://hledger.org/dev/hledger.html#options.
I've mentioned it briefly near the start of the manual; and when running tldr fails I've made sure the warning mentions tldr --render
. I think that should be enough.
More of a documentation issue rather than a bug.
The flag
is present in the node-based
tldr
client (npm install -g tldr
, https://github.com/tldr-pages/tldr-node-client), and other clients are a-plenty, official and non-official.For example,
tealdeer
(https://github.com/dbrgn/tealdeer, it also installs astldr
) has another choice of flags:I'd say it would be a bit clearer so say somewhere that the behavior of the
--tldr
flag is compatible with the official clients. I do not have any particular number on the market share of various clients, so maybe this issue touches only a negligible minority of users who can figure out why they seeon their own =)
That
-r
flag is not in the CLI spec, so maybe just say that you need a client that supports it?