[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: NR 3.6.1, Displaying LilyPond notation
From: |
Urs Liska |
Subject: |
Re: NR 3.6.1, Displaying LilyPond notation |
Date: |
Fri, 4 Dec 2015 16:31:58 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 |
Am 04.12.2015 um 16:23 schrieb Federico Bruni:
> Il giorno ven 4 dic 2015 alle 15:52, David Kastrup <address@hidden> ha
> scritto:
>> Well, no, that isn't what is meant by "interpreted".
>>
>> How about:
>>
>> The music function \displayLilyMusic displays the following music
>> expression while also retaining it as part of the surrounding
>> expression. This is convenient when inserting \displayLilyMusic into
>> existing music expressions since it does not affect their interpretation
>> when printing a rendition of them.
>>
>> Sometimes you indeed only want to print some expression without letting
>> LilyPond do anything else with it. In that case, you can place \void
>> before \displayLilyMusic and the entire expression will be discarded
>> after displaying it.
>
> Much better, now I think I got it.
>
> The meaning of "displaying" here should be made more clear: display in
> the console, not in the output. Some redundancy may help with avoiding
> any misunderstanding:
>
> The music function \displayLilyMusic displays the following music
> expression _in the console_ while...
One thing that might benefit from some more disambiguation is:
\displayLilyMusic displays the music expression in (re-generated)
LilyPond input syntax, regardless of whether it is fed {a b c} or
\musicFunctionThatReturnsASymphony, while \displayMusic displays the
textual representation of a Scheme function.
Urs
>
>
> _______________________________________________
> lilypond-user mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/lilypond-user