when do you usually use the man page for a complex command line tool to answer a question you have?

[jasmin@queer.group]

@b0rk answered with that option as well. with alt+h in fish, it just opens as some kind of overlay, allowing me to search the man page without removing what I've entered first.

If the man page doesn't work, the second approach is `cheat <command>` with cheat being a fish function which queries cheat.sh/<command> and pipes the output into bat.

And only after that, I'll search for information via the browser ^^

[me@social.k3can.us]

@b0rk I'm sure how to vote, but usually my order is:

1. --help
2. Google
3. man page

[jyn@tech.lgbt]

@b0rk usually —help first, then google or an llm to find the flags i’m interested in, then a man page for the details

in the middle i’ll try things; if they work i’ll either stop there, or skip the intermediate steps and go straight to the man page to figure out what the general behavior is now that it’s working in this specific case

[preinheimer@phpc.social]

@b0rk I usually start with a help command (usually shorter, probably covers what I need). the man page is like a tier 3 option.

[uastronomer@mastodon.monoceros.co.za]

@b0rk It was a bit of a toss-up for me. Sometimes I'll go straight to man, other times straight to generic google alternative. Man has the advantage of being right there - I don't even have to change my window focus - and while it can be very dense, there's a good chance I'll find an answer in the introduction or the examples at the end. But often it's simply too dense and I'm more interested in quickly solving the problem right in front of me than mastering a new tool, and then I'll open a browser and do a search.

The bad news for man pages though is that quality has definitely declined over the years. More modern packages are less likely to have a good man page, or sometimes don't have one at all. It's pretty obvious why, no sense complaining about it, but it can be annoying.

[claudius@darmstadt.social]

@b0rk i'm using manpage, when I am already on the terminal with a relatively complex command, and I just need that one extra option. I hit Ctrl+A to go to the start, type "man " (and leave all the rest of the command in place!) and hit enter. Man doesn't care about that stuff after the first arguement, so it's relatively convenient.

[polywolf@social.treehouse.systems]

@b0rk usually Google just brings me to a online man page if it's a program that has an extensive man page or --help (git, curl, etc.). If I don't know the program has a good man page then I will Google.

[b0rk@social.jvns.ca]

@uastronomer when you say "it's pretty obvious why" what do you mean?

(is it that with stack overflow & the internet generally it feels like there's less pressure to have good docs than when they were the only source of information?)

[chupson@tech.lgbt]

@b0rk i tend to first try to find the answer in the man page, and if i can’t do so quickly i’ll search for it on the internet. and if that fails, i’ll read the man page more carefully

[stepheneb@ruby.social]

@vikxin @b0rk

Same.

Also check my shell history

[csgraves@turtleisland.social]

@b0rk I've been using Linux since 1997 or so, with Slackware. I learned very early on that the only definitive source for the answer, or at least the first place one should look, is in the man pages.

I have never trusted any search engine, and nowadays, I certainly do not trust Google at all, especially with how evil the company is, and how they too force AI on everyone.

[boredzo@mastodon.social]

@b0rk It kind of depends on the question—usually my question is something like “what's the option to do such-and-such again?” which is easily answered by --help or the manpage.

When it's something more conceptual, then --help probably won't explain it and my first stop will be the manpage to see whether it does, because it's authoritative and I already have it. If that fails, then I'll try the web, and maybe a relevant book if I have one.

[astrid@physik.cool]

@b0rk I look a the man page if there is an option for what I want, usually searching for keywords I am interested in. However with git/ffmpeg I usually just google for what I need too. Their manpages are so full of options that I get easily overwhelmed. Some big manpages like bash's I've seen enough times to not get lost.

[talexb@fosstodon.org]

@b0rk Usually because my aging brain says, "Oh, that's the -s option", so I try that, and discover, No, it's not. Then I look in the man page, and discover it was actually the -S option. Well, half right?

[csgraves@turtleisland.social]

@silvermoon82 @vatine @b0rk where did you find something like that? Seems like a lot of books.

[groxx@hachyderm.io]

@b0rk I search for tools where I already know the man page is unhelpful (either too small or there's just a million options that make a whole language to learn to do basic stuff).

Which is quite a lot tbh, but I do absolutely start out with the official documentation on practically everything. Answers and mistake-preventions are almost always found in there the quickest, because mistakes consume a ton of time.

[scruss@xoxo.zone]

@b0rk I use apropos first to find the manual pages around the subject. If it doesn't turn up anything, I hit the web (or 'apt-cache search' to see if there are packages that might help me)

[maxine@hachyderm.io]

@b0rk if I’m already at least a little familiar with a tool, I would much rather look at the man page than search online. But this is partially influenced by the fact thay search got worse, but man pages actually did finally get better.

[vitu@bolha.us]

@b0rk voted "other"

Usually go for tldr. If needed, man page / --help

[b0rk@social.jvns.ca]

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