lilypond-devel
[Top][All Lists]
Advanced

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

Re: Feature request


From: Phil Holmes
Subject: Re: Feature request
Date: Mon, 24 Sep 2012 11:17:02 +0100

----- Original Message ----- From: "David Kastrup" <address@hidden>
To: "Werner LEMBERG" <address@hidden>
Cc: <address@hidden>
Sent: Monday, September 24, 2012 8:44 AM
Subject: Re: Feature request


Werner LEMBERG <address@hidden> writes:

  \beaming { c8[ c] c r c[ c c c] }

Ouch.  Of course.

but yes, that would be great.

This could probably be

  \beaming {8[ 8] 8 8 8[ 8 8 8] }

Uh no.  You need the rest, or you need to write something like
\beaming {4 8[ 8] 8[ 8 8 8]}

Don't think so. With this command, it would seem that the rule is "delete all previous autobeaming rules and only autobeam in the pattern set with manual beams here". Then you need neither the rest or the crochet.

And where the overrides can be used, the meter might not be known yet,
so one needs to write something like
\beaming 4/4 { ... }
(somewhat redundant) and/or require that the argument consists of
whole bars separated by bar checks.

Again, with the suggestion above, this is not needed. This part of the rule is that the bracketed note lengths must form a complete bar in the current time signature. If not, an error is thrown.

It is probably easiest to require the time specification always (it is
needed for setting baseMoment and figuring out measureLength): that way
the chance for users to mess up once they have LilyPond stop complaining
is minimized.


--
Phil Holmes



reply via email to

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