Re: lyricmode regression

[Vik Reykja]

On Sun, Sep 22, 2013 at 6:39 PM, David Kastrup <address@hidden> wrote:

> David Kastrup <address@hidden> writes:
>
> > Vik Reykja <address@hidden> writes:
> >
> >> Upgrading from 2.14.2 (Ubuntu 12.10) to 2.17.27 (git head) in order to
> try
> >> something, I noticed my music was broken.  Here is a minimal example
> >> illustrating the problem:
> >>
> >> \new Lyrics \lyricmode { \skip 1.*3 }
> >
> > The lexer apparently thinks this to be the same as
> >
> > \skip 1 ".*"3
> >
> > I'll take a look and see whether I can find where LilyPond veers
> off-course.
>
> Tracker issue: 3571 (
> http://code.google.com/p/lilypond/issues/detail?id=3571)
> Rietveld issue: 13256053 (http://codereview.appspot.com/13256053)
> Issue description:
>   Stop \lyricmode { \skip 1.*3 } from failing.  The problem was that
>   the lexer preferred to match ".*" as a word since the matched
>   pattern was longer than the explicit pattern matching ".". The word
>   pattern is now amended so that it does not compete with the single-
>   character patterns.
>
> Thanks for the report.
>

And thank you for your quick response.  This does indeed fix my minimal
example.  However, it introduces several

programming error: no solution found for Bezier intersection
continuing, cross fingers

in my actual file.  I will try to come up with a new minimal example within
the next few days.

It would be nice if that error gave me some kind of clue where to look.
Examining the pdf, I don't notice any slurs or ties that look bad.  There
is horrible collision on string numbers (this is a guitar piece) but I
don't see what Bezier has to do with that.
-- 
Vik