[Code blocks]: Consolidate issues

[joshbruce]

This issue consolidates reference to issues and PRs related to code blocks. Issues will be closed, PRs will be left open, if no merge conflicts exist. See #956

[mercmobily]

Josh, this means that all of these issues are still valid and unresolved, even though they are marked as "closed". Right?

[joshbruce]

Pretty much. Given the issues span 5+ years I figured this was a good way to put them in one place to maybe put a checklist together to say, "We have tests in the current codebase that demonstrate this is no longer a problem." (I think the community was getting overwhelmed by the sheer number of open issues and maybe not knowing where to begin to contribute back.)

So, if you're looking to contribute, it might be pretty simple. If there's no test to measure the validity - then, it's not resolved - so, it may be as simple as writing a test, verifying it passes, then submitting the PR. If there's a test already - then we can remove it from the reference list.

Hope that makes sense.

[joshbruce]

@mercmobily: Shorter version. I don't know if they're resolved or not. Kinda hoping the community will help out on that score. One or two people can't do all the heavy lifting...as has been evidenced. So, I'm taking a somewhat different tack with things. :)

[jmduke]

I'm not sure if this is helpful (and I'd be happy to delete the comment if not), but here's a base case of how marked differs from most implementations:

https://johnmacfarlane.net/babelmark2/?text=%3Ch1%3ETest%3C%2Fh1%3E%0A++++++++++++%3Cp%3EShould+this+code+be+in+a+pre+block%3F%3C%2Fp%3E

This has bit me a couple times and I couldn't find specific settings that would resolve it (and though babelmark is testing against 0.2.6 I'm seeing the same behavior on 0.3.9.)

[Feder1co5oave]

To do list

toward 0.4.0:

• Preserve new lines (\n) within a <code> block #645 to be fixed to comply with CM. Duplicate Issue: when parsing code to <pre>, \n at the end lost #931. PR: Preserve trailing newlines in code fences #1011
• Tabs within code block are converted to 4 spaces? #644 not easily fixable (I believe WONTFIX? or 0.5.0)
• code block containing line break with new line starting with html fails #501 codespan not rendering. This issue is about html detection - see [Mixed content]: Consolidate issues #985
• fix backticks in inline code (fixes #312) #503 fix backticks in inline code (replaces #503, fixes #312) #1013 codespan bug (fixes A little puzzle about backtick quotes #759 Single backtick in inline code #312)
• grammar for inline codes is not good #1052 codespan bug following fix backticks in inline code (replaces #503, fixes #312) #1013
• marked 0.3.14 hangs on the attached file, worked in 0.3.9 #1058 code fence ends prematurely (ending fence must be on a new line)

toward 0.6.0:

• issues demanding a working/better default behavior when highlighting code: highlight.js code block missing hljs class  #393 Change to renderer options means highlight option no longer works #350 Don't throw an exception for unknown code block languages #810 Uncaught Error: Unknown language: "undefined" #803
  Possible solution: Some highlighters require class on a wrapping element to render properly #418 ?