Markdown syntax highlighting errors

[lemerchand]

Heyo, just grabbed a license the other day. I am very stoked about this project. Onto the not positive stuff :)

I popped open a .md file and started typing away and my results were something along these lines:

As you can see, many of the delimiters don't pick anything up. Some of them do, but only color the symbol. Any ideas what could be causing it?

I'm on 64-bit Windows 10, with a i7-3770k @ 3.5ghz and 32gb of RAM. No significant changes to the config file to report.

@

[zetashift]

I'm on Linux x64, bad specs and I have the same thing:

Using 0.5.9-nightly on commit 2b0be8b

[bryphe]

Hi @lemerchand ,

Thanks for logging this and sharing the screenshots - I'm able to reproduce these. At first I thought these might be theme-specific but unfortunately seem to not be tied to themes, but our actual syntax highlighting engine.

Will be helpful to have these cases for our next round of syntax-highlight improvements.

[zbaylin]

I think this might have to do with the combination of Markdown and HTML syntax highlighting. If I write HTML in a Markdown file, it seems to highlight just fine. However, if I write Markdown in an HTML file, it's treated as plain text (as it should be).

HTML in Markdown (.md) vs HTML in HTML (.html):

[Christopher-Hayes]

I've had similar issues across multiple file types. For example, adding a ; to the end of imports or adding a new import in JS/TS files will often turn off syntax highlighting for the rest of the file. I've also had seemingly "arbitrary" highlighting, like in the package.json below: