Github highlights escape sequences in raw strings.

[milesrout]

• Editor name and version: GitHub
• Platform: GitHub
• Color scheme: GitHub
• MagicPython version: GitHub

Github highlights escape sequences in raw strings.

[1st1]

Screenshot?

[milesrout]

[milesrout]

It should probably be the other way around---highlight in '\n'.join on line 60, don't highlight in r'\node...' on line 62.

[1st1]

Right, this is because lower-case 'r' raw strings are highlighted as regexp literals, for example: https://github.com/python/cpython/blob/master/Lib/http/cookies.py#L432. This isn't a new feature, r'' strings were highlighted as regular expressions in TextMate and Sublime Text (and thus GitHub) from the beginning.

You can use upper-case R prefix to get true raw-string highlighting:

a = R'aaa \n aaa'
a = r'aaa \n aaa'

I'd say it's too late to change this.

[milesrout]

Oh that's odd. I suppose that's justifiable. What about the lack of highlighting in non-raw strings?

[1st1]

What about the lack of highlighting in non-raw strings?

Well, this is just a convention now in many major editors. Lower-case r'strings' are highlighted as regexps, upper-case R'strings' are highlighted as actual raw strings.

upd: Sorry, misread the question :) @vpetrovykh answered it below.

[vpetrovykh]

The apparent lack of highlighting of '\n'.join is due to the color scheme choices that GitHub made, not to the lack of distinction in the language package. Basically, you would see the string being highlighted correctly with escaped characters in other editors (like Atom or Sublime Text) with richer color schemes.

[milesrout]

Hmm, non-ideal but doesn't look like the issue is on your end. Thanks.