Re: [PATCH] Add scheme engraver for StaffTab notation

[Carl Sorensen]

On 2/25/15 8:36 AM, "David Kastrup" <address@hidden> wrote:

>
>The current solution does not switch modes apart from jumping into
>Scheme mode for #'guitar-tuning and we could easily get rid of that #'
>as well (yes, that will actually cause a measurable speedup as I found
>out in the course of issue 2883).

Another advantage of the current system is that the input is disconnected
from the internals, that is, it is not necessary to know the details of
how stringTunings are stored in order to add a new tuning.

I believe that the input files should use native LilyPond syntax as much
as reasonable, and that string-tunings-init.ly should use
\makeDefaultStringTuning directly on the chord.

I think that it is a good improvement to let \makeDefaultStringTuning have
either a stringTuning or a chord as an input variable, and thus allow

\makeDefaultStringTuning #'cello-tuning <c, g, d a>

in addition to 

\makeDefaultStringTuning #'cello-tuning \stringTuning <c, g, d a>

Thanks,

Carl