search

mmarkdown / mmark

Mmark: a powerful markdown processor in Go geared towards the IETF
https://mmark.miek.nl
Other
480 stars 45 forks source link

Is the lack of the NoIntraEmphasis parser Extension intentional? #143

Closed dwaite closed 2 years ago

dwaite commented 3 years ago

When writing specifications, it is not uncommon to deal with parameters which are camel_cased_strings. By default, mmark will render these as camelcasedstrings because of the lack of the NoIntraEmphasis extension.

I didn't see any option or comment regarding why this extension is the one extension missing from gomarkdown's CommonExtensions definition within mmark's parser.

Would it be possible to add this extension, even if as an option which needs to be enabled within the title block?

miekg commented 3 years ago

Not intentionally, so we might as well add it. The only problem now becomes if this would be a backwards incompatible change?

miekg commented 2 years ago

solved with #147, if that doesn't show up any problems, we should remove the flag, default to added the extensions and call it a day.

dwaite commented 2 years ago

@miekg Just to make sure it is clear: this still defaults to the same behavior - its an opt-out by -intra-emphasis=false

miekg commented 2 years ago

Ah..we might want to flip that (soon) and wait for any fall out

On Fri, 5 Nov 2021, 18:02 David Waite, @.***> wrote:

@miekg https://github.com/miekg Just to make sure it is clear: this still defaults to the same behavior - its an opt-out by -intra-emphasis=false

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/mmarkdown/mmark/issues/143#issuecomment-962062618, or unsubscribe https://github.com/notifications/unsubscribe-auth/AACWIWZZNDG632SXACDQWWDUKQL2VANCNFSM5CYIUNRA .