Richard Shann writes:
> On Mon, 2021-01-04 at 00:45 +0100, David Kastrup wrote:
>> Richard Shann writes:
>>
>> > My understanding of the \beamExceptions function in 2.20 was that
>> > you
>> > should be able to pass it a complete bar beamed as you would wish
>> > and
>> > expect other bars
On Sun, 2021-01-03 at 22:34 +0100, Xavier Scheuer wrote:
> On Sun, 3 Jan 2021 at 18:04, Richard Shann
> wrote:
> >
> > My understanding of the \beamExceptions function in 2.20 was that
> you
> > should be able to pass it a complete bar beamed as you would wish
> and
> > expect other bars with the
On Mon, 2021-01-04 at 00:45 +0100, David Kastrup wrote:
> Richard Shann writes:
>
> > My understanding of the \beamExceptions function in 2.20 was that
> > you
> > should be able to pass it a complete bar beamed as you would wish
> > and
> > expect other bars with the same beat structure to be
Richard Shann writes:
> My understanding of the \beamExceptions function in 2.20 was that you
> should be able to pass it a complete bar beamed as you would wish and
> expect other bars with the same beat structure to be beamed to match.
But you did not pass \beamExceptions a bar beamed as you
On Sun, 3 Jan 2021 at 18:04, Richard Shann wrote:
>
> My understanding of the \beamExceptions function in 2.20 was that you
> should be able to pass it a complete bar beamed as you would wish and
> expect other bars with the same beat structure to be beamed to match.
> In this example barOne and
My understanding of the \beamExceptions function in 2.20 was that you
should be able to pass it a complete bar beamed as you would wish and
expect other bars with the same beat structure to be beamed to match.
In this example barOne and barTwo have the same rhythm but only barOne
is beamed as
