Rsync, GUIs, power, control, design, and decisions

Re:Rsync, GUIs, power, control, design, and decisions by darkpuma on Tuesday July 09, 2019 @02:36PM (#20395162)

In my experience the coverage is shockingly good. And if you find a case where there is no tldr, you're back where you're started having lost not more than five seconds. The failure case is graceful, so it was easy to put tldr into my workflow.

[ Parent | on HN ]

Re:Rsync, GUIs, power, control, design, and decisions by weaksauce on Tuesday July 09, 2019 @03:06PM (#20395436)

I wonder if tldr returns a meaningful exit value that you could write an alias/function for something like tldr $term || man $term

[ Parent | on HN ]

Re:Rsync, GUIs, power, control, design, and decisions by darkpuma on Tuesday July 09, 2019 @04:59PM (#20396516)

Definitely; tldr returns 0 on success, 1 on failure.

    tldr_or_man() { tldr $1 || man $1 }

[ Parent | on HN ]