[Top][All Lists]

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

Re: LilyPond 2.7.18 released

From: Han-Wen Nienhuys
Subject: Re: LilyPond 2.7.18 released
Date: Tue, 22 Nov 2005 11:20:59 +0100
User-agent: Mozilla Thunderbird 1.0.7-1.1.fc4 (X11/20050929)

Erik Sandberg wrote:

It seems to me that all brackets on a given nesting depth must be the same kind of bracket. I.e., the following bracket configuration can't be done by a single StaffGroup:

\new StaffGroup <<
  \new InnerStaffGroup <<
    \new Staff c'1
    \new Staff c'1
  \new Staff c'1
  \new PianoStaff <<
    \new Staff c'1
    \new Staff c'1

I don't know how common this kind of notation is, but wouldn't it be more generic to ditch the systemStartDelimiters property and give the delimiters explicitly in the hierarchy? I.e., for the example in NEWS, something like this: \set StaffGroup.systemStartDelimiterHierarchy = #'(SystemStartSquare (SystemStartBracket a (SystemStartSquare b)) c)

(I don't have a particular need for this myself, I just want to bring up the issue before backward compatibility becomes a problem)

YEs, you're right. I contemplated this before, but didn't do it out of a. lazyness, b. elegance. If we go for this, then a syntax like

  #(Square ((Bracket (x (Square y))

looks more logical to me.


 Han-Wen Nienhuys - address@hidden -

reply via email to

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