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

[lilypond.git] / input / lsr / inserting-score-fragments-above-a-staff,-as-markups.ly

diff --git a/input/lsr/inserting-score-fragments-above-a-staff,-as-markups.ly b/input/lsr/inserting-score-fragments-above-a-staff,-as-markups.ly
index 976721b3865c0651c6df9006229d0c616fbcf2bd..66f1a637812674e5e436203840e548820798b108 100644 (file)
--- a/input/lsr/inserting-score-fragments-above-a-staff,-as-markups.ly
+++ b/input/lsr/inserting-score-fragments-above-a-staff,-as-markups.ly
@@ -1,6 +1,6 @@
 %% 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.51"
+\version "2.13.1"
 
 \header {
   lsrtags = "staff-notation"
@@ -12,6 +12,7 @@ contains a @code{\\score} block instead of texts or marks.
 "
   doctitle = "Inserting score fragments above a staff, as markups"
 } % begin verbatim
+
 tuning = \markup {
   \score {
     \new Staff \with { \remove "Time_signature_engraver" }
@@ -37,3 +38,4 @@ tuning = \markup {
   g8 a g a
   g8 a g a
 }
+