Re: lilypond Documentation/user/examples.itely Docu...

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Re: lilypond Documentation/user/examples.itely Docu...

Graham Percival-2

On 19-Aug-05, at 11:18 AM, Han-Wen Nienhuys wrote:

> Index: lilypond/ly/bagpipe.ly
> diff -u lilypond/ly/bagpipe.ly:1.3 lilypond/ly/bagpipe.ly:1.4
>  % Layout tweaks.
>
> +%{
> +
> +% WTF is this? --hwn
>  \layout {
>    \context {
>      \Voice
> @@ -63,6 +66,8 @@
>      \tieUp
>    }
>  }

Do you mean "WTF doesn't this just use \voiceOne", or "WTF does
bagpipe music have all stems down, slurs up, and ties up" ?

As for the first option, it didn't occur to me until just now.  As for
the
second, Sven knows a lot more about bagpipes than us, and he
clearly thinks that bagpipe music is notated that way.  :)

Cheers,
- Graham



_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: lilypond Documentation/user/examples.itely Docu...

Han-Wen Nienhuys
Graham Percival wrote:

>
> On 19-Aug-05, at 11:18 AM, Han-Wen Nienhuys wrote:
>
>> Index: lilypond/ly/bagpipe.ly
>> diff -u lilypond/ly/bagpipe.ly:1.3 lilypond/ly/bagpipe.ly:1.4
>>  % Layout tweaks.
>>
>> +%{
>> +
>> +% WTF is this? --hwn
>>  \layout {
>>    \context {
>>      \Voice
>> @@ -63,6 +66,8 @@
>>      \tieUp
>>    }
>>  }
>
>
> Do you mean "WTF doesn't this just use \voiceOne", or "WTF does
> bagpipe music have all stems down, slurs up, and ties up" ?
>

no, it means:

WTF is a file that doesn't parse doing in the ly/ directory?

--
  Han-Wen Nienhuys - [hidden email] - http://www.xs4all.nl/~hanwen


_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: lilypond Documentation/user/examples.itely Docu...

Graham Percival-2

On 20-Aug-05, at 3:36 PM, Han-Wen Nienhuys wrote:

> Graham Percival wrote:
>> Do you mean "WTF doesn't this just use \voiceOne", or "WTF does
>> bagpipe music have all stems down, slurs up, and ties up" ?
>
> no, it means:
>
> WTF is a file that doesn't parse doing in the ly/ directory?

Well, WTF can't lily parse it?  I figured it was logical that if
slurUp={ \override Slur #'direction = #1 }
and
\layout{ \context { \Voice
   \override Slur #'direction = #1
}}

work well, then replacing the middle of the \layout{\context{}} with
\slurUp should work.  Evidently it doesn't.  :)

I've fixed it in CVS.
- Graham



_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: lilypond Documentation/user/examples.itely Docu...

Han-Wen Nienhuys
Graham Percival wrote:
>> no, it means:
>>
>> WTF is a file that doesn't parse doing in the ly/ directory?
>
>
> Well, WTF can't lily parse it?  

It has been documented (probably as  BUG); the problem is that

   { \override Foo ... }

is a music expression. You can't put music expressions in \context {
\Voice .. } right now.

One could extend \context redefinitions to override this, by extracting
all \set , \override etc. commands from the music expression, and apply
that to \context. Alternatively, one could create a new syntax

   contextMods =  \contextmod {
      \override ..
      \consists ..
   }

and then define slurUp as a \contextmod

Both options would require some hacking at parser.yy.

--
  Han-Wen Nienhuys - [hidden email] - http://www.xs4all.nl/~hanwen


_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Reply | Threaded
Open this post in threaded view
|

Re: lilypond Documentation/user/examples.itely Docu...

Graham Percival-2

On 21-Aug-05, at 4:31 AM, Han-Wen Nienhuys wrote:

> Graham Percival wrote:
>>> no, it means:
>>>
>>> WTF is a file that doesn't parse doing in the ly/ directory?
>> Well, WTF can't lily parse it?
>
> It has been documented (probably as  BUG); the problem is that
>
>   { \override Foo ... }
>
> is a music expression. You can't put music expressions in \context {
> \Voice .. } right now.

That makes sense.  It hadn't occurred to me (obviously), but it _does_
make
sense that
{ \override Foo }
is an expression, whereas
\override Foo
is not.

- Graham



_______________________________________________
lilypond-devel mailing list
[hidden email]
http://lists.gnu.org/mailman/listinfo/lilypond-devel