Skip to content

parser: Check and prompt for empty patterns and region properties (fix crash) #3256

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

Merged
merged 3 commits into from
Apr 21, 2024

Conversation

JoeKar
Copy link
Collaborator

@JoeKar JoeKar commented Apr 16, 2024

By checking for broken syntax definitions in the parsing step we're able to prevent a possible recursion in the current highlighter engine. As a positive side effect we create more precise error messages for the user to help fixing the issues.

Fixes #3253

@JoeKar
Copy link
Collaborator Author

JoeKar commented Apr 16, 2024

@Andriamanitra:
Does this fit your expectation?

@taconi:
Can you please verify the change done in your prepared log definition?

Copy link
Contributor

@Andriamanitra Andriamanitra left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Andriamanitra:
Does this fit your expectation?

Yup, the behavior is exactly what I meant!

@JoeKar JoeKar force-pushed the fix/parser-empty-regex branch from ec3b738 to c71a55f Compare April 16, 2024 18:34
@taconi
Copy link
Contributor

taconi commented Apr 16, 2024

@taconi:
Can you please verify the change done in your prepared log definition?

It's perfect.

@JoeKar JoeKar merged commit c3052b4 into zyedidia:master Apr 21, 2024
@JoeKar JoeKar deleted the fix/parser-empty-regex branch April 21, 2024 18:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

crash when syntax file is not complete?
4 participants