RTFM
This one really sucked post 2001 or so when everything stopped coming with a fucking manual to read. What M and I supposed to R, guy?
CombatWombatEsq@lemmy.world 3 weeks ago
[deleted]
Kolanaki@pawb.social 3 weeks ago
BassTurd@lemmy.world 3 weeks ago
The only time it’s been kind of relevant in my dealings is the Arch wiki, because it really is a solid resource. However, sometimes my issue is a specific one and I need more than general information on a process. RTFM ruins communities when someone is looking for support. It’s just an entitled response to someone asking for help.
Klear@quokk.au 3 weeks ago
It’s not meant as an actual manual. What you’re really supposed to do is comb through ad-ridden google results until you find that one 10 years old reddit thread where someone thanks a deleted comment for solving the issue you have.
raspberriesareyummy@lemmy.world 3 weeks ago
until you find that one 10 years old reddit thread where someone thanks a deleted comment for solving the issue you have.
I wasn’t gonna upvote you, but that one made me chuckle. Also because I have posted many of those “deleted comments” and wiped my reddit profile as clean as I could before leaving years ago.
mech@feddit.org 2 weeks ago
Them: Read The Fucking Manual!
The Manual
The unset builtin treats attempts to unset array subscripts @ and * differently depending on whether the array is indexed or associative, and differently than in previous versions. • Arithmetic commands ( ((…)) ) and the expressions in an arithmetic for statement can be expanded more than once. • Expressions used as arguments to arithmetic operators in the [[ conditional command can be expanded more than once. • The expressions in substring parameter brace expansion can be expanded more than once. • The expressions in the $((…)) word expansion can be expanded more than once. • Arithmetic expressions used as indexed array subscripts can be expanded more than once. • test -v, when given an argument of A[@], where A is an existing associative array, will return true if the array has any set elements. Bash-5.2 will look for and report on a key named @. • The ${parameter[:]=value} word expansion will return value, before any variable-specific transformations have been performed (e.g., converting to lowercase). Bash-5.2 will return the final value assigned to the variable. • Parsing command substitutions will behave as if extended globbing (see the description of the shopt builtin above) is enabled, so that parsing a command substitution containing an extglob pattern (say, as part of a shell function) will not fail. This assumes the intent is to enable extglob before the command is executed and word expansions are performed. It will fail at word expansion time if extglob hasn’t been enabled by the time the command is executed.
raspberriesareyummy@lemmy.world 3 weeks ago
I think there’s an important nuance to lmgtfy or RTFM. These two were clearly identifiable as the kind of - sometimes snarky - min-effort response, and sometimes absolutely justified (e.g. if I googled the question of OP and the very first result correctly answers their question, which I have made the effort of checking myself).
For the slop responses however, the receiver has to invest sometimes considerable time into reading & processing it to even understand that it might be pure slop. And in doubt, as a reader we are left with the moral dilemma of potentially offending the writer by asking “Did you just send me LLM output?”
It is both harder to identify and it drives a wedge into online (and personal) relationships because it adds a layer of doubt or distrust. This slop shit is poison for internet friendships. Those tech bros all need to fuck off and use their money for a permanent coke trip straight until they become irrelevant. :/