Added basic support for LilyPond#1967
Merged
RunDevelopment merged 4 commits intoPrismJS:masterfrom Jul 20, 2019
Merged
Conversation
mAAdhaTTah
approved these changes
Jul 20, 2019
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.
As the title says: This adds basic support for LilyPond. I'm not a musician and understand very little of the theory of the music being highlighted.
With that out of the way, now to a few notes:
I checked every LilyPond file in the LilyPond source and all of them look ok with no noticeable mistakes (at least I didn't notice any).
Also, I want to add an example to the examples page, so if anyone has a nice LilyPond example please tell me.
Examples
All of the following examples are taken for the LilyPond 2.18.2 source code.
(The incorrect Scheme number highlighting is addressed in #1964.)
This resolves #1861.