-
Notifications
You must be signed in to change notification settings - Fork 39
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Highlighting of split #110
Comments
Thanks @maros! I think this is the most important Perl syntax highlighting issue in Perl textmate grammars. I'll elaborate: There are a fixed set of words and characters that will start a regex if followed by a slash. Some examples (using github highlighting since it uses the same grammars): print "good" if /foo/;
print "good" unless /foo/;
print "good" if( /foo/ && /bar/ || /baz/ );
my $result = [ split /foo/, $string ]; # Broken highlighting This is because of one TextMate line that specifies that That single line of TextMate generates lots of issues. Examples: Regexes start after Regexes don't start after Regexes don't start after Regexes don't start after Regexes incorrectly trigger on //= on newlines: textmate/perl.tmbundle#29 Regexes don't start after I think a great start for improving syntax highlighting would be overriding the default highlighting and fixing just this one line. TextMate grammars will never be perfect, but this would be a great start. |
Hi @maros, this is now resolved. In addition to highlighting regexes correctly after Additionally, I made a variety of other fixes while I was in there. For example, although |
The highligting of certain split statements with regular expressions is not correct.
perl-navigator 0.5.1 2023-01-16
vscodium 1.85.1
perl v5.38.0
added this ticket just for reference once you decide to override default syntax highlighting
The text was updated successfully, but these errors were encountered: