lsh: add Bash, Zsh, Python and JavaScript highlighting#791
Open
barkure wants to merge 1 commit intomicrosoft:mainfrom
Open
lsh: add Bash, Zsh, Python and JavaScript highlighting#791barkure wants to merge 1 commit intomicrosoft:mainfrom
barkure wants to merge 1 commit intomicrosoft:mainfrom
Conversation
Author
|
@microsoft-github-policy-service agree |
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
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.
This adds initial LSH syntax highlighting support for:
It also updates Markdown fenced code block routing so that:
bash,sh, andshelluse Bash highlightingzshuses Zsh highlightingpython/pyuse Python highlightingjavascript/js/jsx/mjs/cjsuse JavaScript highlightingScope
This is a lightweight LSH-only change with no new dependencies.
The changes are limited to syntax definitions and highlighting fixtures:
Validation
cargo test -qNotes
The new rules are intentionally simple and follow the style of the existing LSH definitions.
They focus on the main token classes already used elsewhere in the project, such as:
If you would prefer this to be discussed as a feature request first, I am happy to open an issue and rework the PR accordingly.