-
Notifications
You must be signed in to change notification settings - Fork 130
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
Font-lock block literal spilling out #60
Comments
Modifies `yaml-font-lock-block-literals` to initialize `min-level` to `((current-indentation) - yaml-indent-offset)`
Well this is funny. The block literal code existed for quite some time in the font locking rules, but wasn't applied properly, so I fixed that in my recent commits. Apparently this reveals that its logic isn't perfect. Your PR attacks the right place, but you'd need to understand the existing logic to make progress on this problem. |
Yeah, I spent a bit of time last night dowsing the variable space to try to wrap my brain around the logic to no avail. I hate that this isn't working. I'm using YAML to persist my exams and quizzes, so I make extensive use of block literals. For the time being, I've reverted to Thanks for the module all the same! |
Problem
When leaving a block literal to continue a dictionary definition, the rest of the dictionary is font-locked as a string.
This implies that the rest of the dictionary is part of the string literal, which is not true.
This is new behavior.
Current Solutions
The addition of comment symbols seems to "fix" the issue.
However, when the comment symbol is deleted, the font-lock spills back in:
The text was updated successfully, but these errors were encountered: