when do you usually use the man page for a complex command line tool to answer a question you have?
-
when do you usually use the man page for a complex command line tool to answer a question you have? (like git, openssl, rsync, curl, etc)
(edit: no need to say "i use --help then man")
@b0rk depends if I'm looking for "what's the letter option to save curl output to a file" (man) or "What's the incantation to do a fairly complex thing with ffmpeg" (stackexchange)
-
i'm very curious about everyone who says "I'd look there first", if I want to figure out how to do something new I think I'll usually google how to do it rather than look at the man page, and then maybe later look at the man page to look up the details
(I've gotten enough of these answers:
- "I like that man pages don't require changing context"
- "with the man page I know I have the right version of the docs")@b0rk i do try —help first but you made that one option. Also if at the start of the man page I find it very unclear I hit /example to find the example section
-
@b0rk Probably has to do with how you grew up on the internet. Before StackOverflow, there really wouldn’t have been anything useful on the web; “RTFM” was indeed the generic advice (and sometimes phrased more politely) on Usenet and mailing lists.
Also a factor: the quality of the man pages you’re used to (BSD man pages tend(ed?) to be significantly better than “go use the ‘info’ page” Linux default).
-
also it just occurred to me that the one time I wrote a command line tool (https://rbspy.github.io/) I didn't write a man page for it, I made a documentation website instead. I don't remember even considering writing a man page, probably because I rarely use man pages
(not looking to argue about whether command line tools "should" have man pages or not, just reflecting about how maybe I personally would prefer a good docs website over a man page. Also please no "webpages require internet")
@b0rk I almost always google my way to a website manual when I need to know how a tool works. Or I settle for `command --help`. Maybe I should add man into the rotation
-
@simontatham @b0rk "... another possibility is that you don't even yet know which _program_ you want to use ..." apropos is your friend, my friend
@spv @simontatham @b0rk I always use man -k as I cannot spell apropos...
-
i'm very curious about everyone who says "I'd look there first", if I want to figure out how to do something new I think I'll usually google how to do it rather than look at the man page, and then maybe later look at the man page to look up the details
(I've gotten enough of these answers:
- "I like that man pages don't require changing context"
- "with the man page I know I have the right version of the docs")@b0rk too much outdated misinformation on web sources - that’s where AI learned to hallucinate. If I know I want to use a complex tool I’m gonna look to the supposedly canonical source first. If the answer isn’t apparent I turn to the web using the terms the tool uses that approximate what I want to accomplish.
-
i'm very curious about everyone who says "I'd look there first", if I want to figure out how to do something new I think I'll usually google how to do it rather than look at the man page, and then maybe later look at the man page to look up the details
(I've gotten enough of these answers:
- "I like that man pages don't require changing context"
- "with the man page I know I have the right version of the docs")@b0rk for git I agree, but that it is mostly to find the right subcomands (or recipes), so like searching for unknown/forgotten commands. But curl, ssh, rsync: i find easier: is -P or -p or -e … to specify the port? How to filter, etc. I find googling slower, with obsolete comments or without good explanation (eg putting a lot of short options together) so I must go again to man page.
-
i'm very curious about everyone who says "I'd look there first", if I want to figure out how to do something new I think I'll usually google how to do it rather than look at the man page, and then maybe later look at the man page to look up the details
(I've gotten enough of these answers:
- "I like that man pages don't require changing context"
- "with the man page I know I have the right version of the docs")@b0rk an old habit, as I know the basics of the common utils after mumble years and only need a refresher on specific flags that I might use only a few times per year (or decade). Though I have been dabbling in asking a plagiarism bot for things then `man [tool]` [Enter] [/--flag] [Enter] to check unless the answer knocks loose a memory. For newer tools that might not have man pages yet I usually search `tool github` and look for a docs link from there.
-
when do you usually use the man page for a complex command line tool to answer a question you have? (like git, openssl, rsync, curl, etc)
(edit: no need to say "i use --help then man")
@b0rk it depends on the question..
- For "can I even do X..." (or if I know it's quite annoying to get the params right), I like to ask Perplexity
- For "I know I can do X, what's the param again", I like to use `--help` or `man`
- For "I don't remember the exact semantic of X, what does it do exactly?", I like to use `man` -
i think part of the reason I'm feeling interested in man pages right now even though I rarely use them is that search has gotten so much worse, it's frustrating, and it makes it feel more appealing to have trustworthy sources with clear explanations
@b0rk One of the best features of the older man pages was a keyword-in-context index. See https://en.wikipedia.org/wiki/Key_Word_in_Context for an example.
If I thought of a word, I could see where it was used in man pages, and ONLY in man pages. Low noise, high granularity.
I'm tempted to make one as Appendix B of a small reference book I'm writing. I bet I can use my concordance file and grep for each of the words, reporting chapter instead of page in on-line formats.
-
i'm very curious about everyone who says "I'd look there first", if I want to figure out how to do something new I think I'll usually google how to do it rather than look at the man page, and then maybe later look at the man page to look up the details
(I've gotten enough of these answers:
- "I like that man pages don't require changing context"
- "with the man page I know I have the right version of the docs")@b0rk I struggled with which option to choose for that exact reason! There’s a fairly complex interaction between what kind of new thing I’m doing, how the command is structured, and how much of an idea I have of how to approach it. A “what flags do I need to pass” question (more common with curl) will almost always start with man, but for “how do I even approach this” (more common with git) I’m more likely to start with search. But if I think I can find the right man page, I start there.
-
i'm very curious about everyone who says "I'd look there first", if I want to figure out how to do something new I think I'll usually google how to do it rather than look at the man page, and then maybe later look at the man page to look up the details
(I've gotten enough of these answers:
- "I like that man pages don't require changing context"
- "with the man page I know I have the right version of the docs")@b0rk two points:
• Investing in collateral knowledge of other options and the information the developer / documenter put there on purpose. The implied idea is that they know what to emphasize in docs.
• Preference for local information. So it’s --help/man > Google/SO > everything else *gestures vaguely*
-
also it just occurred to me that the one time I wrote a command line tool (https://rbspy.github.io/) I didn't write a man page for it, I made a documentation website instead. I don't remember even considering writing a man page, probably because I rarely use man pages
(not looking to argue about whether command line tools "should" have man pages or not, just reflecting about how maybe I personally would prefer a good docs website over a man page. Also please no "webpages require internet")
@b0rk The point of having a man page (or as you edited the original post: a --help) is that it's self-contained and, hopefully, true to the actual thing you're trying to run. The website requires an internet connection and it might be about a newer version than you have (did your distro or you forget to upgrade the tool?) or older (did the author forget to update the documentation?) and while a site is often a better UX (graphical browsers and whatnot), those are issues to be considered.
-
also it just occurred to me that the one time I wrote a command line tool (https://rbspy.github.io/) I didn't write a man page for it, I made a documentation website instead. I don't remember even considering writing a man page, probably because I rarely use man pages
(not looking to argue about whether command line tools "should" have man pages or not, just reflecting about how maybe I personally would prefer a good docs website over a man page. Also please no "webpages require internet")
@b0rk note: Because Debian requires man pages, I notice that lot of the are written by debian developers, so I assume also a lot of developers don’t use man pages. (note also that writing man pages was very difficult, not just content, but technically: complex non standardized language, various tools, and I still not sure there is a guide on conventions)
-
i'm very curious about everyone who says "I'd look there first", if I want to figure out how to do something new I think I'll usually google how to do it rather than look at the man page, and then maybe later look at the man page to look up the details
(I've gotten enough of these answers:
- "I like that man pages don't require changing context"
- "with the man page I know I have the right version of the docs")@b0rk same, I would only look at a man page in direst need, they are borderline unusable to me from the perspective of “someone who doesn’t know the command at all”
-
i'm very curious about everyone who says "I'd look there first", if I want to figure out how to do something new I think I'll usually google how to do it rather than look at the man page, and then maybe later look at the man page to look up the details
(I've gotten enough of these answers:
- "I like that man pages don't require changing context"
- "with the man page I know I have the right version of the docs")@b0rk --help and man let me figure things out without changing context. sure I have a browser right there, but while on the cli, I want my answers there.
Red Hat drew the same conclusion with the use cases for their wonky Lightspeed cli LLM helper thingy.
ofc if theres no man page Ill go to the website and not really think about it.
-
i'm very curious about everyone who says "I'd look there first", if I want to figure out how to do something new I think I'll usually google how to do it rather than look at the man page, and then maybe later look at the man page to look up the details
(I've gotten enough of these answers:
- "I like that man pages don't require changing context"
- "with the man page I know I have the right version of the docs")@b0rk if i’m answering a question about a tool that i’ve used before, then i’ll check the man page
if it’s a new tool or a new problem and i don’t know the lay of the land, i’ll probably read blog posts about how others have tackled it to gain confidence that i’m looking at a suitable tool, before digging into its documentation
-
i'm very curious about everyone who says "I'd look there first", if I want to figure out how to do something new I think I'll usually google how to do it rather than look at the man page, and then maybe later look at the man page to look up the details
(I've gotten enough of these answers:
- "I like that man pages don't require changing context"
- "with the man page I know I have the right version of the docs")@b0rk I'm kinda half and half right now between `man` and `cmd --help`, I've been using `man` more since I have `nvim` set as my `man pager`, so I can easily grep for parts of the documentation. For example, today I was looking at a series of commands `git clone && git checkout $tag && git submodule`, and I thought to myself, that looks redundant, bet you can do all that with just `git clone`, so I grepped the git clone man page for `checkout` and `submodule` to find all the relevant flags
-
i'm very curious about everyone who says "I'd look there first", if I want to figure out how to do something new I think I'll usually google how to do it rather than look at the man page, and then maybe later look at the man page to look up the details
(I've gotten enough of these answers:
- "I like that man pages don't require changing context"
- "with the man page I know I have the right version of the docs")@b0rk one thing that I don’t think gets enough attention:
If I go on the web I have to worry about versioning. Is my version too old? This doc might not apply to me. Or maybe the online post is too old and my version has newer/better options or features. Man page and -help are locked to my actual version.
-
when do you usually use the man page for a complex command line tool to answer a question you have? (like git, openssl, rsync, curl, etc)
(edit: no need to say "i use --help then man")
@b0rk I almost always do a man page (habit) or especially --help first. Though, unless I'm already kinda familiar and am just looking up a specific flag I usually also exit it right away because I find most quite confusing unless they already have an example usage that fits my exact case.
Then I do a web search for my specific need and usually find it easier there.
