[Top][All Lists]

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

‘Bleed-over’ with LilyPond assignment to a Scheme value

From: Simon Albrecht
Subject: ‘Bleed-over’ with LilyPond assignment to a Scheme value
Date: Mon, 18 Jan 2016 16:31:50 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.5.1

In a large project I ran into the following problem: If I define and call a function in Scheme-only syntax, \removeWithTag will ‘bleed over’ to following expressions (don’t ask me how exactly, I’m only guessing…).
Consider the following dummy example:

\version "2.19.35"

test = { 1-\tag not-vl -"it works!" }

#(define (build-part mus) (make-sequential-music (list mus)))
% no problem with
%#(define (build-part mus) #{ { $mus } #})

vl =
\removeWithTag not-vl
#(build-part test)
% no problem with
%\build-part \test

tbn =
#(build-part test)

\score {

The TextScript should be displayed, but it isn’t. It works with either of the commented alternatives, i.e. those involving the LilyPond parser. I’d be very much interested in the reason for this. It seems like an inconsistency that should be fixed.

Best, Simon

reply via email to

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