Hi Werner, On 19/12/11 05:47, Werner LEMBERG wrote: > >>> So either I interpret something wrong into what you are saying, or >>> you interpret something wrong into what the Guile developers are >>> saying, or the Guile developers interpret something wrong into what >>> usability should be saying. Or a bit of each. >> >> *Shrug*. It's very easy to get things confused with two different >> projects (Guile and LilyPond) developing at different speeds and >> with fundamental deep-level changes going on in each (like >> byte-compilation in Guile and your spring-clean on the parser stuff, >> also I only get chance to work on Lily in bursts, and I'm not able >> to swap between development with the two Guile versions as easily as >> I'd like. > > I strongly suggest that we try to directly involve Andy `Mr. Guile' > Wingo. IIRC, he was already helpful in resolving previous problems, > and he as the main developer of Guile could give helpful insights to > find a satisfying solution. > > Ian, can you do that, with CCing the lilypond-devel list? (And the > lilypond-devel list maintainer, please have an eye to the queue so > that his mails get forwarded quickly). > I'm already on it, sort of. If it looks like something is definitely on the Guile/Scheme side of the fence, I do contact Andy and Ludovic, and normally then put a post on guile-user and/or guile-bugs.
For example, there is a lot of discussion on guile-developers on how to support a feature which has been deprecated (local-eval), and it turns out it was useful to David K in his parser spring-clean, so I flagged it with Guile and it's now in their bug-tracking system. It looks like they're going to provide us with a solution, but the discussion on the thread is way over my head. . . My current woes with the markup facility are mainly on the LilyPond side, and how it's currently implemented, and how to get from "here" (Guile V1.8) to "there" (Guile V2.0). I don't think we need to involve the Guile guys on this bit yet. Anyhow, thanks for the reminder, Werner, Cheers, Ian _______________________________________________ lilypond-devel mailing list [email protected] https://lists.gnu.org/mailman/listinfo/lilypond-devel
