-
Notifications
You must be signed in to change notification settings - Fork 42
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
Issue: highlighting breaks with long object lines #59
Comments
rejdeboer
changed the title
Issue: highlighting breaks with long logic lines
Issue: highlighting breaks with long ${{ }} lines
Mar 14, 2024
rejdeboer
changed the title
Issue: highlighting breaks with long ${{ }} lines
Issue: highlighting breaks with long object lines
Mar 14, 2024
Yeah, I'm seeing the same on this fixture: swagger: "2.0"
paths:
/pet/adding-new-pets/testing-thelong-size-path-name/testing-thepath/testingthepathnameggggggggggggggggggggggggglllllllllllllla: {} The worst thing is that the lexical analysis stops on long line and doesn't continue any further. block mapping pair of openapi: 3.1.0
paths:
/pet/adding-new-pets/testing-thelong-size-path-name/testing-thepath/testingthepathnamegggggggggggggggggggggggggllllllllllllll: {}
test: 3 |
This was referenced Apr 11, 2024
This has already been addressed in tree-sitter-grammars#6 and is waiting for a release in tree-sitter-grammars#15 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What is the issue?
Whenever you have lines that contain a lot of logic, like if-statements and variables, the syntax highlighting below that logic line breaks. This problem is triggered when writing logic lines that are longer than 128 characters
Steps to reproduce
Working example
nvim screenshot:
Broken example (add one more e)
nvim screenshot:
What behavior is expected?
The syntax highlighting doesn't break when using lines that are longer than 128 characters
What have I already tried?
:set synmaxcol 0
:syntax sync fromstart
The text was updated successfully, but these errors were encountered: