lilypond-auto
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Lilypond-auto] Issue 4348 in lilypond: Patch: Part combiner: move d


From: lilypond
Subject: Re: [Lilypond-auto] Issue 4348 in lilypond: Patch: Part combiner: move direction handling out of iterator
Date: Sun, 19 Apr 2015 17:50:28 +0000


Comment #9 on issue 4348 by address@hidden: Patch: Part combiner: move direction handling out of iterator
https://code.google.com/p/lilypond/issues/detail?id=4348

\displayLilyMusic tries to recognize LilyPond commands based on the Scheme structures they create. This is often a sophisticated programming task.

Maintaining \displayLilyMusic often requires that we re-teach it to recognize the output of commands that we change, adding a burden of synchronization to LilyPond. \displayLilyMusic does not even try to recognize some commands
   \displayLilyMusic \new Voice {\voiceTwo b4}

The goal of this patch is to let \partcombine use the standard \voiceXxx commands, rather than re-implement them independently. I suggest we need only preserve the useful parts of existing Lilypond. I have trouble imagining a use for \displayLilyMusic\partcombine but the changed output seems as useful as the original.

Teaching \displayLilyMusic to reverse-engineer \partcombine as suggested in comment #7 might be possible, but I think it would be unwise. I think the resulting interdependencies in code would be enough of a burden to stop any further improvements to \partcombine.

--
You received this message because this project is configured to send all issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings



reply via email to

[Prev in Thread] Current Thread [Next in Thread]