On Wed, Mar 25, 2009 at 07:08:40PM +0100, James E. Bailey wrote:
>
> GIT from git.sv.gnu.org
> git clone git://git.sv.gnu.org/lilypond.git
This does not set up easy pulling or pushing in the future, and
generally assumes that people know how to use git. It also
downloads all branches, which
Joe Neeman wrote:
> [explanation of spacing code...]
> One solution might be the following, which involves modifying only
> accidental-placement: make 2 copies of every accidental, one for the
> start-of-a-line case and one for the middle-of-a-line case (so the
> start-of-a-line accidentals would
On Thu, 2009-03-26 at 10:26 -0400, Chris Snyder wrote:
> Joe Neeman wrote:
> > [explanation of spacing code...]
>
> > One solution might be the following, which involves modifying only
> > accidental-placement: make 2 copies of every accidental, one for the
> > start-of-a-line case and one for the
On Thu, Mar 26, 2009 at 6:06 AM, Graham Percival
wrote:
> On Wed, Mar 25, 2009 at 07:08:40PM +0100, James E. Bailey wrote:
>>
>> GIT from git.sv.gnu.org
>> git clone git://git.sv.gnu.org/lilypond.git
>
> This does not set up easy pulling or pushing in the future, and
> generally assumes that p
Hello,
The first patch fixes a newly added link on the download page, and the
second adds LilyPond 2.13 to the list on the documentation page.
Thanks,
Patrick
>From c7f3bec4129e4cc132dd6a534028d94c10b2a68e Mon Sep 17 00:00:00 2001
From: Patrick McCarty
Date: Thu, 26 Mar 2009 14:44:55 -0700
Subj
Nicolas Sceaux free.fr> writes:
> you can try that:
>
> -foo.ly-
> #(module-define! (resolve-module '(guile-user)) 'lilypond-module
> (current-module))
> #(top-repl)
>
>
> guile> (set-current-module lilypond-module)
> #
> guile> parser
> #) > >
> guile> (display-schem
