Janek Warchoł <janek.lilyp...@gmail.com> writes:
> Hi Jan-Peter,
>
> 2014-07-29 9:34 GMT+02:00 Jan-Peter Voigt <jp.vo...@gmx.de>:
>> Hi Janek,
>>
>> your predefined context are cool :)
>
> Thanks!
>
>> I see them in context with my lalily templates -- they will of course
>> benifit. And the editionEngraver can indeed take advantage from specific
>> context names. But still there need to be a way to separate (for
>> example) violin 1 and 2.
>
> As i said, defining new instrument contexts is very cheap - you can just do
>
> \newInstrument "ViolinI" "Violin" "StaffGroup"\with { } \with { }
> \newInstrument "ViolinII" "Violin" "StaffGroup"\with { } \with { }
>
> and have ViolinI and ViolinII available.
Would it be feasible to put the context mods _before_ some reasonably
related argument, possibly like
\newInstrument \with {} "ViolinI" "Violin" \with {} "StaffGroup"
or probably
\newInstrument "Violin" \with {} "ViolinI" \with {} "StaffGroup" ?
Because when they are before a related non-optional argument, one can
make them optional. Then if they are just \with {} anyway, you can omit
them.
--
David Kastrup
_______________________________________________
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user
