[EMAIL PROTECTED] writes:
> > Can you be more specific about "lacking documentation"? I recently
> > added a section on adjusting output to the tutorial, which explains
> > how to go about tweaking.
>
> Yes, this was of great help how to do it in general, but without
> knowing exactly which inpu
> Try \apply #(lambda (x) (display x) x) ...
Aah, this is exactly what I want!
> * the mapping from syntax to parse trees is not entirely trivial. For
> example
>
>R1
>
> is internall converted to
>
> { \spanrequest \start mmrest
> s1
> \spanrequest \start mmrest
> }
>
[EMAIL PROTECTED] writes:
> 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 a
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"
s
