Stack Exchange network consists of 183 Q&A communities including Stack Overflow, the largest, most trusted online community for developers to learn, share their knowledge, and build their careers.
The problem was a misspelled _gaq (written as _gat).
Should these be closed? Surely they're of no use to anyone once the OP recognizes the mistake.
If so, what justification should be given? Not a real question? Too localized?
Just to be clear, the question linked above actually was not broken due to a typo. This was my mistake, and raises some other interesting questions. See the discussion below.
Note, this applies to many Stack Exchange sites, not only Stack Overflow.
@Lix hmm, you're right, I just tested it out and apparently _gat is a thing once the google analytics stuff is injected. In fact I think I actually knew _gat was a thing at some point and forgot. I don't suppose there's any way to remove my premature flag? ;)
I think that it is better to miss flag a question rather than un-flag a possibly bad question. If most of your flags are valid I do not believe that this should have any negative effect - your flag will just be ignored.
I don't see why the flagger shouldn't be able to unflag after realizing the flag was invalid. I imagine there could be plenty of cases where someone flags something and then either realizes they misunderstood something, or some conversation unfolds that indicates things weren't as they seemed, or whatever. Lack of negative effect doesn't necessarily make nonunflagability preferable to unflagability.
I agree with you there - perhaps one should reconsider your usage of flags - maybe raise the bar for flaggable posts. Perhaps wait to see if the OP makes some edits that would improve the post. In any case, as long as your helpful flags count is high and you don't have many rejected flags then the user acting on the flag will realize that it was a mistakenly flagged. Unless this happens a lot I don't think it is such an issue.
I'm more worried about the moderator not necessarily knowing enough about the subject matter to realize the flag was bad, and closing it with improper justification. Not to imply that moderators don't know their stuff, but not everyone is an expert at everything.
With all the possible typos one could make for the same code snippet, imagine how much questions we could have, if those questions would not be closed as too localized.
@kiamlaluno yeah, I gather by comparing the score of the Q and top A that this is assumed to be fairly obvious / common knowledge. I just wanted to be sure.
@ShadowWizardSaysNoMoreWar I agree. This is about the current "Caused by Typo" close reason, written when too-localized was used. Since it has its own tag it can be closed as "No longer reproducible". But it still leaves a problem, this Q and this one seem to be the most upvoted on the subject of the Typo close reason on MSE, but in order to keep them open they should be updated to current standards.
I think "too localized" would be appropriate in such a case... A simple proof-read of the code by the OP would have prevented the issue - point it out to them and VTC.
It is possible however that this one small spelling mistake is not the only problem with the code - one should also consider the same code without the mistake and try to see if a problem still exists. Sometimes the error could have been caused by the OP rushing to post the question.
The only reason I can see for leaving a post like that open is that other people can see how embarrassed the OP was and they'll make an effort to proof-read their own code before posting :)
An important thing to note is that these posts should not be edited to fix the typo!
Proof reading aside, this guy's obviously not even looking at any log output, or he'd have his problem pinpointed immediately. Every typo question I've seen has been like that.
Perhaps a comment regarding debugging advice would be appropriate as well. But you are right - these types of posts should not be here - If the OP took a little bit more care they could have been prevented.
Stack Overflow has a specific close reason for such questions under "Off-Topic -> Other": "This question was caused by a problem that can no longer be reproduced or a simple typographical error. While similar questions may be on-topic here, this one was resolved in a manner unlikely to help future readers. This can often be avoided by identifying and closely inspecting the shortest program necessary to reproduce the problem before posting."
But...sometimes they are insanely useful to people tracking down the same error message, so I don't think a policy of "close on site" is necessarily appropriate....
Yes, spelling mistakes and tiny syntax errors are frequently closed as too localized. Usually, the people who posted answers will not vote-to-close out of fear of losing the reputation they gained. I almost always need to flag these for moderators because no one else votes for them. I think the general majority just don't look hard enough to see when questions are too localized or not.
There is one instance where they should not be closed - if they are exceptionally well documented, including the specific error that the typo gave them. Others will have similar problems in the future, look up the error issued, and have one more thing to check when nothing else helps because they'll keep overlooking the spelling issue.
I don't believe we need a community policy to close such questions, mostly because some users will close them blindly without taking into account that some of them will still be worthwhile.
I do not agree - if a question is too localized, it does not matter how much effort was put into the post and documenting the errors. I fail to see how one person's spelling mistake will be beneficial.
Actually, I sort of agree, on the condition that the correct version for the typo'd thing is especially confusing/misleading, like for instance the "correct" version itself is actually misspelled (think HTTP REFERER, also seen it happen in some private APIs).
Apparently at least some mods agree with this. I custom flagged a typo question and it was rejected with "This is declined because while they did make a typo, they include code, the error, and a lot of good stuff people can google for if they have that problem."
By clicking “Accept all cookies”, you agree Stack Exchange can store cookies on your device and disclose information in accordance with our Cookie Policy.
_gatis a thing once the google analytics stuff is injected. In fact I think I actually knew_gatwas a thing at some point and forgot. I don't suppose there's any way to remove my premature flag? ;)too-localizedwas used. Since it has its own tag it can be closed as "No longer reproducible". But it still leaves a problem, this Q and this one seem to be the most upvoted on the subject of the Typo close reason on MSE, but in order to keep them open they should be updated to current standards.