Context Navigation

Changes between Initial Version and Version 1 of Ticket #2145, comment 3

-                      initial
+                      v1
 And different problem. It looks that current JS highlighting rules doesn't
 include case for regexps at all. Finding regular expression isn't hard,
 scan non-comments and non-strings for /\/.+(?<!\\)\//[igmy]* regexp.
+scan non-comments and non-strings for `/\/.+(?<!\\)\//[igmy]*` regexp.
 As i understand problem is that / can be both division operator and beginig of the regexp. Simples difference is that before / in regexp we need to have: { or ( or [ or , or ; or =  or other oprator (+ - / & && || | ^ ~). But befor division operator we need to have ) or digit or letter or dot. (We inore of course whitespaces in the match)
+As i understand problem is that / can be both division operator and beginig of the regexp. Simples difference is that before / in regexp we need to have: { or ( or [ or , or ; or =  or other oprator (`+ - / & && || | ^ ~`). But befor division operator we need to have ) or digit or letter or dot. (We inore of course whitespaces in the match)
 .+ becuase 'var a = //;' is illegal as this is empty regexp (would always match), and actually it is a commened ';'  string
+`.+` becuase `'var a = //;'` is illegal as this is empty regexp (would always match), and actually it is a commened `';'`  string