Hint: :q!
Sister communities:
Community rules (click to expand)
1. Follow the site-wide rules
sudo in Windows.Please report posts and comments that break these rules!
Reminds me of a comment I once came across in a work application's code: "This function took forever to write correctly. It was hard work. I didn't document it. Figure it out."
Of course the variables were not defined properly and were named esoterically.
the variables were not defined properly and were named esoterically
I wonder why it was so hard and took so long to write
Poor skill, mostly.
As demonstrated by the variable naming and documentation.
Int ajdixneh = fuckyouandthisjob;
At what point is documenting decompiled code easier?
$ mysterytool
$
WHAT DID YOU DO?!
$ mysterytool -vv
DEBUG: Complete.
$
Knowing my luck, It probably deleted a rarely used system library and will lead to unpredictable crashes.
I don't understand how devs can be too lazy to write documentation but somehow they'd rather explain the same shit in discord over and over and over and over and over and over
The help command is one of the first things I work on in any project. Even if I'm never gonna share it, my future self will appreciate it.
Even on simple scripts, it's so help to remind yourself however the hell you made it work.
Why is discord so popular in non-gaming circles? People use it as a shitty, bloated and centralized IRC clone, with the voice fuction being completely ignored.
bc everyone is a gamer, and using another chatting app is just adding more clutter
i write poorly documented code on my solo projects because i am lonely
I think it's loneliness, honestly.
That and corporate work environment tends to rewards those that can explain stuff vocally ad nauseum.
I was recently trying trying to get help on a clipboard program someone had recommended me, clipq. What I found instead was a GitHub discussion where the dev said "I'm not sure what you mean by 'man' pages" in response to someone asking for them. I think I need to find an alternative
Did they at least provide woman pages then?
/s
Haha, I made this :) Here’s the blog post I created it for, if you want a bit of context:
But also
mysterytool --help
mysterytool: unrecognized option: '-'
ok then...
mysterytool -h
mysterytool: unrecognized option: 'h'
mysterytool --help
‘--help’ unrecognized option, -h for help
I will burn this motherfucker to the ground
Or the opposite:
mysterytool -h
-h unrecognized option, --help for help
Both need to burn.
And
mysterytool -h
mysterytool: try our info page that requires a custom viewer because gnu is better than standards. And there is no regular man page because fuck you
If the program's author hasn't bothered to properly document its function, then it has no business being on my machine.
Programmers generally detest to do documentation, so when the user help "UI" is all down to a programmer to define this is often what you get, especially if it's a small tool.
Yeah this is shitty, and if you're a programmer reading this and you agree with it, be better. There is no excuse for under-documenting a CLI.
Even when I'm developing, I write out my usage text first, like -o [json,csv,pretty] specify output format (default 'pretty') [NOT IMPLEMENTED] or the like.
Exclusively installed through some dodgy PPA you got from a blog.
strings `which mysterytool` | less
Give up your darn secrets before I start fumbling around with strace and get even more frustrated!
I just want to say this is a masterful use of the format.
Quite the mystery!
What's worse is when the tool doesn't error out for providing bad flags. And it always seems like those same tools always use nonstandard flags.
