In my answer here I wanted to prevent syntax highlighting as described in here

But it's not working. Not working means: Even though I said

<!-- language: lang-none -->

before the start of the block, a couple of characters are still highlighted, probably because of the Python tag to the question.

Also thought this (rerendering after in-page edit) might be an issue, so that only I see the wrong highlighting. But that's marked as fixed.

Is it my fault or a bug or none but expected behaviour? If the latter, why would we want this?

  • @Tim: Thanks! Any chance to include that in the documentation. The phrasing is not clear to me, and there's no example showing how these tags are included in surrounding text. Also, if you put your comment in an answer I can accept it.
    – cfi
    Nov 6 '12 at 12:25
  • Yeah, I had thought this had come up before so I was searching for a duplicate first, but was having a hard time finding something. Answered now. As far as the documentation goes, I can't personally update that, but I agree that expanding the example a little might help here.
    – Tim Stone
    Nov 6 '12 at 12:40
  • Felt the same way, but after reading 20 questions about broken highlighting, I gave up. How are these documentation updates handled? Should I open up a feature-request question for that change?
    – cfi
    Nov 6 '12 at 12:52
  • Someone may act on this post if they feel it worthwhile, but posting something with feature-request editing-help should also be acceptable.
    – Tim Stone
    Nov 6 '12 at 12:55
  • Appreciate the advice! Explicit is better than implicit - can't expect the busy folks to extract implications from some comments, so I've posted here
    – cfi
    Nov 6 '12 at 14:13

You need to make sure that you have a newline before the language hint, just like you need a newline before a code block. I've gone ahead and fixed your post now.

You must log in to answer this question.

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