3 ms·
Sure, content is king, as they say. If you spend all your time using tools/libraries/APIs with good man pages, then use man. If you spend your time using GCC, M
by klodolph 3y ago
Sure, content is king, as they say. If you spend all your time using tools/libraries/APIs with good man pages, then use man. If you spend your time using GCC, Make, Bison, etc., then you’d be better off learning info.
You’d equally not learn how to navigate Javadoc if you don’t write Java code. Seems pretty obvious to me.
I get that info is a little easier if you are used to Emacs keybindings. But if you use info, you’d mostly just use space / backspace, ctrl-s for search, m for menu, and u for up. It’s not a lot of keybindings that you’re probably going to end up using. Yeah, info has M-x, but who ever uses it? Everyone who used man for the first time had to learn those keybindings too.
- btilly 3y agoI spent my early developer life using Perl. Which had perldoc pages that were mirrored to man pages. The few times I ventured into info pages, I found the information scattered and hard to skim because it was divided up inconveniently. While it is true that I must have learned the keybindings for man at one point, they are the same as the keybindings for vi and less. Both of which I frequently used for unrelated purposes, and so were firmly in my muscle memory.