Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 158 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

There are a lot of questions on SO that are essentially read the manpage or read the FAQ/manual kind of questions. So my basic suggestion is that when somebody tries to post something like "What is the return value of xyz_common_function", SO should show a nonobstrusive link to that particular node in the manpage/faq/manual. If such keyword based detection is not possible, then how about people being able to, instead of replying, posting a "pointer to the manpage/faq/manual".

Through the entire length of the suggestion, manpage/faq/manual reffers to something that will be built into SO...

share|improve this question
Building a manpage/faq/manual into SO? That itself is another massive feature, yea? – o.k.w Oct 16 '09 at 10:42

Generally answers that are "read the manual for x" are there because the OP didn't know there was such a function as x, not that they didn't know where to find the manual; so I imagine such a feature would probably have a fairly limited impact on the number of answers which read simply "see the manual for x".

share|improve this answer

One, this is a major feature to add. Keywords for every language under the sun, with context-sensitivity (to know when you're asking about a given feature)? Entire class libraries? This could get freakin' huge -- and for not a lot of payoff, in my mind.

That, and generally, "RTFM"-type (or the more modern equivalent, "LMGTFY") answers are frowned upon to begin with. It's often been said that Google is StackOverflow's home page -- that is to say, so much of their traffic comes from Google searches that kicking someone out of the StackOverflow environment (even if not to Google itself) is probably not the right approach.

Often, there is a deeper question. Sure, API x might cover everything they need, and pointing them at raw docs might be OK. But a lot of the time, I've seen that people are more interested in how to apply API x to suit their needs, and that's information that may not be readily apparent in the man page.

Finally, again, the SO goal is to be THE repository for this information. Yes, much of it may be repetition of "what's out there" -- but the goal is to make it so that SO is the one place you as a developer have to go. That, I think, is part of why the FAQ specifically says that no question is "too newbie."

share|improve this answer

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .