I'm sorry, but I simply don't buy this argument, nor any of your follow on arguments in the thread. You're arguing to do a disservice to both the original poster (by not gently correcting him/her), and the newbie searcher (by reinforcing bad searches), all in the name of allowing a particular node to be found quickly. Meanwhile, we're getting in the way of more advanced searchers (it's not a stretch to think that someone who has more experience in CGI is going to need to search for help on signals or POSIX), and encouraging (by our passive acceptance) these bad subject lines.
Many of the people asking questions are also experienced. You're arguing to cater to the lowest common denominator. I would suggest instead that when someone fails to search properly, we, instead, reply and gently Help Super Search Newbies instead. That way we help them help themselves, and still have a search system that works.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||