Fixed and improved lex.vim (second update) #14
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This update fixes highlighting of start condition scope with pattern starting with
{
. A regex pattern that starts with a{
should not open a start condition scope.With this update and the previous, fixes were applied to correct the following issues:
<state>{ ... }
are not recognized correctly, leading to highlighting errors below it such as%%
not being highlighted.{...}
but otherwise its is not, which is inconsistent.%{...%}
) are not recognized and are not highlighted.%%
and in start condition scopes%{...%}
are not recognized in start condition scopes<state>{ ... }
.<*>
is not recognized and not highlighted.//
-comments are not always recognized and highlighted.ECHO
, which is inconsistent.“...”
are not highlighted in abbreviation definitions, whereas in patterns they are highlighted.%option
are highlighted inconsistently when used before or after initial code blocks (both places are valid).%s
and%x
are inconsistent or not highlighted at all when placed before initial code blocks.%top{
is not recognized, which should be the same as a%{
block, in principle any%name{
should be recognized.