Carl
Before I saw this email from you I had tucked away
the note from -user to include it in the Scheme
tutorial in the Learning Manual. This is where it
and other trivial uses of Scheme belong, I think.
Then, with a few of these easier examples behind
them, users will be able to tackle the
Op woensdag 31-12-2008 om 15:43 uur [tijdzone +0100], schreef Jan Nieuwenhuizen:
IWBN to do this ABI=32 think automagically (and from bin/gub or
gub/settings.py or gub/linux.py or something.)
I've added a check to gub/settings.py; this may work nor or it
may be necessary to add ABI=32 to
On 1/13/09 2:29 AM, Trevor Daniels t.dani...@treda.co.uk wrote:
Carl
Before I saw this email from you I had tucked away
the note from -user to include it in the Scheme
tutorial in the Learning Manual. This is where it
and other trivial uses of Scheme belong, I think.
Then, with a few
On Tue, Jan 13, 2009 at 02:06:14AM +0100, John Mandereau wrote:
Carl D. Sorensen a écrit :
Graham and Trevor,
This mail below, from -user, shows why I think NR 5 and NR 6 should be
combined into one chapter, something like Extending LilyPond.
I don't mind renaming NR 6, but they should stay
On 1/10/09 7:44 PM, Patrick McCarty pnor...@gmail.com wrote:
Hello,
This patch reworks def-grace-function so that it inserts the
docstring, if defined, into the template for define-music-function.
If the docstring is not defined, the unquote-splicing strips the empty
list from the
On 1/11/09 2:50 AM, Neil Puttock n.putt...@gmail.com wrote:
Hi Patrick,
2009/1/11 Patrick McCarty pnor...@gmail.com:
Hello,
This patch reworks def-grace-function so that it inserts the
docstring, if defined, into the template for define-music-function.
If the docstring is not
When I make changes to ly/music-functions-init.ly (which will affect
Appendix B.14 of the Notation Reference), then run
make web
from Documentation/user, make produces the following output:
sorensen2:user Carl$ make web
make --no-builtin-rules -C ../../scripts/build out=
true
make
Carl D. Sorensen a écrit :
When I make changes to ly/music-functions-init.ly (which will affect
Appendix B.14 of the Notation Reference), then run
the documentation is not updated to reflect the changes in
ly/music-functions-init.ly.
Should I post this to bug?
No, issues with makefiles
On 1/13/09 10:38 AM, John Mandereau john.mander...@gmail.com wrote:
Carl D. Sorensen a écrit :
When I make changes to ly/music-functions-init.ly (which will affect
Appendix B.14 of the Notation Reference), then run
the documentation is not updated to reflect the changes in
Someone can correct me if I'm wrong, but I think you'll need to build
lilypond from source. You'll want to have a look in the program usage
about building lilypond from source, and then there is a thread in
the developers list on using the binary wrapper once you have the
program built. I
Hallo all,
James E. Bailey schreef / wrote / skribis:
Someone can correct me if I'm wrong, but I think you'll need to build
lilypond from source.
There's no need to do that to use LP on Mac OS X Leopard.
http://ivo.bouwmans.name/lilypondleopard/ describes several methods to use
the compiled
Am 13.01.2009 um 20:43 schrieb Ivo Bouwmans:
Hallo all,
James E. Bailey schreef / wrote / skribis:
Someone can correct me if I'm wrong, but I think you'll need to
build lilypond from source.
There's no need to do that to use LP on Mac OS X Leopard.
Ah, but he wants to, apparently.
Am
In message 496bcb51.3030...@ee.kth.se, Mats Bengtsson
mats.bengts...@ee.kth.se writes
I would soften the formulation a bit, for example replacing
When ... into a variable, wrap ... by
When ... into a variable, it is recommended to wrap ...
Fine, that's okay :-)
After all, this is just a
Anthony W. Youngman wrote:
I
To my mind, always convert via C means I don't get confused as to
which pitch a piece of music is in. (And as I said, it makes it easy
to print a score in concert). It's just a case of being consistent,
and if you re-use the music you don't have to ask yourself
Hi Anne,
I'd suggest you start by joining the Frogs [1]. As a Frog, you will get
some get some help in exploring lilypond's internals for the first time.
You could also have a look at the bug tracker [2] if you want ideas for
a project. Have a look, in particular, at the bugs with priority Low
or
15 matches
Mail list logo
