Still good, still useful. The hesitation on the user interface seems foolish. Without a stable user interface this becomes a function for just one user.
Changing the current global variable 'partcombine-chord-range' will not become the user interface. There is no context in which to set that range, because \parcombine does its job outside any context: variable = \partcombine \violinOne \violinTwo So the choices are 1) a variant \partcombineSelectChordRange that takes an extra argument 2) an optional argument to \partcombine If you push this I'll submit the patch for option (2) https://codereview.appspot.com/144170043/ _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
