allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dave Brondsema" <d...@brondsema.net>
Subject [allura:tickets] #7987 Standardize fenced blocks in markdown
Date Mon, 21 Sep 2015 15:49:02 GMT
- **labels**:  --> sf-current, sf-4



---

** [tickets:#7987] Standardize fenced blocks in markdown**

**Status:** open
**Milestone:** unreleased
**Labels:** sf-current sf-4 
**Created:** Mon Sep 14, 2015 05:18 PM UTC by Dave Brondsema
**Last Updated:** Mon Sep 14, 2015 05:18 PM UTC
**Owner:** nobody


Switch from our custom `FencedCodeProcessor` to the standard extension https://pythonhosted.org/Markdown/extensions/fenced_code_blocks.html
so that we can support \`\`\` style, and so that blank lines are not needed before and after
the `~~~~` blocks.  This will get us more closely aligned with the CommonMark standard, and
the syntax highlighting of the markdown editor, and the 

However, the format for denoting the language inside the block is different there than the
[CodeHilite](https://pythonhosted.org/Markdown/extensions/code_hilite.html) extension which
we are already using (and our current `~~~~` uses as well since it simply makes an indented
block).  So we'll have to figure out how to reconcile that.


---

Sent from forge-allura.apache.org because dev@allura.apache.org is subscribed to https://forge-allura.apache.org/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://forge-allura.apache.org/p/allura/admin/tickets/options.
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
Mime
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message