You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Dave Brondsema <da...@brondsema.net> on 2015/09/14 19:18:25 UTC
[allura:tickets] #7987 Standardize fenced blocks in markdown
---
** [tickets:#7987] Standardize fenced blocks in markdown**
**Status:** open
**Milestone:** unreleased
**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.
[allura:tickets] #7987 Standardize fenced blocks in markdown
Posted by Igor Bondarenko <je...@gmail.com>.
- **status**: in-progress --> review
- **Comment**:
Closed #882. `ib/7987`
TBH, I was surprised it worked with minimal changes. Make sure I did not miss something :)
---
** [tickets:#7987] Standardize fenced blocks in markdown**
**Status:** review
**Milestone:** unreleased
**Labels:** sf-current sf-4 42cc
**Created:** Mon Sep 14, 2015 05:18 PM UTC by Dave Brondsema
**Last Updated:** Fri Dec 25, 2015 09:17 AM UTC
**Owner:** Igor Bondarenko
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.
[allura:tickets] #7987 Standardize fenced blocks in markdown
Posted by Dave Brondsema <da...@brondsema.net>.
- **labels**: sf-current, sf-4, 42cc --> sf-4, 42cc
---
** [tickets:#7987] Standardize fenced blocks in markdown**
**Status:** closed
**Milestone:** unreleased
**Labels:** sf-4 42cc
**Created:** Mon Sep 14, 2015 05:18 PM UTC by Dave Brondsema
**Last Updated:** Wed Jan 06, 2016 05:08 PM UTC
**Owner:** Igor Bondarenko
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.
[allura:tickets] #7987 Standardize fenced blocks in markdown
Posted by Igor Bondarenko <je...@gmail.com>.
- **labels**: sf-current, sf-4 --> sf-current, sf-4, 42cc
- **status**: open --> in-progress
- **assigned_to**: Igor Bondarenko
---
** [tickets:#7987] Standardize fenced blocks in markdown**
**Status:** in-progress
**Milestone:** unreleased
**Labels:** sf-current sf-4 42cc
**Created:** Mon Sep 14, 2015 05:18 PM UTC by Dave Brondsema
**Last Updated:** Mon Sep 21, 2015 03:49 PM UTC
**Owner:** Igor Bondarenko
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.
[allura:tickets] #7987 Standardize fenced blocks in markdown
Posted by Dave Brondsema <da...@brondsema.net>.
- **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.
[allura:tickets] #7987 Standardize fenced blocks in markdown
Posted by Dave Brondsema <da...@brondsema.net>.
- **status**: review --> closed
- **Reviewer**: Dave Brondsema
- **Comment**:
Excellent! I tested every combination of code blocks and language specifiers I could think of and they all work, I love it! This enables lots of nice formatting features:
* backticks not just tildes
* language specifier can go in backtick/tilde line, matching CommonMark and github format
* no blank line required before and after
* can nest backtick and/or tilde lines within a block (if different type/number of them)
* code blocks work immediately before or after lists
---
** [tickets:#7987] Standardize fenced blocks in markdown**
**Status:** closed
**Milestone:** unreleased
**Labels:** sf-current sf-4 42cc
**Created:** Mon Sep 14, 2015 05:18 PM UTC by Dave Brondsema
**Last Updated:** Tue Jan 05, 2016 04:07 PM UTC
**Owner:** Igor Bondarenko
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.