2012/10/29 David Kastrup <d...@gnu.org>:
> The definition of Devnull is
>
> \context {
> \name "Devnull"
> \type "Engraver_group"
>
> %% don't want to route anything out of here:
> \alias "Staff"
> \alias "Voice"
> \description "Silently discards all musical information given to this
> context."
> }
>
> and it is accepted by \Score. So it will capture overrides to Staff and
> Voice (and Devnull), but anything else will create a context of the
> appropriate type in the containing \Score context and direct the
> override there.
>
> To change this, Devnull would either need to contain more aliases, or it
> would need to \accept the respective contexts itself or have a
> \defaultchild accepting them. But in the latter cases, those contexts
> would be fully operative, defeating the idea of Devnull.
>
> Should Devnull try to be an alias for every context type? Good
> question.
I think it should.
Janek
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
