lilypond-1.3.66

diff --git a/Documentation/regression-test.tely b/Documentation/regression-test.tely
index 51cc4d1460f073d1d0fc635e655af67188bdf33c..60e4ba57a85c60fd49dfdbc960bc83479fd63294 100644 (file)
--- a/Documentation/regression-test.tely
+++ b/Documentation/regression-test.tely
@@ -43,11 +43,17 @@ a column.  The dots go along as rests are shifted to avoid collisions.
 
 @mudelafile{dots.ly}
 
+Accidentals worki: the second note does not get a sharp. The third and
+fourth show forced and courtesy accidentals
+
+@mudelafile{accidental.ly}
+
 Multiple measure rests do not collide with barlines and clefs.  They
 are not expanded when you set @code{Score.skipBars}.  Although the
 multi-measure-rest is a Spanner, minimum distances are set to keep it
 colliding from barlines. 
 
+
 @mudelafile{multi-measure-rest.ly}
 
 If @code{Score.skipBars} is set,
@@ -130,7 +136,6 @@ not set.  Main note scripts don't end up on the grace note.
 
 @mudelafile{grace.ly}
 
-
 @section Beams, slurs and other spanners
 
 Beaming is generated automatically. Beams may cross bar lines. In that

diff --git a/lily/spacing-engraver.cc b/lily/spacing-engraver.cc
index 0f26e7ca16c17c2949835f847d1afb113f2e4a2f..a61b79a2235a2f94d2388551659b8508655db6c9 100644 (file)
--- a/lily/spacing-engraver.cc
+++ b/lily/spacing-engraver.cc
@@ -22,7 +22,6 @@ int
 Rhythmic_tuple::time_compare (Rhythmic_tuple const &h1,
                              Rhythmic_tuple const &h2)
 {
-  
   return (h1.end_ - h2.end_ ).sign ();
 }
 

diff --git a/scm/generic-property.scm b/scm/generic-property.scm
index 506be8a760c5be68ea8a5f113308a44e19308287..3b3d46665fcf3985eb8dab281d789765de6ce171 100644 (file)
--- a/scm/generic-property.scm
+++ b/scm/generic-property.scm
@@ -1,4 +1,8 @@
 
+; BROKEN as of 1.3.55, FIXME
+;
+
+
 ;
 ; Format: 
 ; (cons 'Type name