|From:||Auto mailings of changes to Lily Issues via Testlilyissues-auto|
|Subject:||[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5251 document restNumberThreshold|
|Date:||Fri, 28 Dec 2018 13:41:53 -0000|
Though, said snippet compiles with 2.18. Thus there's no need to put it in snippet/new, if it is present in /Documentation/snippets.
So the need to run makelsr.
To come out of the dilemma, would it be reasonable to commit a run of makelsr as a single patch and delay Malte's patch?
[issues:#5251] document restNumberThreshold
Created: Tue Jan 09, 2018 07:58 PM UTC by Malte Meyn
Last Updated: Fri Dec 28, 2018 12:16 PM UTC
Owner: Malte Meyn
As it’s fairly common, recommended by Gould, and—depending on house style for longer measures—sometimes necessary to have single measure MMRs marked with a “1” in orchestral parts, it should be documented how this can be achieved:
\set restNumberThreshold = 0
The default seems to be “unset” but in multi-measure-rest-engraver.cc it is hardcoded to 1; you won’t find this value in engraver-init.ly.
Sent from sourceforge.net because address@hidden is subscribed to https://sourceforge.net/p/testlilyissues/issues/
To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
_______________________________________________ Testlilyissues-auto mailing list address@hidden https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
|[Prev in Thread]||Current Thread||[Next in Thread]|