On 9/11/07, Reinhold Kainhofer <[EMAIL PROTECTED]> wrote: > > > After you found out, it makes sense (because the bracket is not a bracket > in > the sense that it encloses something, but rather an attribute to the > note). > But if you are used to writing code, interleaving brackets and braces > seems > completely counter-intuitive (in particular since lilypond is very picky > about slurs when you work with << ....\\ ....>>). I ran into this very > problem a while back and it took me some time to figure out that I can > interleave the brackets.
Well, I'm no programmer, so that could explain why I've never given it a second thought. Once you have found out how it works, it might seem like a no-brainer, but > if > you have not yet, then such a snippet is quite useful The problem is, as Mats says, it's not specific to beaming; it applies equally to things like slurs and ties. If a snippet is to be submitted to LSR, it needs to be more generalized. Regards, Neil
_______________________________________________ lilypond-user mailing list lilypond-user@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-user
