-
Notifications
You must be signed in to change notification settings - Fork 216
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.
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
STRIKETHROUGH doesn't work without FENCED_CODE_BLOCKS #131
Comments
Think there is just the addition of the "~" char to the list of special chars missing for option
|
vsch
added a commit
to vsch/pegdown
that referenced
this issue
Aug 22, 2015
fix Escaped Characters for disabled extensions sirthias#179 add StrikeNode has isClosed() member sirthias#178 fix Reference node includes trailing blank lines sirthias#177 fix Setext headers not allowing blanks after --- or === sirthias#176 fix CaptionNode not having source index range set sirthias#175 add ATXHEADERSPACE extension to require a space/tab after # in AtxHeaders sirthias#144 add RELAXEDHRULES extenstion to relax requirement of a blank line after horiz. rule. sirthias#129 fix STRIKETHROUGH extension did not add ~ to special characters. sirthias#131
vsch
added a commit
to vsch/pegdown
that referenced
this issue
Aug 22, 2015
fix Definition Lists sirthias#180 fix Escaped Characters for disabled extensions sirthias#179 add StrikeNode has isClosed() member sirthias#178 fix Reference node includes trailing blank lines sirthias#177 fix Setext headers not allowing blanks after --- or === sirthias#176 fix CaptionNode not having source index range set sirthias#175 add ATXHEADERSPACE extension to require a space/tab after # in AtxHeaders sirthias#144 add RELAXEDHRULES extenstion to relax requirement of a blank line after horiz. rule. sirthias#129 fix STRIKETHROUGH extension did not add ~ to special characters. sirthias#131
Merged
Closed by #181. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Curiously, the
STRIKETHROUGH
extension doesn't appear to work on its own in 1.4.2. It only works if theFENCED_CODE_BLOCKS
extension is also active.The text was updated successfully, but these errors were encountered: