On Jan 15, 2021, at 18:58, Thomas Morley wrote:
>
> (3) if the cadenza has inner bar-lines, we should provide a simple
> method to increase BarNumbers. Not sure, if we could implement this as
> an automtism…
I had a similar thought, but for a method to force a measure break, with other
things (
Am Fr., 15. Jan. 2021 um 02:36 Uhr schrieb Dan Eble :
>
> On Jan 14, 2021, at 19:13, Dan Eble wrote:
> >
> > On Jan 14, 2021, at 18:33, Dan Eble wrote:
> >>
> >> Alas, all is not well with earlier versions. Consider the confusing bar
> >> numbers in the following elaboration of your example. H
>>> Add issue #3640 to this discussion. Accidentals, bar numbers, and
>>> (now) multi-measure rests are all impacted by the fact that \bar
>>> "|" does not create a new measure.
>>
>> Maybe the whole thing is primarily a documentation issue that could
>> be fixed with prominent warnings at appro
Dan Eble writes:
> On Jan 15, 2021, at 06:53, David Kastrup wrote:
>>
>> Werner LEMBERG writes:
>>
Add issue #3640 to this discussion. Accidentals, bar numbers, and
(now) multi-measure rests are all impacted by the fact that \bar "|"
does not create a new measure.
>>>
>>> May
On Jan 15, 2021, at 06:53, David Kastrup wrote:
>
> Werner LEMBERG writes:
>
>>> Add issue #3640 to this discussion. Accidentals, bar numbers, and
>>> (now) multi-measure rests are all impacted by the fact that \bar "|"
>>> does not create a new measure.
>>
>> Maybe the whole thing is primari
> On Jan 15, 2021, at 04:53, Werner LEMBERG wrote:
>
>
>> Add issue #3640 to this discussion. Accidentals, bar numbers, and
>> (now) multi-measure rests are all impacted by the fact that \bar "|"
>> does not create a new measure.
>
> Maybe the whole thing is primarily a documentation issue
Werner LEMBERG writes:
>> Add issue #3640 to this discussion. Accidentals, bar numbers, and
>> (now) multi-measure rests are all impacted by the fact that \bar "|"
>> does not create a new measure.
>
> Maybe the whole thing is primarily a documentation issue that could be
> fixed with prominent
> Add issue #3640 to this discussion. Accidentals, bar numbers, and
> (now) multi-measure rests are all impacted by the fact that \bar "|"
> does not create a new measure.
Maybe the whole thing is primarily a documentation issue that could be
fixed with prominent warnings at appropriate places?
OK, I guess the inline attachments didn't work.
Sorry,
Here is the text verbatim.
--snip--
Important changes to default expiration dates for job meta data and
artifacts took effect on June 22, 2020. As part of this change
expiration dates have been applied to job artifacts that were created
Hello,
Here is the current patch countdown list. The next countdown will be on
January 17th.
A list of all merge requests can be found here:
https://gitlab.com/lilypond/lilypond/-/merge_requests?sort=label_priority
Push:
!605 Fix documentation of option `-dcrop`. - Werner Lemberg
https:/
Hello,
I suddenly started getting this pop up when looking at reg tests from
our CI system.
I can see the date is from last year, so I don't know the significance
of me seeing this 'today' - after all, I've been looking at CI reg tests
for a while now and not seen this before.
So in case
11 matches
Mail list logo
