In the large "DOC: Makefile" thread that nobody new is going to
read, there was a proposal to use .ily to indicate "setup"
lilypond files.
I quite like this suggestion, so I'm asking somebody to take the
next step: integrate this with lilypond.
- change (almost) everything in ly/ to .ily.
- updat
On Fri, May 15, 2009 at 01:56:35PM +, Kieren MacMillan wrote:
> I figured I'd do it in two steps:
> 1. Create a function that takes a chord of three notes, and formats each
> note(head) appropriately.
> 2. Modify the function to take one or two notes, and generate the other parts
> of
> the no
Patrick McCarty wrote:
On Fri, May 15, 2009 at 02:39:26PM -0500, Jonathan Kulp wrote:
Here's a patch to add the .ily extension to the filetype.vim file in the
sources and to the Application Usage 2.2.2 "Vim mode" sample filetype.vim.
You should also add the *.ily to vim/lilypond-ftdetect.vim,
> "John" == John Mandereau writes:
John> pe...@chubb.wattle.id.au a écrit :
>> If you use GNU extensions, then here's the Makefile I generally
>> use, to convert everything in the current directory.
>>
John> Your makefile is certainly useful for many pruposes, but it
John> doesn't take inclu
2009/5/15 Kieren MacMillan :
> Hi Neil,
>
> Thanks for the help.
>
>> Tricky without another voice, since there's only one stem for all the
>> noteheads. You can change the length of a stem by overriding 'length,
>> but you'd need to be careful about stem direction because negative
>> values will b
Hi Neil,
Thanks for the help.
> Tricky without another voice, since there's only one stem for all the
> noteheads. You can change the length of a stem by overriding 'length,
> but you'd need to be careful about stem direction because negative
> values will be required, and you won't be able to
2009/5/15 Kieren MacMillan :
> I'm trying to come up with a Scheme function to generate string harmonics
> automatically.
Why on earth would you want to do that. ;)
You might like to take a look at Valentin's function here (though it
uses separate voices):
http://repo.or.cz/w/opera_libre.git?a=
On Fri, May 15, 2009 at 02:39:26PM -0500, Jonathan Kulp wrote:
> Here's a patch to add the .ily extension to the filetype.vim file in the
> sources and to the Application Usage 2.2.2 "Vim mode" sample filetype.vim.
You should also add the *.ily to vim/lilypond-ftdetect.vim, because
vim/filetype.vi
Here's a patch to add the .ily extension to the filetype.vim file in the
sources and to the Application Usage 2.2.2 "Vim mode" sample filetype.vim.
Jon
--
Jonathan Kulp
http://www.jonathankulp.com
From 2c173c2b6cacb37a7243585fb73ae81168aa40e8 Mon Sep 17 00:00:00 2001
From: Jonathan Kulp
Date: F
On Fri, May 15, 2009 at 12:42:41PM -0500, Jonathan Kulp wrote:
> Anthony W. Youngman wrote:
>> In message <4a0d4529.9080...@gmail.com>, John Mandereau
>> writes
>>> pe...@chubb.wattle.id.au a écrit :
If you use GNU extensions, then here's the Makefile I generally use,
to convert everyt
Anthony W. Youngman wrote:
In message <4a0d4529.9080...@gmail.com>, John Mandereau
writes
pe...@chubb.wattle.id.au a écrit :
If you use GNU extensions, then here's the Makefile I generally use,
to convert everything in the current directory.
Your makefile is certainly useful for many pruposes
> I changed the ` backticks to the $() construct on recommendations
> from one of my scripting books, which alleges that backticks are
> old-fashioned.
BTW, you might read the `autoconf' documentation which has a few,
quite long chapters on writing portable make and shell scripts.
http://www.g
Anthony W. Youngman wrote:
parts:
for LILYFILE in Parts/*.ly ; do $(LILY_CMD) "$$LILYFILE" ; done
mv *.pdf $(OUTDIR)/
It works exactly as it did with the GNU wildcard, except that multiple files
can't be compiled at once with separate processors. I'll probably stick
with the GNU wi
> My bash-fu is minimal to non-existent, but couldn't you do something
> like
>
> for LILYFILE in Parts/*.ly ; do $(LILY_CMD) "$$LILYFILE" & ; done
> wait
> mv *.pdf $(OUTDIR)/
>
> ?
>
> I'm sure there's a command, and I think it is "wait", that says to
> wait and collect status from all
In message <4a0d8c1f.8020...@gmail.com>, Jonathan Kulp
writes
>Werner LEMBERG wrote:
>>> parts:
>>> $(LILY_CMD) $(wildcard Parts/*.ly)
>>> mv *.pdf $(OUTDIR)/
>> `wildcard' is a GNU extension. It can be circumvented with shell
>> commands, however, I suggest to name the part files explic
In message <4a0d4529.9080...@gmail.com>, John Mandereau
writes
pe...@chubb.wattle.id.au a écrit :
If you use GNU extensions, then here's the Makefile I generally use,
to convert everything in the current directory.
Your makefile is certainly useful for many pruposes, but it doesn't
take inclu
> Pity. In that case, the original approach is best for portability I
> suppose. Here's how I have the "parts" target now:
>
> parts:
> for LILYFILE in Parts/*.ly ; do $(LILY_CMD) "$$LILYFILE" ; done
> mv *.pdf $(OUTDIR)/
>
> It works exactly as it did with the GNU wildcard, except
John Mandereau wrote:
I'm attaching one of my makefiles, which is not perfect, either, but
it works very well for my scores.
It's a good example of a makefile adapted to a particular purpose... I'm
not sure which
criterions we should use to adopt makefiles in the docs, besides having
a gen
Reinhold Kainhofer a écrit :
Shouldn't this be rather done with prerequisites, variable substitutions and
some generic rules?
This is exactly what I wrote, isn't it?
movement_pdf_target is a phony target rule template, which I apply
to the list of movements MOVEMENTS, and I defined a generic
Werner LEMBERG wrote:
parts:
$(LILY_CMD) $(wildcard Parts/*.ly)
mv *.pdf $(OUTDIR)/
`wildcard' is a GNU extension. It can be circumvented with shell
commands, however, I suggest to name the part files explicitly.
Pity. In that case, the original approach is best for portabil
> parts:
> $(LILY_CMD) $(wildcard Parts/*.ly)
> mv *.pdf $(OUTDIR)/
`wildcard' is a GNU extension. It can be circumvented with shell
commands, however, I suggest to name the part files explicitly.
>> $(OUTDIR)/%.pdf: Scores/%.ly
Percent rules are a GNU extension.
>> define movemen
On Thu, May 14, 2009 at 03:51:29PM +, Tim Wilkinson wrote:
> I am very interested in becoming a `Code Janitor', as described on the
> call-for-help web page on the lilypond site.
Great! If you haven't already, please read the Contributor's
Guide for tips on getting started with lilypond devel
John Mandereau wrote:
MASTER_FILE might be clearer
Ok I've changed this.
Shell loops can often be replaced with source wildcards and pattern
rules, which takes advantage of several make implementations (including
GNU), especially concurrency: with the increasing number of multi-core
CPUs p
> Top posting is often superior to bottom-posting.
[Sorry... the web email interface I'm forced to use while my MacBook is in for
repairs clearly messed up the last post, so I'm forced to used gmane. =\]
Hello, all!
I'm trying to come up with a Scheme function to generate string harmonics
autom
Hello, all!
I'm trying to come up with a Scheme function to generate string harmonics
automatically.
I figured I'd do it in two steps:
1. Create a function that takes a chord of three notes, and formats each
note(head) appropriately.
2. Modify the function to take one or two notes, and
Am Freitag, 15. Mai 2009 12:55:08 schrieb John Mandereau:
> MOVEMENTS=I II III IV
>
> # define targets mvI ... mvIV
>
> # maybe need to be surrounded by $(eval ...)
>
> $(foreach m, MOVEMENTS, $(call movement_pdf_target,$(m))
>
> parts: $(foreach m, MOVEMENTS, mv$(m))
Shouldn't this be rather don
> "Jonathan" == Jonathan Kulp writes:
Jonathan> John Mandereau wrote:
>> Jonathan Kulp a écrit :
>>> I would welcome "best practice" advice on these. Once I'm
>>> satisfied with how they work on Linux & Mac (and Windows if anyone
>>> wants to help me with them), then I'll put generic filename
Hi,
I am very interested in becoming a `Code Janitor', as described on the
call-for-help web page on the lilypond site. I have C++ experience gained
mainly through my degree (mechanical engineering with computing BEng) and
through a few personal projects since, and although I do not have pytho
Jonathan Kulp a écrit :
Thanks for looking at this, John. I've gone through the two makefiles
and updated according to your advice, and have also made changes based
on recommendations in the GNU Make Manual, such as specifying the
shell and defining unusual utilities in variables (viewer as
"a
pe...@chubb.wattle.id.au a écrit :
If you use GNU extensions, then here's the Makefile I generally use,
to convert everything in the current directory.
Your makefile is certainly useful for many pruposes, but it doesn't take
included files into account:
it will try to build those who have a .
30 matches
Mail list logo
