From: David Kastrup Date: Thu, 19 Sep 2013 12:52:26 +0000 (+0200) Subject: Issue 3565: Doc, EG: LilyPond's getting too smart for the "Inline Scheme code" section X-Git-Tag: release/2.17.27-1~2^2~5 X-Git-Url: https://git.donarmstrong.com/?a=commitdiff_plain;h=85c1631b1fa42cc767df2d8087588af15381241d;p=lilypond.git Issue 3565: Doc, EG: LilyPond's getting too smart for the "Inline Scheme code" section The "Inline Scheme code" section already was embarrassing enough during its last revision, when a trivial syntactic change was all that was required in order to have the stated problem go away without requiring to revert to Scheme. Since then, the situation has further deteriorated: the originally "what we would like to do but it fails" example works entirely unchanged without a hitch. --- diff --git a/Documentation/extending/programming-interface.itely b/Documentation/extending/programming-interface.itely index 759c1dfc4c..311a138073 100644 --- a/Documentation/extending/programming-interface.itely +++ b/Documentation/extending/programming-interface.itely @@ -1303,16 +1303,15 @@ my-callback = #(lambda (grob) @node Inline Scheme code @section Inline Scheme code -TODO: the example for this section is ill-chosen since -@example -F = -\tweak font-size #-3 -\flageolet -@end example -(note the @samp{-} marking it as a post event) will actually work fine -for the stated purpose. Until this section gets a rewrite, let's -pretend we don't know. +TODO: after this section had been written, LilyPond has improved +to the point that finding a @emph{simple} example where one would +@emph{have} to revert to Scheme has become rather hard. + +Until this section gets a rewrite, let's pretend we don't know. The main disadvantage of @code{\tweak} is its syntactical -inflexibility. For example, the following produces a syntax error. +inflexibility. For example, the following produces a syntax error +(or rather, it did so at some point in the past). @example F = \tweak font-size #-3 -\flageolet