lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 3687 in lilypond: only full-measure-rests shou


From: lilypond
Subject: Re: [Lilypond-auto] Issue 3687 in lilypond: only full-measure-rests should be able to compress
Date: Sun, 26 Apr 2015 16:38:23 +0000


Comment #2 on issue 3687 by tdanielsmusic: only full-measure-rests should be able to compress
https://code.google.com/p/lilypond/issues/detail?id=3687

It's relatively easy to write a music function which uses skipBars like \compressFullBarRests but which filters out the MM rests first, like this:

compressMMRests =
#(define-music-function (parser location music) (ly:music?)
   (music-map
    (lambda (m)
      (if (or
           (member 'rhythmic-event (ly:music-property m 'types))
           (member 'multi-measure-rest (ly:music-property m 'types)))
        (if (eq? 'MultiMeasureRestMusic (ly:music-property m 'name))
          #{ \set Score.skipBars = ##t #m #}
          #{ \set Score.skipBars = ##f #m #} )
        m))
    music))

I've used a different name, because \compressFullBarRests is likely to be embedded in many scores and it would be difficult to impossible to write a convert-ly entry to replace it with a music function. One way forward would be to install the proposed compressMMRests music function, leaving \compressFullBarRests and skipBars unchanged, then modify the manuals to use \compressMMRests {...} instead of \compressFullBarRests.

What do you think?  Should I submit a patch to do that?

Trevor


--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

[Prev in Thread] Current Thread [Next in Thread]