a couple of regression tests

[James Bailey]

So, as a result of my new-found ability to quickly and easily look at the 
regression tests, I noticed some things:

The regression test for beam-quant-standard has a (to me) odd warning:

Processing `beam-quant-standard.ly'
Parsing...
Interpreting music... [8][16][24]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
warning: Error in beam quanting.  Expected (-0.19,-0.19) found (0.0 . 0.0).
warning: Error in beam quanting.  Expected (-0.19,-0.19) found (0.0 . 0.0).
warning: Error in beam quanting.  Expected (-0.19,-0.19) found (0.0 . 0.0).
warning: Error in beam quanting.  Expected (3,3) found (3.5 . 3.5).
warning: Error in beam quanting.  Expected (2.19,2.19) found (2.81 . 2.81).
Layout output to `beam-quant-standard.ps'...
Converting to `./beam-quant-standard.pdf'... 

I don't know if this is the desired behavior, but I thought I'd point it out. 
If it is the desired behavior, I may make a suggestion on how to make that a 
bit more apparent in the regtest description.

• beam-multiple-cross-staff has beams that collide with a notehead. see the 
following warning:

Processing `beam-multiple-cross-staff.ly'
Parsing...
Interpreting music... 
Preprocessing graphical objects...
beam-multiple-cross-staff.ly:24:20: warning: ignoring too many clashing note 
columns
    b8[ b16 \stemUp 
                    b,,16 ]
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
warning: no viable initial configuration found: may not find good beam slope
Layout output to `beam-multiple-cross-staff.ps'...
Converting to `./beam-multiple-cross-staff.pdf'... 

• beam-funky.ly has beams that collide with ledger lines. This may be related 
to one of the existing kneed-beams/cross-staff beams issues already in the 
tracker.

• beam-cross-staff.ly generates warnings, but the output is fine:

Processing `beam-cross-staff.ly'
Parsing...
Interpreting music... 
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
warning: no viable initial configuration found: may not find good beam slope
warning: no viable initial configuration found: may not find good beam slope
Layout output to `beam-cross-staff.ps'...
Converting to `./beam-cross-staff.pdf'... 

bar-scripts.ly is a bit confusing for me. There's a \break, but it's not 
apparent, shortInstrumentName is set, which should show up on the line that has 
the break, but I don't see it. Also, the description implies that a mark should 
appear on an invisible barline, but I don't see that either. Does this do what 
it's supposed to and I'm just misunderstanding it, or is it supposed to do 
something and it isn't?

baerenreiter-sarabande.ly does not displaye within the margins of the pdf 
documentation. Actually compiling the regtest is fine and the html version is 
fine, however.