Re: [Lilypond-auto] Issue 2948 in lilypond: Patch: Applies scheme indentation according to the GNU guidelines

[lilypond]

Comment #26 on issue 2948 by address@hidden: Patch: Applies scheme indentation  
according to the GNU guidelines
http://code.google.com/p/lilypond/issues/detail?id=2948

Applying the script tampers with the inside of strings in  
scm/define-context-properties:
@@ -516,9 +516,9 @@ voices is preserved.
 @example
 @{
   r1 r1*3 R1*3
-  \\set Score.skipBars= ##t
-  r1*3 R1*3
address@hidden
+     \\set Score.skipBars= ##t
+     r1*3 R1*3
+     @}
 @end example")
      (skipTypesetting ,boolean? "If true, no typesetting is done,
 speeding up the interpretation phase.  Useful for debugging large

and also in scm/define-grob-properties:
@@ -970,7 +970,7 @@ line just before it would otherwise stop.")
      (toward-stem-shift ,number? "Amount by which scripts are shifted
 toward the stem if their direction coincides with the stem direction.
 @code{0.0} means keep the default position (centered on the note
-head), @code{1.0} means centered on the stem.  Interpolated values are
+                                                     head), @code{1.0}  
means ce
 possible.")
      (transparent ,boolean? "This makes the grob invisible.")

@@ -1001,7 +1001,7 @@ one below this grob.")
 happen?")
      (whiteout ,boolean? "If true, the grob is printed over a white
 background to white-out underlying material, if the grob is visible.
- Usually #f by default.")
+Usually #f by default.")
      (width ,ly:dimension? "The width of a grob measured in staff
 space.")
      (word-space ,ly:dimension? "Space to insert between words in

I think the automatically generated commit should get reverted as a whole  
(that's easiest on the commit history), and then additional work needs to  
be done to bring the code base into a state where it behaves nicer under  
fixscm and/or fixscm needs to be amended (though its current behavior  
corresponds to untweaked Emacs, and it probably makes sense to have the  
source act benign under that premise as quite a few people actually use  
untweaked Emacs).

--
You received this message because this project is configured to send all  
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings