-
Notifications
You must be signed in to change notification settings - Fork 262
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
html syntax highlight misses on single tags #1196
Comments
@rnpnr , I think, this could be closed. |
Otherwise, added as a commit to https://git.cepl.eu/cgit/vis/vis/commit/?id=5629ca0091c2 and after testing, I will submit it upstream. |
Just submitted: orbitalquark/scintillua#114 |
This can stay open for now. We can bulk pull in the changes once its resolved upstream. |
Ok, got some good help from orbitalquark. There are tags that handle this case here but are not in the themes. I will post a PR soon that will solve this issue more correctly, but might first spend some time looking for similar issues with tags in other lexers that are not handled by the themes. The patch I suggested when I opened this is not correct. What is needed is something like this in the themes:
or
or how ever seems more appropriate. These are just the ones that I noticed so far, mainly because both were not getting styled. |
Oh I see now; those should actually be available to style but are just not included in the default themes. This line: Line 287 in a7aac10
replaces the I don't have a good way of indicating all possible combinations in the themes besides just adding them and letting people tweak for their own preferences. |
I had hoped to prepare a more expansive set of changes. #1197 will have to do for now until I have more time. |
Single html tags like hr, input, and meta (etc) aren't getting highlighted.
My lua knowledge is pretty sparse, but here's a work-around that is working for me so far:
I'm running vis built from git HEAD on alpinelinux edge.
I can also report this upstream to scintillua if that is desired.
The text was updated successfully, but these errors were encountered: