Improve listing of lexers in README file #176
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
added 2 commits
September 18, 2018 18:19
This makes it easier to scan through the line and add new lexers in the future.
|
Very nice! |
mrsdizzie
pushed a commit
to mrsdizzie/chroma
that referenced
this pull request
Jul 15, 2020
This makes it easier to scan through the line and add new lexers in the future.
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.
With all the lexers that Chroma now supports I thought that the README page would be a bit easier to read/scan if lexers are grouped based on their name.
So this pull request turns the paragraph with all lexers into a table. Here's how that looks like.
(Since this pull request doesn't add something new, but merely changes how it looks, I'm fine with it not being merged. It's just a little suggestion from my side.)