11

I just posted the question Using collcell package with csvsimple, or datatool. After posting it looks like the formatting of the two error messages is not identical:

actual post

But, when I go to edit it what I see in the preview is identical preview for the second case, but not for the first case:

preview

9
  • Great question. :) The same happens with the spoiler syntax, as seen in this answer of mine.
    – Paulo Cereda
    Commented Nov 14, 2012 at 22:23
  • Looking on the source the bug in my opinion is in the edit preview.
    – Speravir
    Commented Nov 15, 2012 at 0:55
  • +1, even though it doesn't look like you're using markdown in a way that it is supposed/expected to be used?!
    – doncherry
    Commented Nov 15, 2012 at 1:37
  • @doncherry: You mean in terms of using the >? What is the official way of quoting errors?
    – Peter Grill
    Commented Nov 15, 2012 at 1:39
  • @Speravir: Yep, I thought it best to leave so that the SE programmers can use it as a test case to see if the updates fix the display in preview mode.
    – Peter Grill
    Commented Nov 15, 2012 at 1:41
  • If you paste the error as is, select all of it, then click the code markup button, and then the block quote button, you get this: i.sstatic.net/IfvbT.png
    – doncherry
    Commented Nov 15, 2012 at 1:44
  • 2
    @doncherry: Wow, you may find this hard to believe but I have never noticed the block quote button? :-) Have always added the > manually.. Now that I know, that I can ask even more questions as it will now take me less time. :-) Thanks.
    – Peter Grill
    Commented Nov 15, 2012 at 1:48
  • 1
    Glad to be of help :). Another tip, in case you didn't know: You can also use Ctrl+K for code and Ctrl+Q for block quotes.
    – doncherry
    Commented Nov 15, 2012 at 1:55
  • @doncherry: Excellent... So much faster...
    – Peter Grill
    Commented Nov 15, 2012 at 1:58

1 Answer 1

Reset to default
7

Interesting edge case, and one where various Markdown implementations disagree. That leaves the call to me, and I think the server-side version did the more correct thing here, so I've changed the preview to behave the same way. This fix is in the next build of the sites.

You must log in to answer this question.

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