Re: Fingerings and stringnumbering don't avoid collision with accidentals!

[Graham Percival]

Han-Wen Nienhuys wrote:
> Graham Percival escreveu:
> > Please make sure you send an example that can compile; I had to change
> > the #3 to #'3.  
>
> sounds like another bug.

Curious.  Here's my exact input and output:
----
\version "2.11.4"
\paper {ragged-right    = ##t }
{\set fingeringOrientations    = #'(left)    <cis''-3>}
{\set strokeFingerOrientations = #'(left)    <cis''-\rightHandFinger #3>}
{\set stringNumberOrientations = #'(left)    <cis''\3>}
----
tsubasa:~/tmp gperciva$ lilypond bug.ly
GNU LilyPond 2.11.4
Processing `bug.ly'
Parsing...
bug.ly:4:70: error: GUILE signaled an error for the expression beginning 
here
{\set strokeFingerOrientations = #'(left)    <cis''-\rightHandFinger #
                                                                      3>}
Unbound variable: 3>}
bug.ly:4:52: wrong type for argument 1.  Expecting number or string, 
found #<unspecified>
{\set strokeFingerOrientations = #'(left)    <cis''-
                                                    \rightHandFinger #3>}
Interpreting music...
Preprocessing graphical objects...
Interpreting music...
programming error: Not a music type
continuing, cross fingers
Bus error
tsubasa:~/tmp gperciva$
----


The culprit appears to be the lack of a space after the 3, in "#3>}", 
not the ' as I originally though.  (when I added the ' I automatically 
added a space)
But it worked on Windows without a space...?

Cheers,
- Graham