[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: LSR #983 produces strange result
|
From: |
Jean Abou Samra |
|
Subject: |
Re: LSR #983 produces strange result |
|
Date: |
Sun, 23 Apr 2023 11:22:41 +0200 |
|
User-agent: |
Evolution 3.48.0 (3.48.0-1.fc38) |
Le dimanche 23 avril 2023 à 10:04 +0200, Thomas Morley a écrit :
> Am So., 23. Apr. 2023 um 09:33 Uhr schrieb Thomas Morley
> <[thomasmorley65@gmail.com](mailto:thomasmorley65@gmail.com)>:
>
> >
> > Am So., 23. Apr. 2023 um 07:45 Uhr schrieb Werner LEMBERG
> > <[wl@gnu.org](mailto:wl@gnu.org)>:
> >
> > >
> > >
> > > Please have a look at
> > >
> > >
> > > [https://lsr.di.unimi.it/LSR/Item?id=983](https://lsr.di.unimi.it/LSR/Item?id=983)
> > >
> > > This code has obviously worked some time before, but it no longer
> > > doesn't. Is this a problem with the code or a bug?
> > >
> > >
> > > Werner
> > >
> >
> >
> > Fixed inside LSR by replacing
> > \once\omit Staff.BarLine
> > by
> > \once\hide Staff.BarLine
> >
> > No clue though, why it works now.
> >
> > Cheers,
> > Harm
>
>
> I think it may be a bug. Consider:
> {
> \textLengthOn
> s1-"loooooooooooooong"
> \once \omit Staff.BarLine
> \clef F
> r1
> }
> with a starting spacer _and_ an omitted BarLine _and_ a clef change.
>
> 2.22. is ok, but output of 2.24. is bad.
The MM rest placement sounds like
https://gitlab.com/lilypond/lilypond/-/issues/6550
The horizontal placement of the clef looks strange but I haven't investigated
further.
signature.asc
Description: This is a digitally signed message part