Re: programming error while inserting ChordNames in Staff

2013-03-31 Thread Colin Hall
Thomas Morley writes: 2013/3/30 Colin Hall colingh...@gmail.com Thomas, devs, what do you want to do with this thread? As David pointed out, it is expected behaviour now. Therefore I'd reject the bug report. OK, the bug report is duly rejected. Cheers, Colin. -- Colin Hall

Re: programming error while inserting ChordNames in Staff

2013-03-30 Thread Colin Hall
Thomas Morley writes: 2013/3/28 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: 2013/3/28 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: [...] Why would you want to have ChordNames internal to a Staff? It was requested by

Re: programming error while inserting ChordNames in Staff

2013-03-30 Thread Thomas Morley
2013/3/30 Colin Hall colingh...@gmail.com 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

programming error while inserting ChordNames in Staff

2013-03-28 Thread Thomas Morley
Hi, this code used to work with 2.16.2: \version 2.16.2 \new Staff \with { \accepts ChordNames } \new ChordNames \chordmode { \override ChordName #'Y-offset = #-1 c } With 2.17.12 an programming error occurs: GNU LilyPond 2.17.12 Processing `atest-22.ly' Parsing... Interpreting music...

Re: programming error while inserting ChordNames in Staff

2013-03-28 Thread David Kastrup
Thomas Morley thomasmorle...@googlemail.com writes: this code used to work with 2.16.2: \version 2.16.2 \new Staff \with { \accepts ChordNames } \new ChordNames \chordmode { \override ChordName #'Y-offset = #-1 c } Why would you want to have ChordNames internal to a Staff? With 2.17.12

Re: programming error while inserting ChordNames in Staff

2013-03-28 Thread Thomas Morley
2013/3/28 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: [...] Why would you want to have ChordNames internal to a Staff? It was requested by a german user. He wants the ChordNames printed in a Staff. Is there a better way to achieve it? [...] I think if we

Re: programming error while inserting ChordNames in Staff

2013-03-28 Thread David Kastrup
Thomas Morley thomasmorle...@googlemail.com writes: 2013/3/28 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: [...] Why would you want to have ChordNames internal to a Staff? It was requested by a german user. He wants the ChordNames printed in a Staff. Is

Re: programming error while inserting ChordNames in Staff

2013-03-28 Thread Thomas Morley
2013/3/28 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: 2013/3/28 David Kastrup d...@gnu.org: Thomas Morley thomasmorle...@googlemail.com writes: [...] Why would you want to have ChordNames internal to a Staff? It was requested by a german user. He wants