Several scope names per pattern

[pchaigno]

Some of the patterns in the grammar file have several scope names:

babel-sublime/JavaScript (Babel).YAML-tmLanguage

Lines 1270 to 1275 in a9a908f

	'1': {name: meta.tag.jsx punctuation.definition.tag.begin.jsx}
	'2': {name: meta.tag.jsx entity.name.tag.jsx}
	end: (</)(\2)(>)|(/>)
	endCaptures:
	'1': {name: meta.tag.jsx punctuation.definition.tag.begin.jsx}
	'2': {name: meta.tag.jsx entity.name.tag.jsx}

I don't know whether this works in Sublime Text, but when using this grammar to highlight files on GitHub.com (cf. github-linguist/linguist#4223), it causes HTML highlighting to break inside JSX files, as shown in this Ligthshow example.

[Thom1729]

Can you provide more context on how you are using babel-sublime outside Sublime? I am currently working on a complete replacement of the syntax definition with a new .sublime-syntax, and this will probably not be compatible with tools other than Sublime.

[pchaigno]

We use a fork of babel-sublime in Linguist to highlight JSX code on GitHub.com (cf. github-linguist/linguist#4223). Linguist doesn't support .sublime-syntax unfortunately (cf. github-linguist/linguist#3214).

[Thom1729]

Unfortunately, I don't think it will be practical to maintain the old tmLanguage definition going forward. It's very badly out of date, and .sublime-syntax is capable of providing much better highlighting. If Linguist is using a fork, then it probably makes the most sense to maintain that fork to serve Linguist's needs without worrying about divergence from babel-sublime.