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

Support for strikethrough #221

Closed
rfscotteb opened this Issue May 31, 2013 · 5 comments

Comments

Projects
None yet
4 participants
@rfscotteb
Copy link

rfscotteb commented May 31, 2013

We formally (and politely) request support for strikethrough. We use Bitbucket, and they indicated we should make this request here. Thank you for your time and consideration!

@waylan

This comment has been minimized.

Copy link
Member

waylan commented Jun 7, 2013

Thanks for your polite request. Unfortunately, It is not clear to me whether you are requesting that striketrough be added as a default behavior of Markdown, or as an optional extension. As stated in our project goals, the default behavior of Python-Markdown should not deviate from the Markdown syntax rules. As strikethrough is not mentioned in the rules, we will not be adding it to Python-Markdown as a default behavior.

If you are requesting an extension, that might be considered (although extremely unlikely). Why does it need to be shipped with Python-Markdown? Why can't it exist as a third party extension? In fact, how is some new markup better that just using inline raw html (<del>some text</del>)? There would hardly be any saved typing there. And then consider the following (from the inline html rules):

For any markup that is not covered by Markdown’s syntax, you simply use HTML itself. There’s no need to preface it or delimit it to indicate that you’re switching from Markdown to HTML; you just use the tags.

In my opinion, the simplicity of using raw del tags isn't enough motivation for me to implement and maintain an extension. Especially when considering the markdown philosophy above. Of course, you're free to disagree with me. But that's why we have an Extension API. You can implement whatever changes to the syntax that you want.

In fact, if you want to write the extension yourself, you might want to take a look at this tutorial which steps you through the process of creating an extension. It happens to implement strikethrough, among other things. You are free to take that code and do what you want with it. I only wrote if for demonstration purposes and have no need to use it or desire to maintain it.

@waylan waylan closed this Jun 7, 2013

@rfscotteb

This comment has been minimized.

Copy link
Author

rfscotteb commented Jun 7, 2013

Hi! Thank you so much for your response. I completely understand your position. The reason I was making this request is because Bitbucket uses your library to parse Markdown and they have indicated they won't use any extensions either. In addition, the <del> syntax does not work in Bitbucket.

I will push Bitbucket to support some extensions or at least the <del> syntax.

Thanks again!
Rob

@Friz-zy

This comment has been minimized.

Copy link

Friz-zy commented Apr 13, 2015

Hello guys,
2015 on calendar, maybe you can add support for github flavored markdown?

Goal for example:
Input: ##~~Hard~~Hand way
Export: ~~Hard~~Hand way
Even at wiki it has another convention...

@waylan

This comment has been minimized.

Copy link
Member

waylan commented Apr 13, 2015

@Friz-zy, not sure what the calendar year has to do with anything. We will change the default behavior when the syntax rules change (granted, that seems highly unlikely). Of course, you can write your own extensions which change the behavior in any way you want. In fact, many have. Perhaps you will find an existing extension that meets your needs.

@n37r06u3

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment