Need help? Check out our Support site, then


Brackets in Markdown Code

  1. Hey,
    It seems to be impossible to post short code snippets (i.e. surrounded with ticks: code) with brackets inside (i.e. <code>). While the ticks do work to render they code, anything in brackets disappears.

    This works on other sites (e.g. StackOverflow, etc.).

    Is there any way to achieve such a thing?

    The blog I need help with is blog.i3arnon.com.

  2. I tagged this thread for a Staff response. Please subscribe to it so you are notified when they respond. To subscribe look in the sidebar of this thread, find the subscribe to topics link and click it.

  3. Have you tried using the code shortcode, instead of the ticks? https://en.support.wordpress.com/code/posting-source-code/

    If you're still encountering this issue, please link me to a post containing the content (the outermost ticks or code shortcode, and the sourcecode content you want to display). You should use spaces before and after any brackets to prevent the text from being rendered as code.

  4. The code shortcode works, but it's only for separate lines of code.

    I need to write bits of code inside regular text. The ticks aren't even the issue as you can't use brackets without them as well.

    If you'll write Outer<Inner> then <Inner> disappears when the markdown is converted.

    I don't have any example in a post, since I can't publish one with this issue. What I've been doing is replacing the brackets with < and > (i.e. Outer<Inner>).

  5. @i3arnon -- Can you write the post as a draft? I'm happy to have a look.

  6. Oh.. I do have a post scheduled. I didn't know you can see that.

    I'm not sure how to link it. I hope this works: http://blog.i3arnon.com/2015/12/16/async-linq-to-objects-over-mongodb/

  7. Hi, @i3arnon

    When I got to this thread your post had already published, but I did some testing and was able to reproduce the error.

    Am I correct that you're using the HTML editor? I noticed that if I try to add brackets inside backticks in the HTML editor it got stripped out, but if I add them using the visual editor they get converted to the HTML entities instead. In this case the HTML entities display on the published post as well.

    I did find an open bug report on this, but it looks like this behaviour might be intentional. However, I'm adding the new information I've uncovered to that report and I'll let you know if I learn anything new.

    Meanwhile, can you please use the HTML entities instead, or use the visual editor when adding brackets inside markdown.

  8. The post is scheduled, but not yet publicly available. If you open the url without your account you'll get an error saying the post if not found.

    I've been using the text editor in the "old" WP Admin UI as it says in the markdown post:

    When writing with Markdown, make sure you always use the Text editor and not the Visual editor. Using the Visual editor may cause unexpected results with Markdown.

    https://en.support.wordpress.com/markdown/

    But lately I moved to writing on stackedit.io and publishing to wordpress.

    I can use the html entities (as I did in the recent post I published http://blog.i3arnon.com/2015/11/30/valuetask/) but it makes writing the post extremely hard to understand as it's not really markdown. The whole idea is to avoid writing HTML explicitly.

  9. I can use the html entities (as I did in the recent post I published http://blog.i3arnon.com/2015/11/30/valuetask/) but it makes writing the post extremely hard to understand as it's not really markdown. The whole idea is to avoid writing HTML explicitly.

    I completely understand this. Unfortunately, using HTML entities, or an alternative symbol with an explanation to readers that it should be substituted (which likely won't work on stackedit), are the only workarounds at this time, until our developers find out what is causing this.

    I will update you if I learn anything new.

  10. Are there any news on this?

  11. I'm sorry but the answer is not yet.

  12. Hi there,

    @timethief is correct that there's no news on this yet. If there are any new developments I will post an update in this thread.

  13. Any update on this issue?

  14. Nothing yet, no. As I said before, we'll update this thread when there is any new developments.

Topic Closed

This topic has been closed to new replies.

About this Topic