Il 18/01/2021 00:49, David Kastrup ha scritto:
Davide Bonetti writes:
At first glance, it would appear that all of those changes are intended
to be upwards-compatible. As such it would not make a lot of sense to
place them in a separate, different file rather than extend the existing
one. O
Davide Bonetti writes:
> Hello to everyone.
>
> I have updated the accordion registers that are in accreg.scm.
>
> I modified accreg.scm and renamed in "accregtwo.scm". This file must
> be placed in lilypond usr/share/lilypond/current/scm directory in
> order to make it work.
>
> also, at the top
Hello to everyone.
I have updated the accordion registers that are in accreg.scm.
I modified accreg.scm and renamed in "accregtwo.scm". This file must be
placed in lilypond usr/share/lilypond/current/scm directory in order to
make it work.
also, at the top of a input file is necessary to put
On Jan 15, 2021, at 12:17, Werner LEMBERG wrote:
>
>> The "Unmetered music" section in the manual already discusses issues
>> with bar numbers, accidentals, and autobeaming. It might be helpful
>> to mention the workaround of using \partial 1024 s1024 to force a
>> new measure at the end of a ca
Am Samstag, dem 16.01.2021 um 20:20 +0100 schrieb Han-Wen Nienhuys:
> On Sat, Jan 16, 2021 at 2:52 PM Jonas Hahnfeld wrote:
> > > I can probably trim down the fix to be more backward compatible.
> > >
> > > Do you know of documentation that details what is and is not allowed
> > > in an ABI-compa
Hello,
Here is the current patch countdown list. The next countdown will be on
January 19th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!594 Bar numbers should not change with visibility - Dan Eble
https:
