Edit - Meta Stack Exchange

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*

Rev

Thanks for your answer. While you were answering, I also updated my question, sorry. My main point is: The preview renders everything as expected, so I didn't notice the wrong output until several days later. (I accidentally deleted this important piece of information in the first edit of my question.)

Hendrik Vogt
– Hendrik Vogt

2011-02-01 15:23:46 +00:00
Commented Feb 1, 2011 at 15:23
That was really fast! Thank you very much indeed, this is exactly what I wanted, namely that my examples now look just as broken in the preview as in the final version. And yes, it is great to make users aware of problems with their markdown as soon as possible. Thanks again!

Hendrik Vogt
– Hendrik Vogt

2011-02-01 19:01:16 +00:00
Commented Feb 1, 2011 at 19:01
I just tested it in the sandbox, and it works great. Thanks a lot!

Hendrik Vogt
– Hendrik Vogt

2011-02-02 09:24:54 +00:00
Commented Feb 2, 2011 at 9:24

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »