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
>
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 li
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 fa
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 p
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
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
includes, some non-conventional symbols). T
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 people to this branch.
Needed would be a rebase,
2018-06-05 1:42 GMT+02:00 edes :
>
> el 2018-06-04 a las 23:45 Thomas Morley escribió:
>
>> You could try to checkout a branch from master and apply all of the
>> attached patches.
>
> Thank you very much for the patches, "Thomas"!!
>
> I applied them to the sources pulled from git, and lilypond co
el 2018-06-04 a las 23:45 Thomas Morley escribió:
> You could try to checkout a branch from master and apply all of the
> attached patches.
Thank you very much for the patches, "Thomas"!!
I applied them to the sources pulled from git, and lilypond compiled
without a problem. I haven't done exte
2018-06-04 0:23 GMT+02:00 edes :
>
> I'm using lilypond on gentoo linux, compiled using the official gentoo
> ebuild. After updating guile to 2.2.3, lilypond stopped working. The
> following minimal example:
>
> \version "2.19.80"
> \relative c' { c4 d e f }
>
> produces the following output:
>
> G
Am 04.06.2018 um 02:43 schrieb edes:
el 2018-06-04 a las 01:06 David Kastrup escribió:
Sounds like an encoding or other I/O problem with the intermediate
PostScript files. Can you use -dno-delete-intermediate-files and
compare the resulting intermediate files (named rather randomly so
you'll h
edes writes:
> el 2018-06-04 a las 01:06 David Kastrup escribió:
>
>> Sounds like an encoding or other I/O problem with the intermediate
>> PostScript files. Can you use -dno-delete-intermediate-files and
>> compare the resulting intermediate files (named rather randomly so
>> you'll have to loo
el 2018-06-04 a las 01:06 David Kastrup escribió:
> Sounds like an encoding or other I/O problem with the intermediate
> PostScript files. Can you use -dno-delete-intermediate-files and
> compare the resulting intermediate files (named rather randomly so
> you'll have to look for them).
Hi, th
edes writes:
> I'm using lilypond on gentoo linux, compiled using the official gentoo
> ebuild. After updating guile to 2.2.3, lilypond stopped working. The
> following minimal example:
>
> \version "2.19.80"
> \relative c' { c4 d e f }
>
> produces the following output:
>
> GNU LilyPond 2.19.81
I'm using lilypond on gentoo linux, compiled using the official gentoo
ebuild. After updating guile to 2.2.3, lilypond stopped working. The
following minimal example:
\version "2.19.80"
\relative c' { c4 d e f }
produces the following output:
GNU LilyPond 2.19.81
Import (ice-9 threads) to have
15 matches
Mail list logo
