-
Notifications
You must be signed in to change notification settings - Fork 3.4k
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 broken #286
Comments
I had the same issue, but only when using marked as described under "Pro level", so I investigated a bit: This works as expected:
and renders as:
When using the lexer and parser separately with a custom renderer, the following code
ignores the strikethrough and produces:
As far as I can see, the
outputs So my issue here is that I have no idea if that is the same issue of @bsaelim, but it may be an explanation. |
I think the issue as I described it may be resolved by pull request #1015. |
I confirm #1015 solves this issue, but it has a performance problem if you call marked several times. For now, remember to do something like this: var marked = require('marked');
var myRenderer = new marked.Renderer();
marked.setOptions({ renderer: myRenderer });
var tokens = var tokens = marked.lexer('~~strikethrough~~');
console.log(marked.parser(tokens)); outputs <p><del>strikethrough</del></p> I'm closing this in favor of the linked PR. |
some textis no longer working.The text was updated successfully, but these errors were encountered: