[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Point-and-Click URIs not properly formed (see text at end of message
From: |
Patrick McCarty |
Subject: |
Re: Point-and-Click URIs not properly formed (see text at end of message) |
Date: |
Fri, 19 Nov 2010 12:37:14 -0800 |
On Fri, Nov 19, 2010 at 8:56 AM, Mike Bagneski <address@hidden> wrote:
> I should explain that the .ly files that cause this are exported from
> Tuxguitar, so my understanding of lilypond code is limited. Here's a much
> smaller example that returns the busted URIs:
>
> TrackAVoiceAMusic = #(define-music-function (parser location inTab)
> (boolean?)
> #{
> \tempo 4=120
> \clef #(if $inTab "tab" "treble_8")
> \key c \major
> \time 4/4
> \oneVoice
> r1
> \bar "|."
> \pageBreak
> #})
> TrackAStaff = \new Staff <<
> \context Voice = "TrackAVoiceAMusic" {
> \TrackAVoiceAMusic ##f
> }
>>>
> TrackATabStaff = \new TabStaff \with { stringTunings = #'( 4 -1 -5 -10 -15
> -20 ) } <<
> \context TabVoice = "TrackAVoiceAMusic" {
> \TrackAVoiceAMusic ##t
> }
>>>
> TrackAStaffGroup = \new StaffGroup <<
> \TrackATabStaff
>>>
> \score {
> \TrackAStaffGroup
> }
>
> Hope I'm doing this right. Thanks!
Thanks, Mike.
This _is_ related to the use of music functions, in particular, with
the use of embedded LilyPond expressions within music functions.
I still see "<string>" in the URIs when the expression is very
minimal, so I'll open a tracker issue.
http://code.google.com/p/lilypond/issues/detail?id=1416
Thanks,
Patrick