Personally, if I made an error, be it a typo or a spelling mistake, I would appreciate a correction, otherwise I might be going on making that typo, or mistake.
For me it is similar to being corrected wrt some mistakes I made in a code I posted or a solution I suggested.
We are using languages as a tool, for explaining problems, for giving solutions, and for displaying the problem/solution. The language can be Perl, or it can be English, and mistakes in either can cause a problem, so corrections are welcomed. However, the way to correct mistakes isn't by a Janitor editing the mistake. If someone made a typo, /msging her should suffice. Correcting the mistake might even go unnoticed by the OP, resulting in no knowledge gained.
In this light, I don't see why monks who would be the first to point out a syntax error, or not using strict, or globally assigning a perlvar, would hesitate in correcting a mistake in a language either than Perl.
A badly phrased question, or a badly structured code, or bad grammar can all cause someone to misinterpret the question, or not try to give her thought to it.
I would even take that to the extreme case, since I consider English mistakes to be the same as Perl mistakes, in the context of asking a question/receiving an answer. In my opinion, titling a post with something like "need help" or "this doesn't work" or "Huh? why is that?" isn't different than an XY Problem or a typo. The OP should consider his title the way he considers his English or his code, and should, or shouldn't be corrected accordingly, only not by a Janitor, but by the OP itself.
Stop saying 'script'. Stop saying 'line-noise'.
We have nothing to lose but our metaphors.
In reply to Re: Fixing typos in replies
by Erez
in thread Fixing typos in replies
by almut
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |