Weird markdown syntax highlighting

[JohnONolan]

Accidentally discovered this bug while reporting #958

When typing the same char lots of times, eg: dddddddddddddd - Markdown thinks it is a link, and gives it a class of .cm-link (this should not happen)

[JohnONolan]

Another false .cm-link insertion in this context

[ErisDS]

Can we have a markdown label, so we can track all of these? The markdown mode in CodeMirror is so different to the regex parser we use in showdown, the best way to fix all these is going to be to unify them.

[sebgie]

The first problem ('ddddddd') is caused by Github flavored markdown (gfm.js: line 66). It matches a hex number with more than 7 characters. Is Github flavor needed?

[sebgie]

Second problem is codemirror behaviour where it interprets the first [every ... world] as a broken link.

[JohnONolan]

@ErisDS You will see we have an "editor" label already to track all of these ;)

[ErisDS]

@JohnONolan lol when did that happen... but cool.

@sebgie, we are using certain features of gfm, like auto linking, so if we turn it off we lose features, and if we turn it on we get oddness like this.

With regards to [every ... world] being a broken link, it depends on the markdown spec, and your interpretation of it. In markdown [...] is the first part of a link. If you want to use this syntax in text you should escape it... @JohnONolan should have written \[every ... world\]. CodeMirror is entirely correct in determining this as a broken link. But I'll be the first person to say that this is a completely crap user experience.

We're absolutely pushing the boundaries of the markdown specification. We are using parts of the GFM spec, and we are in part defining our own 'Haunted Markdown' spec. At the moment, we're doing this using existing tools and it's absolutely not the best solution.

Long term we want to formalise our spec and build our own tools.
Short term we need to make decisions about where these issues are acceptable, and where we really need to fix them as best we can.

Unfortunately, I'm not sure there is any quick fixes for these issues without forking / writing our own CodeMirror mode, and even that is more of a 0.4 quick fix, as opposed to something we can hack in for 0.3.2.

[JohnONolan]

#wontfix