One of the answers here was mangled by the markdown engine. Several people noticed, so it wasn't just my browser.

The original text was [sp][sp][sp][sp]include <string.h> ([sp] = space)

This rendered as include

When I edited it to #include <string.h> it was fine. I checked, it wasn't a tabbing problem.

Here it is, but it appears normal, don't know why it was broken on that other page:

include <string.h>
share|improve this question
    
I cannot reproduce it, here. The only case the string is mangled is when I indent include <string.h> with a tab, and then 3 (or 4) spaces; in that case, the code line is not shown with a different background, and <string.h> doesn't appear. –  kiamlaluno Sep 3 '10 at 16:30
    
I can confirm the issue on SO: I tried to write include <string.h> with four spaces at the beginning, and `<string.h> was not shown; the code line was not rendered with a different background either. –  kiamlaluno Sep 3 '10 at 16:34
add comment

1 Answer

up vote 3 down vote accepted

Looking at the revision and its source, it looks like a simple linebreak issue. A blank line is necessary after normal text to use a code block.


This line is normal text. This is a line immediately afterwards with 4 spaces in front. It has to test.

This line is normal text again.

This is a proper line with 4 spaces in front. It has <something> to test as well.

Source of the above:

This line is normal text.
    This is a line immediately afterwards with 4 spaces in front. It has <something> to test.


This line is normal text again.

    This is a proper line with 4 spaces in front. It has <something> to test as well.
share|improve this answer
    
I left a blank line before and after the code line. This is the result. –  kiamlaluno Sep 3 '10 at 16:38
    
Hmmm, I doubt that, assuming the 2nd revision was the troublesome source? (Indeed, the 1st revision that you mentioned gave trouble too, but that's not what Eric is describing?) –  Arjan Sep 3 '10 at 16:38
    
@kiamlaluno My screenshot doesn't seem to have this issue. –  Grace Note Sep 3 '10 at 16:40
    
@Grace Note: I find strange that we get different results. Did you try on SO? –  kiamlaluno Sep 3 '10 at 16:42
    
@kiamlaluno That's the only way to properly test. I used an answer on that same SO question to test this, and I'm not able to replicate it when it is properly formatted. –  Grace Note Sep 3 '10 at 16:43
    
Any browser differences then? –  Arjan Sep 3 '10 at 16:44
    
@Arjan I'm not seeing anything wrong in that revision. The history it is visible, and in this replication it is also visible. –  Grace Note Sep 3 '10 at 16:45
    
I'm running IE8 on XP. –  Grace Note Sep 3 '10 at 16:46
    
Never mind. There was a strange character at the beginning of the line; When the cursor was at the beginning of the line, and I pressed the cursor right key, the cursor didn't move to the right side, but it did move when I pressed it the second, and third time. I guess there was a hidden character. –  kiamlaluno Sep 3 '10 at 16:50
add comment

You must log in to answer this question.

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