We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
As per David Kastrup in the LilyPond users' forum:
Calling git grep "\\\\override[^=]*#'[a-z]" in the current Frescobaldi source tree delivers way too many hits.
Calling
git grep "\\\\override[^=]*#'[a-z]"
in the current Frescobaldi source tree delivers way too many hits.
Search for all "bad" overrides in the code base and bring them up to post-2.18 syntax, for instance:
\override Tie #'thickness = #2
becomes
\override Tie.thickness = #2
And a way should be found to fix any overrides that span line breaks.
The text was updated successfully, but these errors were encountered:
8f71e31
Should be fixed. Please reopen if you find a missing spot.
Sorry, something went wrong.
There's a "clever" one hidden in two lines in clef_treble_8.ly, lines 7 and 8. (Sorry, I don't know how to re-open the issue.)
Ah yes, fixed in b6bc6e8.
(Sorry, I don't know how to re-open the issue.)
Ok, then I guess people without triage access to the repository can't reopen issues.
No branches or pull requests
As per David Kastrup in the LilyPond users' forum:
Search for all "bad" overrides in the code base and bring them up to post-2.18 syntax, for instance:
becomes
And a way should be found to fix any overrides that span line breaks.
The text was updated successfully, but these errors were encountered: