fret-diagrams.scm:657:42: Wrong type: #f

2015-08-19 Thread ClausRogge
I have two nearly identical pairs of code files, one calling the other. One of them works, the other one gives me the strange error quoted. Layout file one: %%% \version 2.18.2 \paper {#(set-default-paper-size a4) indent = 0 top-margin = 0\cm left-margin = 1\cm right-margin = 1\cm

Re: fret-diagrams.scm:657:42: Wrong type: #f

2015-08-20 Thread ClausRogge
Well, your code is not a minimal example and it does not compile and thus it does not show the error. All I can say for now: I suspect your linebreaking of the strings for the fret-diagram. Hi Harm, thanks for replying ... what is a minimal example? Anything I can do to make things easier ...

Re: fret-diagrams.scm:657:42: Wrong type: #f

2015-08-22 Thread ClausRogge
OK thanks for all your suggestions ... the error was very simple - one space too much here \stopStaff s2 s_\markup {\bold D dur}^\markup{{\fret-diagram #s:6;h:5; -!! 6-2;6-3;6-5;5-2;5-4;5-5;4-2;4-4;4-5;3-2;3-4;2-2;2-3;2-5;1-2;1-3;1-5;}} I didn't show in my posting because of the automatic line

Unwanted barree finger in fret diagram

2015-09-08 Thread ClausRogge
Why is there a barre sign in these fret diagrams? Far as I cn see, I haven't told LP to do a barre finger in teh first fret ... minimal example, this time I hope: \version "2.18.2" \paper{#(set-default-paper-size "a4") indent = 0 top-margin = 0\cm left-margin = 1\cm right-margin = 1.5\cm

Re: Unwanted barree finger in fret diagram

2015-09-08 Thread ClausRogge
Thank you! Solved the issue ... funny that I didn't come across this earlier -- View this message in context: http://lilypond.1069038.n5.nabble.com/Unwanted-barree-finger-in-fret-diagram-tp180816p180820.html Sent from the User mailing list archive at Nabble.com.

Re: Line numbers in editor window

2015-09-17 Thread ClausRogge
AFAIK, the Mac version is the only one that comes with it's own editor and I used that for nearly ten years, gravely missing the line numbering. Finally discovered Frescobaldi which is a fantastic editor! It helps you to keep an eye on all these brackets as well -- View this message in context: