Am Mo., 20. Jan. 2020 um 23:52 Uhr schrieb David Kastrup <d...@gnu.org>:
>
> Thomas Morley <thomasmorle...@gmail.com> writes:
>
> > Am Mi., 15. Jan. 2020 um 01:23 Uhr schrieb David Kastrup <d...@gnu.org>:
> >
> >> We need to put out the difference between # and $ even for beginners.
> >> Basically # can only be used for stuff where you can figure out the
> >> meaning in context without even looking at the Scheme expression
> >> involved. Which has the advantage that the Scheme expression does not
> >> get looked at earlier than expected. While $ (like \ ) can change the
> >> interpretation of stuff around it depending on what it evaluates to but
> >> that means that LilyPond may try evaluating it earlier than expected.
> >>
> >> The typical problem case we have is
> >>
> >> blabla = something
> >> \blabla
> >>
> >> when LilyPond is not sure that something is a complete expression before
> >> looking at what is following it.
> >>
> >> --
> >> David Kastrup
> >
> > I just stumbled across:
> >
> > ~$ lilydevel scheme-sandbox
> > GNU LilyPond 2.19.83
> > Processing
> > `/home/hermann/lilydevel/usr/share/lilypond/current/ly/scheme-sandbox.ly'
> > Parsing...
> > guile> (display-lily-music #{ $(ly:parser-include-string "\\tweak
> > color $red") b4 #})
> > \tweak color #'(1.0 0.0 0.0) b4
> >
> >
> > If you do the same with #red, below returns:
> > \tweak color #"red" b4
> >
> > Not sure what we may want here...
>
> Uh, you lost me there.
>
> guile> (display-lily-music #{ $(ly:parser-include-string "\\tweak color
> #red") b4 #})
> \tweak color #'(1.0 0.0 0.0) b4
>
>
> --
> David Kastrup
Uh - oh, I can't reproduce anymore what I had meant to see.
Must have done a mistake somewhere.
Sorry for the noise.
Harm
