Re: 2.21.1 change of behavior of \compressMMRests?

[Paul Scott]

Thank you for this, Valentin.

On 5/3/20 11:14 PM, Valentin Villenave wrote:
> On 5/3/20, Paul Scott <address@hidden> wrote:
> > Out of simple curiosity what is the purpose of the \compressMMRests { }
> > structure rather than the \set or \override action I would think of?
> > I'm guessing \compressMMRests does \set \unset or \override \revert pairs.
> As you can see if you open the music-functions-init.ly file in your
> LilyPond installation, it’s a fairly simple music function that relies
> on the skipBars property:
> https://git.savannah.gnu.org/cgit/lilypond.git/tree/ly/music-functions-init.ly#n313
> As does compressEmptyMeasures, formerly compressFullBarRests -- but
> these are just a mere override:
> https://git.savannah.gnu.org/cgit/lilypond.git/tree/ly/property-init.ly#n168
>
> Now, your question is exactly why I felt the need to add a whole new
> subsection to the Notation Reference:
> http://lilypond.org/doc/v2.21/Documentation/notation/writing-parts#compressing-empty-measures
> I hope this can answer your question (as well as the rationale behind
> the renaming of FullbarRests into EmptyMeasures); please do tell us if
> that seems unclear to you or if you have some suggestions to improve
> that part of the documentation.

I did look at that documentation when this first came up and rejected 
\compressEmptyMeasures both because of the less logical (to me) name and 
this documentation whose first example suggests behavior that I wouldn't 
want for any music I work with, i.e. writing a whole note in 2/4 rather 
than two tied half notes.

Taking all the feedback I have received in this thread I believe all I 
should have ever used is

\set Score.skipBars = ##t

I just thought \compressFullBarRests was the sophisticated way and less 
vulnerable to lower level LilyPond code changes.

Stay well,

Paul


> Cheers,
> -- V.