This is because the hilite code is very simple and doesn't make sure there is a match before setting the fg color to ID_SINGLE_STRING. The solution would be to make the hilite logic check for a pair before coloring, if one is found then it will color.
This is because the hilite code is very simple and doesn't make sure there is a match before setting the fg color to ID_SINGLE_STRING. The solution would be to make the hilite logic check for a pair before coloring, if one is found then it will color.
Single quotes are only highlighted until the EOL. Since in most langs single quotes are either chars or single line strings.
Back quote is mostly unchanged but it will match with a closing single quote since the use of `foo' is common.
Double quote is consider single line as well unless the is a backslash followed by a newline char.
Commits 7f66ad51f783ff56d7f281e7af053c7f99690180 and 867a2e9e84bc4f51954dce37ed57855fc453c8af add in better highlighting.
Single quotes are only highlighted until the EOL. Since in most langs single quotes are either chars or single line strings.
Back quote is mostly unchanged but it will match with a closing single quote since the use of `foo' is common.
Double quote is consider single line as well unless the is a backslash followed by a newline char.
Kevin "The Nuclear" Bloom
This is because the hilite code is very simple and doesn't make sure there is a match before setting the fg color to ID_SINGLE_STRING. The solution would be to make the hilite logic check for a pair before coloring, if one is found then it will color.
Commits
7f66ad51f7and867a2e9e84add in better highlighting.Single quotes are only highlighted until the EOL. Since in most langs single quotes are either chars or single line strings.
Back quote is mostly unchanged but it will match with a closing single quote since the use of `foo' is common.
Double quote is consider single line as well unless the is a backslash followed by a newline char.