Re: programming error while inserting "ChordNames" in "Staff"

[Thomas Morley]

2013/3/30 Colin Hall <address@hidden>

>
> Thomas, devs, what do you want to do with this thread?
>
> As I understand it, a user on the German forum has tried this, for good
> reasons, and it failed with a programming error.
>
> David explained that this is not surprising.
>
> So, we can treat this as a bug, with a resolution that Lilypond
> detectings the condition and reports it as an error and exits.
>
> Or the feature of "ChordNames within a Staff" could be documented using
> the advice given (but not yet proven?) as per David's last email.
>
> Or we can reject the bug report.
>
> Please advise.
>
> Cheers,
> Colin.
>

 At first sight I thought it might be a bug, because 2.17.12 returned a
programming error while 2.16.2 worked without complains.

As David pointed out, it is expected behaviour now. Therefore I'd reject
the bug report.

In order not to loose information about how to do it and possible problems
with it, I could create a LSR-snippet, tagged doc, ensuring it works with
the current LSR-version up to latest devel-version.
Or, if this isn't possible, to add such a snippet to
/Documentation/snippets/new.

Regards,
  Harm