[Top][All Lists]

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

Re: [LSR] multi-measure-rest-length-control.ly snippet should not use \c

From: James Lowe
Subject: Re: [LSR] multi-measure-rest-length-control.ly snippet should not use \compressFullBarRests
Date: Tue, 11 Sep 2018 13:59:26 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1


On 30/08/18 10:54, Federico Bruni wrote:
Hi folks

Bug Squad, this does not require a new issue in the tracker, but just someone who can fix the snippet on the LSR website.

There's a recent snippet file imported from LSR which contains \compressFullBarRests.

$ git grep \compressFullBarRests Documentation/snippets
Documentation/snippets/multi-measure-rest-length-control.ly:25: \compressFullBarRests Documentation/snippets/new/multi-measure-rest-length-control.ly:17: \compressFullBarRests

Given this commit:

commit ba9a8dc730bb3a681455150bc0a3eef0976523af
Author: Trevor Daniels <address@hidden>
Date: Fri May 1 22:56:47 2015 +0100

   Issue 3687 (part 2): Amend docs to use \compressMMRests

     Amend the examples in the LM and NR to use the \compressMMRests
     music function rather than the predefs \compressFullBarRests and
     \expandFullBarRests to avoid advocating the use of techniques
     which may have undesirable side effects.

we should replace it with \compressMMRests.
Who can do this change in the LSR?
I cannot find this on the LSR.

It is in LilyPond's own Snippets (but that is not the same thing) so a change to this would require a change in git.


grep -r "compressFullBarRests" * | wc -l

gives a count of 38 (of which 14 are *.po files) so we might as well change it for those files too right?

In which case a tracker would be best.

Let me know.


reply via email to

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