lilypond-devel
[Top][All Lists]
Advanced

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

Re: displayLilyMusic and guilev2


From: Thomas Morley
Subject: Re: displayLilyMusic and guilev2
Date: Sun, 9 Feb 2020 14:11:28 +0100

Am So., 9. Feb. 2020 um 00:23 Uhr schrieb David Kastrup <address@hidden>:
>
> Thomas Morley <address@hidden> writes:
>
> > Am Sa., 8. Feb. 2020 um 23:59 Uhr schrieb David Kastrup <address@hidden>:
> >>
> >> Thomas Morley <address@hidden> writes:
> >>
> >> > Hi,
> >> >
> >> > one problem with guilev2 are anonymous procedures. Like how to get
> >> > nice output for
> >> >
> >> > \void
> >> > \displayLilyMusic \new Voice { \applyContext #(lambda (ctx) (display 
> >> > ctx)) b4 }
> >> >
> >> > An older lily-build out of e57c27dc14 with the patches from
> >> > guilev2-work on top and guile-2.0.14 returned:
> >> > \new Voice { \applyContext ##f b4 }
> >> > Which is suboptimal.
> >> >
> >> > A todays build out of c334743a6d and guile-2.2.6, selfcompiled out of
> >> > ~/guile-2.2 (my-guile-2-2-6)$ git log --oneline
> >> > 9a11be136 (HEAD -> my-guile-2-2-6, origin/stable-2.2)
> >> > 00-repl-server.test: don't use fixed path for socket
> >> > 5d2956497 Respect thread local fluid defaults
> >> > aa0bfa2f9 Fix peval bug that ignored excess args
> >> > fb7b873af web: Update comment regarding the 'tls-wrap' port wrapper.
> >> > edf5aea7a Fix non-deterministic crash in 'finalization_thread_proc'.
> >> > 659526d33 ports: 'scm_port_poll' honors "w" flags.
> >> > a69b567d9 (guile-2.2.6) build: Do not record LDFLAGS in .pc file.
> >> > 85de8637c (tag: v2.2.6) Bump version for Guile 2.2.6.
> >> > ...
> >> >
> >> > returns:
> >> > \new Voice { \applyContext #(lambda (ctx) (display ctx)) b4 }
> >> > which is nice again and the same as in 2.19.84 with guile-1.8
> >> >
> >> > Does anybody knows whether it's a guile- or lily-improvement?
> >>
> >> No idea.  It might be a different compilation option or environment or
> >> eval setting that is at work here because I have ostensibly also a 2.2.6
> >> and your commits on top of the tag don't look like they could make a
> >> difference.
> >
> > To be sure, you still get:
> > \new Voice { \applyContext ##f b4 }
> > ?
>
> dak@lola:/usr/local/tmp/lilypond$ out/bin/lilypond scheme-sandbox
> GNU LilyPond 2.21.0
> Processing 
> `/usr/local/tmp/lilypond/out/share/lilypond/current/ly/scheme-sandbox.ly'
> Parsing...
> GNU Guile 2.2.6
> Copyright (C) 1995-2019 Free Software Foundation, Inc.
>
> Guile comes with ABSOLUTELY NO WARRANTY; for details type `,show w'.
> This program is free software, and you are welcome to redistribute it
> under certain conditions; type `,show c' for details.
>
> Enter `,help' for help.
> scheme@(#{ g161}#)> (void (displayLilyMusic #{ \new Voice { \applyContext 
> #(lambda (ctx) (display ctx)) b4 } #}))
>
> \new Voice { \applyContext ##f
>  b4 }
> scheme@(#{ g161}#)>
>
>
> Success: compilation successfully completed
> dak@lola:/usr/local/tmp/lilypond$
>
>
>
> -*- mode: compilation; default-directory: "/tmp/" -*-
> Compilation started at Sun Feb  9 00:21:33
>
> /usr/local/tmp/lilypond/out/bin/lilypond hh.ly
> GNU LilyPond 2.21.0
> Processing `hh.ly'
> Parsing...
> \new Voice { \applyContext ##f
>  b4 }
>
> hh.ly:1: warning: no \version statement found, please add
>
> \version "2.21.0"
>
> for future compatibility
> Success: compilation successfully completed
>
> Compilation finished at Sun Feb  9 00:21:35

Because of other strange results I trashed my previous build and
started from scratch.
With the new build out of
7362fcde45 (HEAD -> master, origin/master, origin/HEAD) Issue 5733/4:
int->vsize in Dot_column
I've now got the same results from compiling a ly-file.

But in scheme-sandbox:
scheme@(#{ g161}#)>  (void (displayLilyMusic #{ \new Voice {
\applyContext #(lambda (ctx) (display ctx)) b4 } #}))
While compiling expression:
unhandled constant #<procedure embedded-lilypond (a b c d)>
scheme@(#{ g161}#)>


No clue

Cheers,
  Harm



reply via email to

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