Re: lilypond not working when compiled against guile-2.2

2018-06-05 Thread Carl Sorensen
On 6/5/18, 2:45 AM, "Thomas Morley" wrote: 2018-06-05 4:14 GMT+02:00 Carl Sorensen : > > > On 6/4/18, 6:13 PM, "Thomas Morley" wrote: > > > That said, in our git we have a 'guile-v2-work'-branch, but it's not > up to date... > > @David >

Re: lilypond not working when compiled against guile-2.2

2018-06-05 Thread edes
el 2018-06-05 a las 10:36 Thomas Morley escribió: > Well, most of those patches are not "my patches" (look at the > authors), over the years several people worked on migrating to > guilev2. Indeed, thank you and Dave and Antonio. And certainly to everyone who contributed to the development of

commit 12fe78825798191ecb7e5a4ee3064679773ae1ab is broken

2018-06-05 Thread Knut Petersen
Commit 12fe788... caused encodingdefs.ps to be out of sync with the emmentaler fonts. It even does not pass a 'make check' against the previous commit - have a look at the staccato in test-output-distance. The png generated from commit be08490329a2242... shows the expected staccato, the png from

Re: lilypond not working when compiled against guile-2.2

2018-06-05 Thread David Kastrup
Thomas Morley writes: > 2018-06-05 4:14 GMT+02:00 Carl Sorensen : >> >> >> On 6/4/18, 6:13 PM, "Thomas Morley" wrote: >> >> >> That said, in our git we have a 'guile-v2-work'-branch, but it's not >> up to date... >> >> @David >> I think about updating this branch, it would be

Re: lilypond not working when compiled against guile-2.2

2018-06-05 Thread Thomas Morley
2018-06-05 4:14 GMT+02:00 Carl Sorensen : > > > On 6/4/18, 6:13 PM, "Thomas Morley" wrote: > > > That said, in our git we have a 'guile-v2-work'-branch, but it's not > up to date... > > @David > I think about updating this branch, it would be far easier to point > interested

Re: lilypond not working when compiled against guile-2.2

2018-06-05 Thread Thomas Morley
2018-06-05 5:22 GMT+02:00 edes : > > el 2018-06-05 a las 02:13 Thomas Morley escribió: > >> Be aware that guilev2 support is still experimental. > > Thanks for the update, Thomas. I haven't used lilypond extensively, but i > have some short but non-trivial scores (lots of tweaks, several levels of