Currently, my greatest problem is to identify grobs so that I can
modify their properties.
I suggest a tool `grob' which accepts a LilyPond code fragment (either
as an argument to the tool or read in interactively using
e.g. readline), returning the context and grob.
Example:
grob a_"foo"
should return something like this:
`a': `Staff.NoteHead'
`Staff.Stem'
`"foo"': Staff.TextScript
In case this isn't possible, I suggest to add a \what keyword to
LilyPond which emits information on its argument to stdout (but having
no other effect):
\what a_"foo"
The trial-and-error method which is necessary at the moment due to
lacking documentation costs way too much time.
Werner
_______________________________________________
Bug-lilypond mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/bug-lilypond
