[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Fret Diagram markup
From: |
Carl D. Sorensen |
Subject: |
RE: Fret Diagram markup |
Date: |
Mon, 17 May 2004 17:03:55 -0600 |
> -----Original Message-----
> From: Heikki Johannes Junes [mailto:address@hidden
> Sent: Monday, May 17, 2004 1:46 PM
> To: Carl D. Sorensen
> Cc: address@hidden
> Subject: Re: Fret Diagram markup
>
>
>
> > It's a fairly lengthy chunk of code to include at the front of a
> > lilypond file. I think it might be reasonable to add as a
> scheme file
> > to the lilypond distribution, and create a new kind of
> standard markup,
> > fret-diagram-markup, rather than using a user-defined
> markup. I don't
> > have CVS access (and in fact, haven't yet been able to get
> lilypond to
> > build on my Cygwin installation), so I don't believe I'm the right
> > person to move this into the lilypond distribution. But if
> I should
> > become that person, I'll try to accept that responsibility.
>
> Actually its fairly simple: just put the initialization
> script into a separate file called
> "fret-diagram-init.ly". This file will be then put to "ly/"
> directory. Then one can use the script you
> wrote by adding just one line in the beginning of the file:
>
> \include "fret-diagram-init.ly"
>
> By adding this line into "ly/declarations-init.ly", one may
> use the scripts even without any extra
> lines.
I agree that this can be done, but it seems "improper" to me to include
as a .ly file a whole chunk of nothing but scheme code. To me, it would
be better to get rid of the # in front of each #(define... and save the
file as fret-diagram-markup.scm, then modify the (use-module ...
statements wherever it is necessary. But I can see that it would work
as a .ly include.
>
> Back to debugging, I tried to compile the attached file, but got:
>
> ...
> 222: 27* (fontify-text font (if (> basefret 1)
> (integer->roman basefret) " "))
>
> /home/hjunes/fret-diagrams.ly:222:36: In expression
> (fontify-text font (if # # ...)):
> /home/hjunes/fret-diagrams.ly:222:36: Unbound variable: fontify-text
>
> I also tried "grep -R fontify-text *" to the
> lilypond-source, but there was no hits.
> Where does the fontify-text function originate from? I should
> have missed something.
In my distribution, fontify-text is found in scm/stencil.scm
Thanks for your review,
Carl
- Fret Diagram markup, Carl D. Sorensen, 2004/05/17
- Re: Fret Diagram markup, Heikki Johannes Junes, 2004/05/17
- RE: Fret Diagram markup,
Carl D. Sorensen <=
- RE: Fret Diagram markup, Carl D. Sorensen, 2004/05/17
- RE: Fret Diagram markup, Carl D. Sorensen, 2004/05/17
- RE: Fret Diagram markup, Heikki Johannes Junes, 2004/05/17
- RE: Fret Diagram markup, Carl D. Sorensen, 2004/05/17
- RE: Fret Diagram markup, Carl D. Sorensen, 2004/05/18
- RE: Fret Diagram markup, Carl D. Sorensen, 2004/05/18