bug-lilypond
[Top][All Lists]
Advanced

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

Re: Possible bug with \oneVoice involving rests


From: David Kastrup
Subject: Re: Possible bug with \oneVoice involving rests
Date: Sat, 14 Jun 2014 21:26:54 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.4.50 (gnu/linux)

James <address@hidden> writes:

> On 02/06/14 17:38, David Kastrup wrote:
>> Yes, that's plausible, but your above reasoning about << >> remains
>> incorrect.
>>
>> Things are more readable if you revert to << >> only when you indeed
>> want parallel voices rather than just multiple notes in a chord.  But
>> they are valid nevertheless.
>>
> Does that mean using << >> without the \\ is acceptable or just an
> unfortunate side effect of (for want of a better phrase) not being more
> strict when parsing << >> without the \\?

Historically, there were

    \sequential { music list }
    \simultaneous { music list }

first.  Then easier to type equivalents

    { music list }

and

    < music list >

came.

Then chord notation was introduced as

    << chord constituents >>

and finally, there was the big change of swapping the syntax for chords
and for simultaneous music.

Quite later \\ was introduced as a shortcut for parallel voices.

Since we are obviously also using << >> in constructs like
\new StaffGroup <<
  \new Staff ...
  \new Staff ...
>>

This is not just a side effect.  It is the principal mode of operation.

-- 
David Kastrup



reply via email to

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