Kieren MacMillan <kieren_macmil...@sympatico.ca> writes: > Hi Dan (et al.), > >> On Feb 6, 2020, at 09:32, Kieren MacMillan <kieren_macmil...@sympatico.ca> >> wrote: >>> So what I want to work on is some sort of ”Splittable Staff“. > > Just to be clear, Valentin wrote that, not me. =) > >> This terminology looks at the use case from a point of view that >> might not be very consistent with LilyPond. Let's think carefully >> about what we want to call this, because names have a way of >> coloring the problem-solving process. > > Agreed.
Without having even looked at the problem, let me add that the programming/Scheme layer of LilyPond often allows to _map_ a problem description in composer terms to an approach in LilyPond terms. So sometimes finding a consistent way of describing and structuring a problem may garner the necessary help from the list that then provides a solution that talks to the user in composer terms, and to the program in LilyPond terms. End of pontification. Just something that tends to lurk in the back of my mind and sometimes might give a different outlook on a problem. -- David Kastrup My replies have a tendency to cause friction. To help mitigating damage, feel free to forward problematic posts to me adding a subject like "timeout 1d" (for a suggested timeout of 1 day) or "offensive".
