[Markdown] Ligatures that start with < aren't rendering

[appsforartists]

Ligatures that begin with < are rendering as two characters in Markdown. They will draw correctly if placed immediately after a backtick or in in a syntax like TypeScript.

[appsforartists]

I'm using Inconsolata, but I can reproduce with Fira Code too.

[keith-hall]

I guess this is due to

Packages/Markdown/Markdown.sublime-syntax

Lines 508 to 513 in 2027e62

	bracket:
	- match: '<(?![a-z/?\$!])'
	comment: |
	Markdown will convert this for us. We match it so that the
	HTML grammar will not mark it up as invalid.
	scope: meta.other.valid-bracket.markdown

. It could be solved by removing the meta scope, but I think it is useful to have the scope there.

[appsforartists]

I bet there's an exclusion character in whatever flavor of regex sublime uses. You could presumably whitelist <= and <- without affecting HTML parsing.

[FichteFoll]

An option would be to match these two specifically before this match to ensure they end up in the same token.

@keith-hall iirc tokenization happens regardless of whether a scope is assigned or not, so removing the meta scope wouldn't help.

[deathaxe]

Looks fixed in ST 3207

[wbond]

@appsforartists Are you still seeing this with the latest version of Sublime Text 3?

[appsforartists]

I can reproduce the original issue in 3211.