"Robin Davies" <[EMAIL PROTECTED]> writes:
> I'm ramping up for a major assault on chord-name.scm in an attempt to get to
> work properly across the board. Fascinating problem. fyi, the general
> approach I'm intending to take is:
Your approach looks well informed, I'm very much looking forward
On Fri, 17 May 2002, Han-Wen wrote:
> > > looks as if you have old lilypond stuff lying around in
> > > /usr/local/share. Can you try removing that ?
> >
> > Did it and retried - I got the same errors.
>
> weird. You removed *everthing*? (including /usr/local/share/scm? )
Well, considering I ha
[EMAIL PROTECTED] writes:
>
> I have found that more and more I have to go to the web page for online
> information which uncovenient when I am home and do not have an open
> Internet connection all the time, or when one prefers to work still with a
> printer reference document.
That is quaint.
"Carlos Garcia Suarez" <[EMAIL PROTECTED]> writes:
> I am not sure what the issue is, but let me say that I have used the
> lilypond manual quite extensively
That's exactly what I think that the issue is:
> ... the effort to re-vamp the manual could be extensive for
> people working for free, m
I am not sure what the issue is, but let me say that I have used the
lilypond manual quite extensively both the tutorial and the index to look
for things.
It provides a good first approach, but it creates a bit of frustation when
you start to discover that they are many things / options that are
[EMAIL PROTECTED] writes:
>
> On Thu, 16 May 2002, Han-Wen wrote:
>
> > > The output of lilypond -V generate_document.ly ends with:
> > > ---
> > > Now processing: `../../ly/generate-documentation.ly'
> > > Parsing...[/usr/local/share/lilypond/ly/init.ly[/usr/local/share/lilypond/
>
[EMAIL PROTECTED] writes:
>
> Ah. Got it.
>
> Yes, I read through the tutorial, but did not "work through" it- I read it
> and afterwards used it for reference rather than trying to create my own
> versions of each example concept.
Another question: did you use the index of the manual for lo
On Thu, 16 May 2002, Han-Wen wrote:
> > The output of lilypond -V generate_document.ly ends with:
> > ---
> > Now processing: `../../ly/generate-documentation.ly'
> > Parsing...[/usr/local/share/lilypond/ly/init.ly[/usr/local/share/lilypond/
> > ly/declarations-init.ly[/usr/local
