Re: Issue 1859 in lilypond: let \contextStringTunings affect only current context.

[David Kastrup]

address@hidden writes:

> Comment #3 on issue 1859 by address@hidden: let
> \contextStringTunings affect only current context.
> http://code.google.com/p/lilypond/issues/detail?id=1859
>
> Good, so this bug seems really fixed.

The way the code had been written originally, I suspect that it was
written with a particular use case in mind.  My guess would be that the
side-effects were worse than the cure, but until we get an explicit
report of the purported problem, I would prefer to have the code stick
with the straightforward version that corresponds with both function
name as well as documentation.

Actually, I don't like the entire approach all too much, so I am
currently working on making a define-scheme-function thingy that can
take Lilypond arguments like define-music-function but produces not a
music but a Scheme expression.

That would make it easy to define a "Scheme" function taking a Lilypond
chord as input and returning a string pitch list, a much more
straightforward interface than the current set of contraptions including
\contextStringTunings.

-- 
David Kastrup