Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

```xxx shouldn't end a fenced code block unless #51

Merged
merged 1 commit into from
Jan 29, 2015
Merged

```xxx shouldn't end a fenced code block unless #51

merged 1 commit into from
Jan 29, 2015

Conversation

mdiep
Copy link
Owner

@mdiep mdiep commented Jan 29, 2015

Fixes #50.

mdiep added a commit that referenced this pull request Jan 29, 2015
@mdiep
Merge pull request #51 from mdiep/nonwhitespace-after-fenced-code-block
316c848 
```xxx shouldn't end a fenced code block unless
@mdiep mdiep merged commit 316c848 into master Jan 29, 2015
@mdiep mdiep deleted the nonwhitespace-after-fenced-code-block branch January 29, 2015 01:17
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Possible Minor Bug: Trailing characters after closing ``` for GHFM fenced code block interpreted differently
1 participant
@mdiep