On: Making Hard Things Easy

[imp0cat]

Right. I don't think you're supposed to read them top-to-bottom.

Use `/` and search for the things of interest (keywords, arguments, options, etc...). Use n/N to quickly jump forward/back.

[lazide → imp0cat]

Find has a particularly bad man page to find things that way.

[imp0cat → lazide]

AFAIK there is a find replacement with sane defaults: https://github.com/sharkdp/fd , a lot of people I know love it.

However, I already have this in my muscle memory: find <where> -name '<what>' -type f(file)/d(directory)

Works in 90% of situations when searching for some file in terminal, ie: find / -name 'stuff*'

The rest of the time is spent figuring out exec/xargs. :)

And once you master that, swap xargs for GNU parallel. I bet your machine has a ton of cores, don't let then sit idly. ;)

[tripleo1 → lazide]

FWIW it's `-maxdepth 1` not `-depth 1`.

But yeah, you're right.

[lazide → tripleo1]

Dude, flashbacks. Aren’t you supposed to do a trigger warning or something first! ;)

[anjanb → lazide]

you can grep the man page contents by using the following command

man <command> | col -b | grep "search_string"