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

I've come across a situation where a question had actually some code along with it, but because the OP didn't add any indentation, I didn't realize it.

There are two reasons why I brought up this topic:

  • Many members would think the question has no value and hence downvote (not necessarily this question ) or just leave.

  • I've rejected an edit to the question thinking that the editor added code to the question and thought This edit changes too much in the original post. and maybe the editor's intention was to post an answer.

Please have a look at the question revisions. If the question had no grammatical or any sort of mistakes and no one edits the question, would anyone spot the code?

share|improve this question
Switch to the markdown view rather than the rendered output view. Then you'll see that the code had been edited rather than added. – ChrisF Feb 13 '13 at 13:44
I've rejected an edit to the question That's why you should always look at the markdown diff before the post diff. – nhahtdh Feb 13 '13 at 13:44
Your rejection reason actually reads as "The edit should be an answer to the question". See – Martijn Pieters Feb 13 '13 at 13:46
And what exactly is the bug you're reporting? The OP should check what he posts and reviewers should spend some time looking at the markdown diff...I see no bug. – Bart Feb 13 '13 at 13:47
@MartijnPieters Yes you are correct, I wanted to leave a comment but marking it as This edit changes.. wouldn't let me – AbZy Feb 13 '13 at 13:47
@Bart I wasn't too sure what to include as a tag – AbZy Feb 13 '13 at 13:48
@Bart You missed one. =) – J. Steen Feb 13 '13 at 13:50
@AbZy: There is always the 'other' option and adding a custom reason. Not that it applied here. – Martijn Pieters Feb 13 '13 at 13:50
thjis is a "bug" at suggester's side; they would better leave comments explaining stuff clearly for reviewer; and no, "improved formatting" doesn't cut it in this case. Something like "fixed markdown mistake of the poster to make their code visible" would do a much better job – gnat Feb 13 '13 at 13:54
@ChrisF Ok I didn't know about the markdown diff. that solves the suggested edits part. how about the first point? if the question wasn't edited at all. how would you evaluate the question? – AbZy Feb 13 '13 at 13:54
I would ask the user to show what they tried, and hopefully they'd reply something along the lines of "I've tried to add my code but it doesn't show", and then that'd be enough of a clue to properly edit the post. – J. Steen Feb 13 '13 at 13:58
@J.Steen Oh boy...that is....yeah....*shakes head* – Bart Feb 13 '13 at 14:05
@J.Steen fair enough. Thank you all for sharing – AbZy Feb 13 '13 at 14:09
One issue is that the markdown+html renderer throws away invalid tags silently. – CodesInChaos Feb 15 '13 at 14:03

I don't really understand what you're asking.

  1. The solution to the code being hard to spot is to edit it to format the code, as someone did.

  2. The solution to you rejecting that edit is to not do that. Always look at the Markdown source before deciding on the validity of an edit. Just in the same way that you always diff your sources before committing to a version control repository, right?

share|improve this answer

You must log in to answer this question.

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