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
Terraform comments are highlighted as errors #2094
Labels
A-lexing
area: changes to individual lexers
Comments
Relates the the following issue raised on Mkdocs Material:squidfunk/mkdocs-material#3696 |
Just checked, reproduces on |
amitkummer
added a commit
to amitkummer/Pygments
that referenced
this issue
Mar 27, 2022
The `blockname` state did not have a `#pop` after it's only rule, which caused outputting errors in pygments#2094. Instead of adding a `#pop`, I merged the `blockname` state with the rule that uses it, to achieve the exact same lexing logic, but without another state in the lexer.
amitkummer
added a commit
to amitkummer/Pygments
that referenced
this issue
Mar 27, 2022
Anteru
pushed a commit
that referenced
this issue
Mar 27, 2022
* Merge unneeded state with it's parent rule The `blockname` state did not have a `#pop` after it's only rule, which caused outputting errors in #2094. Instead of adding a `#pop`, I merged the `blockname` state with the rule that uses it, to achieve the exact same lexing logic, but without another state in the lexer. * Add test for #2094 * Regenerate tokens for previous tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The following valid Terraform code gets highlighted with errors:
pygmentize -g .\main.tf -f html
Both comments
# (1)
and# (2)
are highlighted as errors:<span class="err"> # (1)</span>
/<span class="err"> # (2)</span>
.Using using the following version:
The text was updated successfully, but these errors were encountered: