bug-lilypond
[Top][All Lists]
Advanced

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

Re: Bad slur shape at line break with change of clef


From: Jonas Hahnfeld
Subject: Re: Bad slur shape at line break with change of clef
Date: Sun, 13 Dec 2020 16:29:08 +0100
User-agent: Evolution 3.38.2

Hi all, Harm,

Am Sonntag, dem 13.12.2020 um 13:53 +0100 schrieb Thomas Morley:
> Am Sa., 12. Dez. 2020 um 21:07 Uhr schrieb Timothy Lanfear 
> <timothy@lanfear.me>:
> > 
> > The part of the slur before the line break is badly shaped when another
> > staff has a clef change.
> > 
> > \version "2.20.0"
> > 
> > <<
> >    \new Staff {
> >      R1*2
> >      r2 r4 r8 r16 r32 e''32( |
> >      \break
> >      d''8) r r4 r2 |
> >      R1*3
> >    }
> > 
> >    \new Staff {
> >      R1*3
> >      \clef "bass"
> >      R1*4
> >    }
> >  >>
> > 
> > 
> > --
> > Timothy Lanfear, Bristol, UK.
> > 
> > _______________________________________________
> > bug-lilypond mailing list
> > bug-lilypond@gnu.org
> > https://lists.gnu.org/mailman/listinfo/bug-lilypond
> 
> As far as I can tell it was introduced with
> 
> commit 16a328617e867892e8d5608f95bd6127196e03a2
> Author: Keith OHara <k-ohara5a5a@oco.net>
> Date:   Sun Jun 17 21:45:26 2012 -0700
> 
>     Consistent bounds for slurs; issue 427 and 379
> 
> in 2.15.41.
> [...]
> 
> I attach images with and without the revert.
> While the revert fixes the reported problem, issues 427 and 379 are
> present again.
> 
> Hopefully somebody with more knowledge, chimes in.

Could you create a GitLab issue for the bug report and transfer your
findings? This will make it easier to find the details in the future.

Thanks
Jonas

Attachment: signature.asc
Description: This is a digitally signed message part


reply via email to

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