Update of property assignment syntax for Lilypond conversion (issue #1791)#1800
Merged
mscuthbert merged 4 commits intocuthbertLab:masterfrom Aug 8, 2025
Merged
Update of property assignment syntax for Lilypond conversion (issue #1791)#1800mscuthbert merged 4 commits intocuthbertLab:masterfrom
mscuthbert merged 4 commits intocuthbertLab:masterfrom
Conversation
\override Property #'Attribute = value we have \override Property.Attribute = value
Contributor
Author
|
The flake errors refer to "" vs '' and most have nothing to do with changes I made, so I hesitate to get involved in that. |
Member
|
closing and reopening to get a clear flake sign. |
Member
|
Hi -- those flake things were "caused" by you -- I'll do a quick fix. When you modified the |
Member
|
thanks! |
Contributor
Author
|
Thank you! |
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.
The property assignment syntax for lilypond has been updated, so that instead of
we have
This responds to issue #1791