Dear LilyPond developers,
currently the scm/ subdirectory of LilyPond is flat, and all guile
modules defined there are immediate submodules of scm. Related modules
are not grouped into guile submodules, but marked with a name prefix
(e.g. the framework-* group).
Is this a conscious design
* 2013-01-19 18:20 +0100 Ian Hulin:
On 19/01/13 15:34, Johannes Rohrer wrote:
currently the scm/ subdirectory of LilyPond is flat, and all guile
modules defined there are immediate submodules of scm. Related
modules are not grouped into guile submodules, but marked with a
name prefix (e.g
* 2013-01-04 20:38 +0100 d...@gnu.org:
On 2013/01/04 19:32:02, J. Rohrer wrote:
[Thus I learned something about contexts today: I would not have
naively expected
\context { \AlreadyDefinedContext \name NewContext },
to actually create a new, independent context, since the command
the
grob is produced from a Voice-level engraver instance.
to write a Staff-level Chord_thinout_engraver that still works per
voice. Is that the way to go? Other ideas?
Best regards,
Johannes Rohrer
___
lilypond-devel mailing list
lilypond-devel
