lilypond-user
[Top][All Lists]
Advanced

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

Re: Learning LilyPond, comments invited


From: David Kastrup
Subject: Re: Learning LilyPond, comments invited
Date: Fri, 03 Jan 2014 12:08:52 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.3.50 (gnu/linux)

Urs Liska <address@hidden> writes:

> David Kastrup <address@hidden> schrieb:
>>Colin Tennyson <address@hidden> writes:
>>
>>> The LillyPond parser accepts this, there is no error, and the score
>>_is
>>> rendered correctly_.
>>> But as you point out:
>>>  this:
>>> << \addKey \staffOneNotes >>
>>> is better written as:
>>> { \addKey \staffOneNotes }
>>>
>>>
>>> While the { ... } notation is better, LilyPond accepts both: {
>>\addKey
>>> \staffTwoNotes } and << \addKey \staffTwoNotes >>.  In this case both
>>are
>>> rendered the same.
>>
>>But that's not a given.  Take, for example, the output of
>>
>>
>>------------------------------------------------------------------------
>>
>>
>>Also, if you have something like
>>
>>\new StaffGroup
>>{
>>   << \key c\major { c' c' c' c' } >>
>>}
>>
>>you'll likely be surprised by the results...
>
> Colin, your example works because you have exactly one music
> expression inside the angled brackets.

\addKey \staffOneNotes are _two_ music expressions.  I used exactly the
same template for demonstrating things that don't work.

> These let you enter multiple expressions that are interpreted in
> parallel. And if there is just one expression inside it just does
> nothing.

But that's not what we had here.

-- 
David Kastrup



reply via email to

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