Pretty funny actually - compare carefully the input and output 
Looks like some of the prefix whitespace is expanded on lines #2 and later.
AI-generated summary
The discussion revolves around the font and spacing used in code areas. swisspol points out that the input and output fonts seem different, with some prefix whitespace being expanded on lines #2 and later. swisspol shares a test case using Babelmark to demonstrate the issue.
sam suggests that Markdown handles this scenario correctly and that the current implementation is doing the right thing. However, sam is torn between preferring a monospace font for markdown textareas, which might make the site seem “more computery” and “less friendly.” The decision is ultimately up to @codinghorror.
What does babelmark say: John MacFarlane - babelmark 2
Here’s the test I’m using
----A----x----B----x----x----HEAD
\
x----x----C
And here are the test results.
Just realize the test I pasted above doesn’t render right when viewed in the topic, the source is actually:
Markdown seems pretty unanimous about how to treat that 
and we are doing the right thing.
If you want a monospace font in your editor go for that, by adding a site customization.
I am torn, my personal pref is for monospace markdown textareas, but there is a strong argument monospace makes this “more computery” and “less friendly”. Ultimately this is a decision that is up to @codinghorror. Even cooking Stack Exchange uses monospace (but on the other hand they do not display stuff side by side).
----A----x----B----x----x----HEAD
\
x----x----C
1 « J'aime »
This topic is now closed. New replies are no longer allowed.
We are not interested in changing the font of the editor to monospace