Add support for long options to Batchfile lexer #1626
Merged
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
|
@fireattack Thanks for reporting this and sorry it took a bit of time to get back to you. I think this PR fixes the issue :) |
jneen
approved these changes
Nov 9, 2020
|
@fireattack This will be part of the next release of Rouge, v3.25.0. That's scheduled for release later today/tomorrow (depending on your time zone). Thanks again for filing the issue! 🎉 |
|
Awesome, thanks for the hard work! |
mattt
pushed a commit
to NSHipster/rouge
that referenced
this pull request
May 19, 2021
The Batchfile lexer does not support 'long options' (i.e. options that begin with --). This commit adds support for that.
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.
The Batchfile lexer does not support 'long options' (i.e. options that begin with
--). This PR adds support for that.It fixes #1599.