Thomas Morley <[email protected]> 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. -- David Kastrup My replies have a tendency to cause friction. To help mitigating damage, feel free to forward problematic posts to me adding a subject like "timeout 1d" (for a suggested timeout of 1 day) or "offensive".
