Re: besideCN seems to have stopped working

2012-06-01 Thread Robin Bannister 
Gerry Prosser wrote: 
Removing the dollars certainly seems to work - thank you! 
Hopefully someone cleverer than us will be along shortly to explain why ...


It was David Kastrup's work which makes it possible to remove the dollars. 


And please note that any dollars you remove should of course go directly to him 
...


Cheers, 
Robin


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

besideCN seems to have stopped working

2012-05-31 Thread Gerry Prosser 
besideCN is used to display capo settings along with guitar chord names,
but with 2.15.39 I get error message 'Unbound variable: $which-side'

the last working score I have was compiled with 2.15.13

besideCN = #(define-music-function (parser location which-side added-text)
(integer? string?) #{\once \override ChordNames.ChordName #'stencil =
#(lambda (grob) (ly:grob-set-property! grob 'text (markup #:put-adjacent 0
$which-side ; #LEFT or #RIGHT
(ly:grob-property grob 'text) $added-text)) (ly:text-interface::print
grob)) #})

Chords = \new ChordNames \chordmode {
  \besideCN #LEFT Capo1  d1 fis2:m7 b2:m e1:m7 a
}

any clues, anyone, please ?

Gerry
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: besideCN seems to have stopped working

2012-05-31 Thread Choan Gálvez 

On 5/31/12 12:09 , Gerry Prosser wrote:

besideCN is used to display capo settings along with guitar chord names,
but with 2.15.39 I get error message 'Unbound variable: $which-side'

the last working score I have was compiled with 2.15.13

besideCN = #(define-music-function (parser location which-side
added-text) (integer? string?) #{\once \override ChordNames.ChordName
#'stencil = #(lambda (grob) (ly:grob-set-property! grob 'text (markup
#:put-adjacent 0 $which-side ; #LEFT or #RIGHT
(ly:grob-property grob 'text) $added-text)) (ly:text-interface::print
grob)) #})

Chords = \new ChordNames \chordmode {
   \besideCN #LEFT Capo1  d1 fis2:m7 b2:m e1:m7 a
}

any clues, anyone, please ?


Removing the $ prefixes from both $which-side and $added-text worked for 
me. Actually, I'm not sure why it worked as I'm still an scheme illiterate.


Best.
--
Choan Gálvez

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: besideCN seems to have stopped working

2012-05-31 Thread David Kastrup 
Choan Gálvez choan.gal...@gmail.com writes:

 On 5/31/12 12:09 , Gerry Prosser wrote:

 besideCN = #(define-music-function (parser location which-side
 added-text) (integer? string?) #{\once \override ChordNames.ChordName
 #'stencil = #(lambda (grob) (ly:grob-set-property! grob 'text (markup
 #:put-adjacent 0 $which-side ; #LEFT or #RIGHT
 (ly:grob-property grob 'text) $added-text)) (ly:text-interface::print
 grob)) #})

 Chords = \new ChordNames \chordmode {
\besideCN #LEFT Capo1  d1 fis2:m7 b2:m e1:m7 a
 }

 any clues, anyone, please ?

 Removing the $ prefixes from both $which-side and $added-text worked
 for me. Actually, I'm not sure why it worked as I'm still an scheme
 illiterate.

One could read in the documentation and/or run convert-ly.  That you
guessed right without either while professing to be a scheme illiterate
(Scheme literacy would not actually helped since the earlier behavior of
$xxx inside of #{ ... #} had nothing to do with Scheme) is a bit of
endorsement for the change: its intent was to reduce the amount of clue
required for writing working code.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: besideCN seems to have stopped working

2012-05-31 Thread David Kastrup 
Gerry Prosser ge...@chalkblue.co.uk writes:

 besideCN is used to display capo settings along with guitar chord
 names, but with 2.15.39 I get error message 'Unbound variable:
 $which-side'

 the last working score I have was compiled with 2.15.13

 besideCN = #(define-music-function (parser location which-side
 added-text) (integer? string?) #{\once \override ChordNames.ChordName
 #'stencil = #(lambda (grob) (ly:grob-set-property! grob 'text (markup
 #:put-adjacent 0 $which-side ; #LEFT or #RIGHT
 (ly:grob-property grob 'text) $added-text)) (ly:text-interface::print
 grob)) #})

 Chords = \new ChordNames \chordmode {
   \besideCN #LEFT Capo1  d1 fis2:m7 b2:m e1:m7 a
 }

 any clues, anyone, please ?

convert-ly -ed

is used for upgrading the syntax of files written for an earlier version
of LilyPond to the present.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: besideCN seems to have stopped working

2012-05-31 Thread Gerry Prosser 
Choan ... if you are scheme-illiterate, what does that make me ?  Removing
the dollars certainly seems to work - thank you! Hopefully someone cleverer
than us will be along shortly to explain why .. G

On 31 May 2012 18:03, Choan Gálvez choan.gal...@gmail.com wrote:

 On 5/31/12 12:09 , Gerry Prosser wrote:

 besideCN is used to display capo settings along with guitar chord names,
 but with 2.15.39 I get error message 'Unbound variable: $which-side'

 the last working score I have was compiled with 2.15.13

 besideCN = #(define-music-function (parser location which-side
 added-text) (integer? string?) #{\once \override ChordNames.ChordName
 #'stencil = #(lambda (grob) (ly:grob-set-property! grob 'text (markup
 #:put-adjacent 0 $which-side ; #LEFT or #RIGHT
 (ly:grob-property grob 'text) $added-text)) (ly:text-interface::print
 grob)) #})

 Chords = \new ChordNames \chordmode {
   \besideCN #LEFT Capo1  d1 fis2:m7 b2:m e1:m7 a
 }

 any clues, anyone, please ?


 Removing the $ prefixes from both $which-side and $added-text worked for
 me. Actually, I'm not sure why it worked as I'm still an scheme illiterate.

 Best.
 --
 Choan Gálvez

 __**_
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/**listinfo/lilypond-userhttps://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: besideCN seems to have stopped working

2012-05-31 Thread Gerry Prosser 
David ... thanks, and yes indeed. And I run convert-ly on every new score I
create with denemo, so there really is no excuse for not engaging brain on
this occasion 8-)

Thanks for all the gentle admonishments from around the community .

G

On 31 May 2012 19:30, David Kastrup d...@gnu.org wrote:

 Gerry Prosser ge...@chalkblue.co.uk writes:

  besideCN is used to display capo settings along with guitar chord
  names, but with 2.15.39 I get error message 'Unbound variable:
  $which-side'
 
  the last working score I have was compiled with 2.15.13
 
  besideCN = #(define-music-function (parser location which-side
  added-text) (integer? string?) #{\once \override ChordNames.ChordName
  #'stencil = #(lambda (grob) (ly:grob-set-property! grob 'text (markup
  #:put-adjacent 0 $which-side ; #LEFT or #RIGHT
  (ly:grob-property grob 'text) $added-text)) (ly:text-interface::print
  grob)) #})
 
  Chords = \new ChordNames \chordmode {
\besideCN #LEFT Capo1  d1 fis2:m7 b2:m e1:m7 a
  }
 
  any clues, anyone, please ?

 convert-ly -ed

 is used for upgrading the syntax of files written for an earlier version
 of LilyPond to the present.

 --
 David Kastrup


 ___
 lilypond-user mailing list
 lilypond-user@gnu.org
 https://lists.gnu.org/mailman/listinfo/lilypond-user

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: besideCN seems to have stopped working

2012-05-31 Thread David Kastrup 
Gerry Prosser ge...@chalkblue.co.uk writes:

 David ... thanks, and yes indeed. And I run convert-ly on every new
 score I create with denemo, so there really is no excuse for not
 engaging brain on this occasion 8-)

 Thanks for all the gentle admonishments from around the community
 .

Well, it is a frequent question about an invasive change.  And one
argument in favor of going through with it was that convert-ly actually
was able to convert a sizeable ratio of Scheme code automatically.

Since I spent considerable time getting convert-ly to do an
unprecedented amount of work, you can find me pointing to it frequently.

With this particular syntax change, remove everything that looks like a
mistake will tend to work as well, as someone else noted in a parallel
answer, and that actually was the motivation for the change.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: besideCN seems to have stopped working

2012-05-31 Thread David Kastrup 
Gerry Prosser ge...@chalkblue.co.uk writes:

 Choan ... if you are scheme-illiterate, what does that make me ? 
 Removing the dollars certainly seems to work - thank you! Hopefully
 someone cleverer than us will be along shortly to explain why .. G

Actually, I was not able to explain the _previous_ behavior
satisfactorily.  If you take a look at the history of the Extending
LilyPond manual, you'll find that I rewrote the sections focused around
#{ ... #} repeatedly.  At some point of having to explain the
three-or-whatever uses of $ inside of #{ ... #} I got annoyed to the
point of letting $ have just a single function, and that in- or outside
of #{ ... #} alike, and letting variables and expressions inside of
#{ ... #} work as a naive person would expect without throwing around
dollar signs in incomprehensible manners.

Check out the 2.14 manuals for an approximation of previous behavior.
If you feel like you understand the rationale behind it, you are a
cleverer person than I am.  I preferred dumbing down LilyPond to a level
where I don't feel guilty when explaining it.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user