when do you usually use the man page for a complex command line tool to answer a question you have?
Uncategorized
272
Posts
207
Posters
0
Views
-
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 to be honest, I'll often look there first, but immediately get overwhelmed and try a web search instead.
-
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 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).
-
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 This, when I started in IT not much was on the Internet, man pages, another person, or dead tree books were the first place you looked. As time has progressed, search engines slowly surpassed man pages and books, until recently, now I generally will use a man page before a search, or even an ai, but I have a deep instinctual aversion to ai
-
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 FWIW, I first write the man page, then the code. Helps me clarify what the user wants, how I will interact with the tool. I then generate the README from the man page.
-
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 adding because you lumped man with —help, usually I try -h/—help first then look for authoritative docs
-
@b0rk adding because you lumped man with —help, usually I try -h/—help first then look for authoritative docs
@machinewitch haha yeah I added the note about --help because 20 different people said "i use --help first then man" :)
-
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 in my experience, man pages are written by experts for experts with exhaustive information, while a web search is more likely to point you to the most common uses for the command, or other people asking exactly what you need.
-
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 My recollection is that a lot of searches for command line info would come up with web man pages, like Ubuntu's or... linux.die.net? Only later did forum posts show up.
-
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 yeah if I know the tool has a good man page or help. I will try to use that first.
However, not all tools are equal. Some tools have not even a man page or something. In those cases a google search and stackoverflow often will do.
-
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 a grep or search on the help output or in the man page. Searching on terms..
-
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 Ai is also not helping, if you are using llm? A good man page or help output can correct AIs.
-
@kaleissin @b0rk @karabaic I also wish there were more man pages under Linux.
-
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 getting good documentation is the important bit. One good thing about mandoc is you can render your man page as html and serve it from you website.
-
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 I feel this. The part about search is the main point. keyword/regex search in man has always been a bit awkward even with helpers, google used to be great at bringing up the official site or man pages (which, even if it was for a diferent distro, at least help with context).
usually I try `-h` or `--help` first, then search, then man.
-
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'm a "I'd look there first". Some of my reasons:
1. I'm a recent OpenBSD convert.
2. You already mentioned the decline of Web search.
3. The man documentation is current for the *installed version* of the program.
4. My "weirdo" reason is that I find the Web incredibly distracting and addicting. Using man, even if it takes a little longer to get an answer, keeps me from distracting myself, which ultimately saves time.
-
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 gonna Google something then I need to switch windows and will probably get distracted by whatever other tabs I had open ("oh I'll just respond to this email quick ..."). `man thing` or `thing --help` is right there in the terminal, no extra steps needed.
-
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 me, the man page (or --help) is more accessible if I'm already on the command line. I'll open the man page, search for a few keywords, and then resort to a web search if needed.
-
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 look at the man page first, its because I want to stay on the command line. I forgot that tldr existed, so glad to be reminded of that in this thread.
-
@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
Feed RSS
Gli ultimi otto messaggi ricevuti dalla Federazione
-
-
@miles
Io pensavo che significasse Arancia, Carota Ellimone 🤣
-
D21
non è facile capire come si salva la democrazia
gli esperti non possono dire di saperloqui ci sono considerazioni che consigliano di evitare di lasciare campo libero alla tecnocrazia
https://piudemocraziaintrentino.org/2026/02/12/quo-vadis-democrazia-cronaca-di-un-confronto-necessario-a-roma/
-
ACE (Arbitrary Code Execution) on an ace (asexual) robotgirl
-
Il ghiaccio di Milano.
https://www.ilpost.it/2026/02/21/indagini-omicidio-rogoredo-milano-polizia/
-
"The protocol [ATProto] doesn't distribute value across the network. It concentrates it. Developers are building features on top of Bluesky's infrastructure for free, making it more indispensable with every app that ships.
And Bluesky gets to claim the moral high ground the whole time. "We're open! We're decentralized! You can leave whenever you want!" Meanwhile, the switching cost goes up every day.
Email is an open, federated protocol. Anyone can run a mail server. In practice, running your own mail server is painful and everyone just uses Gmail. The protocol being "open" didn't prevent centralization.
ATProto might be worse. [...] The open protocol is actually a centralization flywheel."
-
mailing list I can sign up to for event notifications?
-
@ben beautiful
