...not literally, of course.  But what happened to the previous menu of close-vote options?  I find the current set unsatisfactory. Take  for example.  Obviously, the question is worthless, because it's an exception that even a n00b programmer should be able to debug on his own. There is nothing special about this bug, and it will help no one in the future.  What could I possibly select as a close reason?   duplicate of... - Maybe. There's the classic  which has been linked to . While the debugging techniques are the same, that's for .NET.  Besides, there are any number of other common exceptions / simple development bugs that wouldn't apply. off-topic because...   ... This question was caused by a problem that can't 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  before posting.Notes below....  unclear what you're asking - No, it's clear that the programmer just needs to debug his code. too broad - No, it's quite specific. primarily opinion-based - Nope.   When it was introduced, I was happy to see a "typo" reason, to rid out all the stupid indentation or bracket questions. But... we no longer have a "lacks minimal understanding" reason, which I think is incredibly important. After all, Stack Overflow is here to solve problems that  encounter... not teach users how to code or debug.  So.... what do I pick?  Can we have another revision on the close vote reasons?  I did a cursory search, but couldn't find a Meta post to the intent behind this latest set of reasons. Edit: I believe this is it:     Edit 1/20  Ah, how could I forget about the classic copy &amp; paste homework assignment?      Right or wrong, my close vote was cast with      off-topic because it shows zero desire to actually understand the problem.      we see a moderator closing a question about an incorrect number of function parameters as lacks sufficient information to diagnose the problem. Of course, there probably is sufficient information, and the wording should really be changed to You're too lazy to RTFM.
13283
Note: the eventual outcome of this discussion involved dropping this particular off-topic reason, along with other changes. See:  &nbsp; &mdash;Shog     I was using the reason "demonstrate a minimal understanding" myself quite frequently, but the more I review, the more I have doubts about it and I think this reason can either be dropped entirely or at least rephrased, so I started to use "problems with code you've written must describe the specific problem" instead:     Questions asking for code must demonstrate a minimal understanding of the problem being solved.   So the poster has posted some description, maybe even a snippet of code and in his mind that already proves that he has that minimal understanding required. After all he described the problem and what he tried to solve. So telling him that he lacks that understanding is rather rude, and from the posters point of view doesn't even apply. What both version of the reason not emphasize is that a description of a problem is not various versions of     it doesn't work   but that we rather mean really specific details (see below). I can often see in the reopen review queue that the "improved" version just includes a more verbatim description, while what usually would be expected is some specific error message, a trace or a log, or whatever applies.  Then it continues with:     Include attempted solutions, why they didn't work, and the expected results. See also: Stack Overflow question checklist   comparing it to:     problems with code you've written must describe the specific problem — and include valid code to reproduce it — in the question itself. See SSCCE.org for guidance.   Which says essentially the same, only in more detail.   So the "minimum understanding" reason is IMO a more rude version of the reason telling the user that an SSCCE is missing.  The intent of giving this reason is to tell the user that he needs to give exact details to be able to help him, so IMO a checklist would be much better. Something like:     Your question was closed because it may not provide enough details. Things you can do to improve your question to get an answer include:         Format the code in a way that makes it readable and easily understandable.   Provide the smallest working sample of code demonstrating the problem (link to SSCCE)   Include your input and output.   If applicable provide logs (i.e. Android debugging log, stack trace, etc.).   If applicable provide the exact error messages (compiler, etc.).      And something like this should be best included already in the banner that appears when a question is closed instead of being hidden in some pages you often enough have to actively looking for.  It might be helpful to adjust this, based on the tags or close reason, as I realize that I'm more focused on the programming area, and the above list may not apply to other areas of SO.  Update  Another thing I forgot to mention (but wanted to) is this:     Questions asking for code   Is IMO essentially an invitation of the type of questions     I have a problem, can you provide the solution? (with an optional please)   while     Questions concerning problems with code you've written   puts at least some emphasis on the fact that the poster has to put some effort himself in trying to solve the problem by providing the code which he used to attempt the solution.
72101
Few arguments against it:   Pressing the flag button doesn't mean actually submitting it (as in every test/form). There might be an unknown duplicate, if you assume it's the first post (as you were told) it might be worthy to flag it. You might want to look if someone else thought it was duplicate by "making half way" to flagging it.   Why pressing the flag button makes you fail an audit? I think it shouldn't.  Edit:  The implementation difficulty (fake flagging UI) and the tips about how avoid failing (and reviewing!) by skipping the answer adds some insight, but still doesn't answer the question why it's not a valid review.    Moreover, I would like to add one more,  describes a reviewer that failed an audit while trying to flag a question as off topic. The question was clearly off topic, and still after 1300 views no one flagged it.
97770
Update: This has been implemented according to the .    OK, so  is the  time I've come across a perfectly valid bug report here on meta.SO that was closed as a duplicate, and the question it was closed as a duplicate of then deleted.  Since I don't have 10k here on MSO, I can't really tell when or why those questions were deleted, but I assume there were valid reasons for it.  However, regardless of the reasons for the deletion, having the questions that were closed as duplicates of the deleted question remain closed seems like a disservice to users.  Presumably, a duplicate of a deleted question either:   is no longer a duplicate, and should therefore be reopened; or is crap, just like the deleted question, and should therefore also be deleted.   I therefore propose that, when a question is deleted, any other questions closed as duplicates of it should be automatically flagged for reopening and/or deletion.  I'll leave the exact implementation details for the devs to decide, but one option might be to just add the dupes to both the reopen and the deletion queue, and let the reviewers in those queues decide their fate.  Or perhaps the 10k auto-flag system used e.g. for "questions closed without comment" could be adapted for this purpose too.  Edit: I like  of automatically adding dupes of deleted questions to the reopen review queue, but with the "leave closed" button replaced with "delete" / "recommend deletion" (since just leaving the question closed is not really a useful option in this situation).
52942
Before you vote to close: there are a lot of questions with titles and/or bodies that are similar to this one. However, none of the ones I saw deal with this particular case.    I have an  that is appropriately closed as a duplicate of an FAQ entry. I just tried to delete it because it doesn't really add any useful search terms or overall value to MSO. I got the following message:     Sorry, this question has answers and cannot be deleted; flag it for moderator attention instead.   That's the same message that comes up when you try to delete your own unclosed answered questions. Since I'm a 10k user, I think the system should at least allow me to cast a regular, non-binding delete vote for that post, if not delete it unilaterally.  I also think that 20k users attempting to delete their own recently closed posts shouldn't have to wait through the 48-hour "possible reopening" period, but since my example question was closed over a year ago I don't know what the system actually does.
95183
I noticed from a question about flagging vs closing (forgive me, I cannot find the link, please post it if you know it), that flags are CONVERTED into close votes for questions automatically. Can somebody confirm this?  If confirmed, I was wondering why the link (again, for questions only) is simply not removed to avoid confusion?
86654
I've just seen that the reason of closing is missing in the reviewing page of closing votes.    Is it a temporary error or it's a bug?  EDIT: Seems that only when there are audits the reason is missing.  If I cannot upload image I will make an ASCII art:  Should this question be closed as: ? (less)  ┌────────────┐ ┌─────┐ ┌────┐ ┌────┐                                              │ Leave Open │ │Close│ │Edit│ │Skip│                                              └────────────┘ └─────┘ └────┘ └────┘ Leave Open if this question should not be closed  Close if this question should be closed for any reason; consider leaving an  explanatory comment before voting  Edit if this question could be improved so that it does not need to be closed  Skip if you are not sure and want to go to the next question
87539
Close reasons still have links to the FAQ in them - these should be referred to as the Help Center, since that's what it is now.   Not Constructive (emphasis obviously mine)     We expect answers to be supported by facts, references, or specific expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, see the FAQ for guidance.  Off Topic (ditto)     Questions on Stack Overflow are expected to relate to programming or software development within the scope defined in the FAQ. Consider editing the question or leaving comments for improvement if you believe the question can be reworded to fit within the scope.  Too Localized (...)     This question is unlikely to help any future visitors; it is only relevant to a small geographic area, a specific moment in time, or an extraordinarily narrow situation that is not generally applicable to the worldwide audience of the internet. For help making this question more broadly applicable, see the FAQ.  Not A Real Question (...)     It's difficult to tell what is being asked here. This question is ambiguous, vague, incomplete, overly broad, or rhetorical and cannot be reasonably answered in its current form. For help clarifying this question so that it can be reopened, see the FAQ.    All of these should be changed to "see this Help Center topic" (or similar). Since, y'know, it's the Help Center, now, not the FAQ.
98484
I came across  in the review queue. Sometimes I come across questions of similar form. My thought is to vote to close as "too-broad" because:   Question is very broad, there are many, many ways to perform that task. No code was posted, no specific coding problem was identified.   But, and this is in general, I always get tripped up when I see that these questions have a reasonable accepted answer: I would have voted it too-broad immediately had I seen the question pop up in the new questions stream; but when I see that the answerer seemed to find the question clear enough (and his answer was accepted and deemed satisfactory), I end up going back and thinking "if it was clear enough for the answerer to provide a specific answer, doesn't that mean it wasn't too broad after all?"  How should I handle questions like this?   And, in general, how should I handle questions that, alone, seem too broad, but when answered, seem specific? Should I ignore the answers when considering closing a question, or do they retroactively change the quality of the question?
56259
Possible Duplicate:                When a question is closed! It will highlight the reason for closure (ie, based on the maximum number of votes for a category is received)  considering the example below: if a question has received two close votes for being off-topic, two as well for not being a not-a-real question. Also someONE found it to be too-localized!  With total number of 5 close votes, question will be closed. But since both the number of off-topic votes and not-a-real question votes are equal ie 2. What will be the reason highlighted on the question after getting closed. Does it depend on the reputation of close voters?  like if (total reputation of close voters for off-topic &gt; total reputation of close voters for not-real-question) then close question as off-topic  This scenario ideally shouldn't happen! But if it happens then how it is handled and is this how it works?     two users have voted for off-topic and two for not-real .. the last   person chose too-localized. Then what will be the close reason?
90313
If I edit a question and then click the "close" link, it doesn't work. Nothing appears on the screen and I'm forced to reload the page before the link works.  A  covers similar ground (except my edit wasn't inline), however this was apparently fixed.  (I've tagged as  as this is the only site I have the reputation to reproduce the issue on.)
10246
Today I have stumbled across a question that was closed . When reading this question , I thought it was valid, and I even might have an answer for it . So I went and read  and  along with some other related questions here on meta . The issue is that because :  I do NOT have 3000 points to vote for opening,  The said question is not my own ,  The person who closed it did not leave a comment, It seems that I have no option to reopen it and answer.   What one should do in that case ? Flag it for moderator ?  I would think this is not the appropriate action here . Contact the closer personally  ? - Same as Above (and also , how ?) Leaving a simple comment ? By reading the above mentioned questions - leaving a simple comment will do nothing by itself to reopen or to catch attention (unless someone else stumbles upon it ..) So what are my options for action ?? (the question is  for reference)
44614
I have , and so went to flag it as such, but after clicking "it doesn't belong here, or it is a duplicate" and "off topic," I get the following.    I think the question is more suited to Code-Review than any of the sites listed, but there doesn't seem to be an option to flag the question as "belongs on CodeReview." I am sure there is a good reason for this, and am curious to know what it is.
120963
If Community ♦ flags something for low quality or because of consecutive closed questions or whatever, I always have to click that the flag was helpful (or declined):      To my understanding, it doesn't make a difference. So, why ask in the first place?
43976
&gt; **Possible Duplicate:**   &gt; [Possible to remove the link to duplicate question?](https://meta.stackexchange.com/questions/50336/possible-to-remove-the-link-to-duplicate-question)    &lt;!-- End of automatically inserted text --&gt;  Some  have this text at the top of the Markdown. I read a bit on the history, and Shog announced this behavior stopped with changes to the system in :  [R]ather than editing in the banner, it's generated as-needed and displayed separately above the question  I'm not able to find much recent information about this, so I'm just wondering what happens if I remove the banner. Does it make a &quot;real&quot; duplicate banner appear? Will it still be closed as a duplicate? Should I remove it or is there some benefit to keeping it there?
35712
I've found strange behavior when closing this  - I definitely see that there are 3 closing votes and 2 of them are at "Off-topic" section:   -but there are no explanations on section itself:   -while, normally, it's expected that it will appear. In custom comments section there are also no closing-votes displayed.   Perhaps it's just my browser (which is FF 26 x64 under Win) - so marking this as a "possible bug". Thank you for your attention.
98486
The old "too localized" closing reason included "questions that are unlikely to help future visitors".   , that if a question resulted from a typo in the OP code those questions should be closed with "too localized" reason.  The current off-topic reason does not cover that.  Should these questions remain open now, as they do not really fall into any current closure category?  UPDATE  I marked  for diamond moderator attention to be deleted as Robert Harvey hinted below, only to get the flag declined as "declined - flags should only be used to make moderators aware of content that requires their intervention".  Can you confidently tell me that this is a useful question that helps the goal of SE?
6290
Having just  from any of the queues, it was reviewing close votes; however, this audit was flawed in that I didn't even cast a close vote.  Often I press the Close button to preview greater detail and sentiment of the closure, spawning the Why should this question be closed dialog box:    Especially for duplicates, where functionality is solely dependent on spawning this dialog.  From Closing > Duplicate, I can search or view selected duplicates:    Although, I realize general closure reasons are summarized on the page:    This question had 6-upvotes, but seemed very localized referencing subjective query is "taking too long" and even had a sqlfiddle link.  Maybe overly broad regarding performance tuning, the OP was posting like a forum with two answer posts to his own question  and  with one of those answers asking follow-up questions.    Wanting to gauge community response, current closure totals struck my curiosity.  So, I pressed the Close button and boom - oh, the humanity!  I failed, and didn't even cast a close vote.    Votes are not cast until a reason for closure is selected and Vote to Close is pressed.  Taking any review very seriously on this site, it only seems fair that my review quality is tested through actionable steps instead of clicking for more detailed information, leveraging the functional design of the close vote user interface.  Sure, it's complex to seed fake vote totals, and then there's controversy of mindless voting in the majority or people who simply cherry pick 4-vote questions.  Still though, it seems unfair I should hesitate to review further information of vote totals and duplicates before skipping due to the implementation of this audit.