Fix Ruby syntax highlighting for predefined variables#3778
Merged
JoeKar merged 1 commit intomicro-editor:masterfrom Jun 20, 2025
Merged
Fix Ruby syntax highlighting for predefined variables#3778JoeKar merged 1 commit intomicro-editor:masterfrom
JoeKar merged 1 commit intomicro-editor:masterfrom
Conversation
JoeKar
approved these changes
Jun 19, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Ruby has a bunch of predefined variables that use special characters like quotes and backticks which completely break syntax highlighting. Adding rules like
constant: "[$]\""would not fix the issue because the string highlighting would still take priority, so I had to work around the issue by using a group with start (which contains the part to highlight) and end (which always matches).Current syntax highlighting:
With this PR applied:
These short names are rarely seen in serious code but they're extremely common in code golf so it would be nice to get this fixed.