[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: New scheme list/identifier syntax has undocumented side-effects
|
From: |
David Kastrup |
|
Subject: |
Re: New scheme list/identifier syntax has undocumented side-effects |
|
Date: |
Sun, 19 Jun 2016 11:38:41 +0200 |
|
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
Malte Meyn <address@hidden> writes:
> Hi list,
>
> the German LilyPond forum discovered a side effect of the new
> identifier syntax: additional to
>
> \version "2.19.40"
> FOO = { c d e }
> \FOO
>
> there are now more cases where you cannot use a variable immediately
> after it’s definition:
>
> \version "2.19.40"
> FOO = "This is a markup"
> \FOO
> BAR = "test.ly"
> \include \BAR
>
> This comes from commit 2a66e23f3 and should be documented in the
> changes IMO because probably that’s nothing that convert-ly can
> handle.
<URL:https://lists.gnu.org/archive/html/lilypond-user/2016-05/msg00350.html>
I'm pretty sure I must have mentioned/discussed this when it was
introduced, but a quick search was not successful in digging up
something more relevant.
--
David Kastrup