|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 11:18:09 -0000|
I thought I asked not to run makelsr?
I am going to test patch version 2 not 3 (without the makelsr).
Running makelsr for patch review is silly - look how many files have changed! How can anyone know what is 'real' and what is just the makelsr?
Please don't commit the patch (when it eventually goes through) with makelsr included as it makes it inconvenient if we have to revert anything or cherry pick the real fix (because the makelesr is effectively merged into the real patch).
So ... if patch version 3 contains anything other than the just makelsr output you will need to re-submit again.
[issues:#5251] document restNumberThreshold
Created: Tue Jan 09, 2018 07:58 PM UTC by Malte Meyn
Last Updated: Fri Dec 28, 2018 10:59 AM 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]|