Add an Alloy lexer #892
Merged
Add an Alloy lexer #892
Conversation
This file contains 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
alecthomas
approved these changes
Nov 25, 2023
|
Ah the README change conflicts with your previous PR I think. |
|
It sure does. I will rebase. |
Signed-off-by: Danila Fedorin <danila.fedorin@gmail.com>
Signed-off-by: Danila Fedorin <danila.fedorin@gmail.com>
DanilaFe
force-pushed
the
alloy-lexer
branch
from
93fc03d to
1fd8424
Compare
|
There, ready for your review again and conflict-free :) |
# for free
to join this conversation on GitHub.
Already have an account?
# 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 PR adds an Alloy lexer, based on the Pygments one. This was generated using the following command:
python3 _tools/pygments2chroma_xml.py \ pygments.lexers.dsls.AlloyLexer \ > lexers/embedded/alloy.xmlOnce again it looks like i'm the only person that needs this, so there's no corresponding issue.