-
Notifications
You must be signed in to change notification settings - Fork 530
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
Adding support for ~~strikethrough~~ in MarkdownExtra #212
Conversation
Thank you for this, but I don't intend to merge it. To me that shortcut syntax for |
@michelf , I tend to disagree simply because I've seen this a lot here in Brazil. On facebook, on twitter... I always thought it's an confusing syntax. Something like |
Perhaps I should revise this decision some day. But, right now, all I can say is that the syntax doesn't convey anything to me when I read it, and I have yet to see this used in the wild. It has some potential to be confusing with the fenced code block syntax too because the marker is quite similar. |
What about:
|
@tovic The problem with |
@tovic , I agree that makes a lot more sense. I suggested it to @michelf years ago by e-mail. But besides the reason he gave, people are already using *[AFS]: Androidish Fragmentation Syndrome Ops. It looks like it is already! |
"I have yet to see this used in the wild". Well, GitHub-flavored markdown uses it. That's how I was able to use strikethrough in the pull request. :) Use it or don't, I don't care... I just implemented it for my own site and thought I'd submit a pull request in case you were interested. |
Or with braces, like hyperlink (but not realy readable):
|
I think |
|
I agree that using |
It is time for some kind of strikethrough support in Markdown Extra. The exact syntax does not matter to me. Some kind of syntax is what matters. Why must we resort to html for this when Markdown is supposed to make this easier? |
This adds support for
strikethroughsyntax (~~strikethrough~~
) in MarkdownExtra.Related issue: #211