I once wrote documentation for a fairly complicated bit of control and analysis software for use with test equipment I built for PhD students to use in my department. Towards the end of the docs I added a message that basically said "if you read this, come and see me and I'll buy you some nice food". Needless to say I never had to buy anyone anything.
linuxmemes
Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
- Instance-wide TOS: https://legal.lemmy.world/tos/
- Lemmy code of conduct: https://join-lemmy.org/docs/code_of_conduct.html
2. Be civil
- Understand the difference between a joke and an insult.
- Do not harrass or attack users for any reason. This includes using blanket terms, like "every user of thing".
- Don't get baited into back-and-forth insults. We are not animals.
- Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
- Bigotry will not be tolerated.
3. Post Linux-related content
- Including Unix and BSD.
- Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of
sudo
in Windows. - No porn, no politics, no trolling or ragebaiting.
4. No recent reposts
- Everybody uses Arch btw, can't quit Vim, <loves/tolerates/hates> systemd, and wants to interject for a moment. You can stop now.
5. π¬π§ Language/ΡΠ·ΡΠΊ/Sprache
- This is primarily an English-speaking community. π¬π§π¦πΊπΊπΈ
- Comments written in other languages are allowed.
- The substance of a post should be comprehensible for people who only speak English.
- Titles and post bodies written in other languages will be allowed, but only as long as the above rule is observed.
6. (NEW!) Regarding public figures
We all have our opinions, and certain public figures can be divisive. Keep in mind that this is a community for memes and light-hearted fun, not for airing grievances or leveling accusations. - Keep discussions polite and free of disparagement.
- We are never in possession of all of the facts. Defamatory comments will not be tolerated.
- Discussions that get too heated will be locked and offending comments removed. Β
Please report posts and comments that break these rules!
Important: never execute code or follow advice that you don't understand or can't verify, especially here. The word of the day is credibility. This is a meme community -- even the most helpful comments might just be shitposts that can damage your system. Be aware, be smart, don't remove France.
My biggest annoyance with man pages are that built-ins are a separate command and that there is no way to print all man pages but the first with the man command. That's right. There's no way to print every page for a command, 1 through 7 or whatever, with a flag. I am confidently saying there's no way to do it.
π
Hoping someone wants to correct me because I want an alias that prints all pages as one. Would also be nice if it did it for built-ins.
mankier saved my ass more times than i'm willing to admit on Barebones distros that came with no man. Especially with the command examples
I read the manual before i buy a product, I watch the product reviews, and if I can I watch the repair videos as well.
Big part of my enjoyment from buying things is the work I do upfront. I tend to do the same with any tech project.
now people just "ask GPT"... "I asked chatGPT".
my answer is "dude, GPT just copypasted from the fucking manual so you don't have to read. congrats, you didn't learn a fucking thing."
it's depressing
I've acquired a reputation as the go-to frontend wizard by reading the MaterialUI documentation. Now half my job is randomly getting called on Teams, listening to someone ramble about what crazy ideas they have for their frontend, and pointing them to the MUI implementation that already exists (because there are no new ideas). It's stupid, those docs are modern and well-structured, people just refuse to read them.
Part of it is cultural and habit and that is something you can just decide to change. It helps if someone brings it up, like this post, or you might not even think of it.
I bought a $10 power strip / surge protector last week. It was the first time this occurred to me. I pulled out the manual to throw it away, and it was only my experience in writing technical documentation that made me stop and consider actually reading/skimming it.
Maybe I'll change this habit. Maybe I'll start reading these things.
Of course some of them aren't meant to be read. But you can usually tell pretty quickly,
Can't find the manual for my girlfriend or her kids.
I need them to actually print the FM in order to R it.
I read the manual for printing and... I'm so sorry.
Reading the Gentoo Handbook in 2005 taught me more about GNU/Linux than all the tutorials about it I've ever seen
When my friends talk about what books they're reading and it comes back to me I just joke and say "oh I largely read non-fiction".
I read every manual, decision tree, process document, whatever lands in front of me.
RTFM is life
i could be reading some fucking manuals right now instead of lemmy...