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.

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

Closed
wants to merge 1 commit into from

Conversation

kiprobinson
Copy link

This adds support for strikethrough syntax (~~strikethrough~~) in MarkdownExtra.

Related issue: #211

@michelf
Copy link
Owner

michelf commented Oct 10, 2015

Thank you for this, but I don't intend to merge it. To me that shortcut syntax for <del> is not self-explanatory enough to the reader (using <del> directly clearer to me). It'd also feel strange to have that without having a shortcut for <ins>.

@michelf michelf closed this Oct 10, 2015
@robsonsobral
Copy link

@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 -- is much easier to understand. However, it's becoming a standard for non-techy people to write ~~something this way~~.

@michelf
Copy link
Owner

michelf commented Oct 10, 2015

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.

@taufik-nurrohman
Copy link

What about:

--del-- ++ins++

@michelf
Copy link
Owner

michelf commented Oct 11, 2015

@tovic The problem with --del-- is that -- is already widely in use for em dash (its 's old as the typewriter days). In the middle of a sentence it'll look like a dash to most people, not a strikethrough. You could maybe disambiguate with spacing, but in usage spacing is often inconsistent around dashes between authors so it's probably not a good idea.

@robsonsobral
Copy link

@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 ~~ and it's easier to embrace a standard than to fight one. Markdown is going to suffer of AFS.

*[AFS]: Androidish Fragmentation Syndrome

Ops. It looks like it is already!

@kiprobinson
Copy link
Author

"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.

@taufik-nurrohman
Copy link

Or with braces, like hyperlink (but not realy readable):

--[text to delete](@2015-10-13) ++[replacement text](@2015-10-13)

@tobiastom
Copy link

I think ~~ is widely used now (for example on GitHub), and I would like to see this added as well.

@MrPetovan
Copy link

~~ is used on Diaspora as well.

@michaelbutler
Copy link
Contributor

michaelbutler commented Apr 10, 2018

I agree that using ~~ for strikethrough is seems very common and I personally use it a fair amount (GitHub, Slack). @michelf have you changed your opinion on this?

@jeffmcneill
Copy link
Contributor

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants