Re: Can't use \clef inside NoteNames and similar contexts

[Reinhold Kainhofer]

Am Mittwoch, 22. Dezember 2010, um 16:08:10 schrieb Michael Ellis:
> Carl, thanks for taking the time to figure it out!  I really appreciate the
> help. It's good to know there's a workaround.

Yes, there is a workaround (which causes lot of work for you!), but I would 
regard this as a bug in the clef command, so bug squad please open a bug 
report (I'm cc'ing the bug-lilypond list).

In particular, the problem appears not only with NoteNames, but with any other 
context that is used without a surrounding staff, i.e. FiguredBass, 
ChordNames, etc. The offending code can be found in line 138 of scm/parser-
clef.scm (function make-clef-set):

          (context-spec-music seq 'Staff))

If you use \clef inside a music expression that is not surrounded by a staff, 
lilypond tries to fine the surrounding staff. As that fails, apparently, it 
simply picks up the first Staff context it finds...

The problem happens with all of the following contexts:
  -) NoteNames
  -) FiguredBass
  -) ChordNames
  -) FretBoards
  -) even with Lyrics!

A small example showing the problems with any of these contexts is attached. 
Note that the first two staves in that example should have a treble clef. 
However, any of the 5 example contexts will cause the first staff to employ a 
bass clef instead (i.e. the clef given in the clef command inside the 
NoteNames/FiguredBAss/ChordNames/FretBoards/Lyrics context!)

Cheers,
Reinhold
-- 
------------------------------------------------------------------
Reinhold Kainhofer, address@hidden, http://reinhold.kainhofer.com/
 * Financial & Actuarial Math., Vienna Univ. of Technology, Austria
 * http://www.fam.tuwien.ac.at/, DVR: 0005886
 * LilyPond, Music typesetting, http://www.lilypond.org

notename.ly
Description: Text Data

notename.pdf
Description: Adobe PDF document