lilypond-book robustness: ensure EOL at the end of @verbatim

[lilypond.git] / input / lsr / outputting-the-version-number.ly

diff --git a/input/lsr/outputting-the-version-number.ly b/input/lsr/outputting-the-version-number.ly
index 63f044725312d497e425a1a5682e9672c72a440b..bade2a58eebb43cf9c91758ef984851be40a68fb 100644 (file)
--- a/input/lsr/outputting-the-version-number.ly
+++ b/input/lsr/outputting-the-version-number.ly
@@ -1,13 +1,17 @@
-%% Do not edit this file; it is auto-generated from input/new
+%% Do not edit this file; it is auto-generated from LSR http://lsr.dsi.unimi.it
 %% This file is in the public domain.
-\version "2.11.61"
+\version "2.13.1"
 
 \header {
-  lsrtags = "text"
+  lsrtags = "text, titles"
+
   texidoc = "
-By putting the output of @code{lilypond-version} into a lyric or a
-text markup, it is possible to print the version number of LilyPond in
-a score, or in a document generated with @code{lilypond-book}.
+By putting the output of
+    @code{lilypond-version} into a lyric, it is possible to print the 
+    version number of LilyPond in a score, or in a document generated
+    with @code{lilypond-book}.  Another possibility is to append the 
+    version number to the doc-string, in this manner: 
+
 "
   doctitle = "Outputting the version number"
 } % begin verbatim
@@ -15,8 +19,10 @@ a score, or in a document generated with @code{lilypond-book}.
 \score {
   \new Lyrics {
     \override Score.RehearsalMark #'self-alignment-X = #LEFT
-    \mark #(ly:export (string-append "Processed with LilyPond version "
-                       (lilypond-version)))
+    \mark #(string-append "Processed with LilyPond version " (lilypond-version))
     s2
   }
 }
+
+
+