Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

6
  • 6
    Whitespaceisforwimpsanyway. Commented Sep 2, 2009 at 22:14
  • I could have sworn that I’d already used this construct – and it’s not that unusual, after all. Well, if the logs say differently, that’s fair enough. Commented Sep 3, 2009 at 10:14
  • 1
    I was surprised too but I can't think of anything that has changed -- it's duplicated on both client and server, and the babelfish Markdown processor (some of them anyway) show the SAME error. Commented Sep 3, 2009 at 12:26
  • 1
    This is just righteous punishment for people who use 8-space-wide indenting. Commented Dec 23, 2009 at 19:20
  • @GMan, i take his comment to be about 8-space-indenting in some random source code file, where actual tabs or 3-or-4-space-indenting is better. Commented Dec 23, 2009 at 21:27
  • This would be awesome if it was fixed, since ctr-k doesn't work on code in a numbered list ( you have to hand indent the extra 4 lines ). Commented Oct 3, 2010 at 0:12