[dkersten]

I get it, but when I reach out for help, its because I wasn't able to figure it out myself and I likely put a significant (relatively speaking) amount of time into it. If its in the manual, it means I overlooked it and could really do with a pointer. If I'm just told RTFM, that leaves a very sour taste.

I understand that devs have to deal with a lot of "dumb" questions, but that doesn't mean they have to be rude. As someone else said, silence would actually be better in this case, but a better response would be something like "hey, that's in the manual, in the blah section" because its not rude, it affirms that it is, indeed, in the manual and gives me a pointer where. Even without the last bit, it would be better. Part of good support is to acknowledge that the person has a problem, even if you can't help. If you don't want to provide support for an open source project (as in the case of the linked issues) then don't respond or at least set up a replacement to turn RTFM into something a bit more human.

> I found the answer valid, because I couldn't find the manual before.

How did RTFM help you find the manual if you didn't find it before, aside from affirming that there is, indeed, a manual?