4 ms·
Man pages are generally not always that great. I recommend people instead digest the GNU `info' manuals, as you'll come away with a much deeper understanding of
by mickeyp 3y ago
Man pages are generally not always that great. I recommend people instead digest the GNU `info' manuals, as you'll come away with a much deeper understanding of all the userspace binaries you're likely to interact with on many common Linux systems today.
I'll make this iron clad promise: if you sit down and read the coreutils manual end-to-end (it'll take a couple of hours) you'll come away brimming with new ways to optimise your CLI workflow.
If you're allergic to the `info' program itself, you can of course read the manuals on GNU's website or, better still: use Emacs's info viewer (`C-h i' or M-x info), which is far superior.
- tpoacher 3y agoInfo has some really crap defaults. I invested some time to make a nice custom config and now I wish more things had info pages, because they're a joy to read.
- rustyminnow 3y agoI should give that a shot. Are there any specific defaults you are referring to? Lack of vi bindings? That's what always stopped me before.
- tpoacher 3y agoThe only key bindings I added were the ability to scroll up/down single lines, because I find page-scrolling annoying. But other than that, by crap defaults I mostly meant presentational issues. Once you spend a couple of minutes to learn the navigation shortcuts, they're not that hard to learn and they make using info quite pleasurable. Here is my own .infokey file, in case it is of interest. #info j up-line k down-line #var link-style=blue,underline active-link-style=yellow,bold,underline cursor-movement-scrolls=Off scroll-behaviour=Page Only highlight-searches=On nodeline=print