On 20/07/13 23:54, Ian Hulin wrote:
> On 20/07/13 22:25, Julien Rioux wrote:
>> On 20/07/2013 5:00 PM, Ian Hulin wrote:
>>> On 13/07/13 20:51, Frédéric Bron wrote:
>>
>> I got started already, see
>> http://code.google.com/p/lilypond/issues/detail?id=3461. I don't
>> think that we need a guile-1
On 20/07/13 22:25, Julien Rioux wrote:
> On 20/07/2013 5:00 PM, Ian Hulin wrote:
>> On 13/07/13 20:51, Frédéric Bron wrote:
I don't think ./configure should do this automatically, but
at the very least, it should fail when it finds a guile
version that is incompatible with our source
Thanks for replies to the last enquiry, David, I'll try and be a little
more coherent in this one (despite the 30C tempertures here in the UK).
You asked in your reply in the last thread:
"The question is whether it even makes sense trying to go through \midi
or whether one should actually use the
> Could you make the Guile-1 compatibility a separate issue from 3382,
> which is about tex-info versions?
Oh, sorry that you missed that but Julien fixed this already:
http://code.google.com/p/lilypond/issues/detail?id=3461
Frédéric
___
lilypond-devel
On 20/07/2013 5:00 PM, Ian Hulin wrote:
On 13/07/13 20:51, Frédéric Bron wrote:
I don't think ./configure should do this automatically, but at
the very least, it should fail when it finds a guile version that
is incompatible with our source code. Can you please open an
issue for it\?
good poin
On 13/07/13 20:51, Frédéric Bron wrote:
>> I don't think ./configure should do this automatically, but at
>> the very least, it should fail when it finds a guile version that
>> is incompatible with our source code. Can you please open an
>> issue for it\?
>
> good point, I will do that. Frédéric
This is good news Janek. One project that might be appropriate is working on
integrating the improvements to musicxml2ly that the Philomelos team have
made on their own fork, but haven't had time to contribute back upstream.
That seems like low-hanging fruit that should be picked.
As David K men
hi David,
> The probability that some envelope-finding code dropped into LilyPond
> by a typical LilyPond contributor is close to the quality of somebody
> who wrote a Phd thesis focused around the topic is slim.
I did write a Phd thesis not very far from that. the time I can spend
on LilyPond
Janek Warchoł writes:
> Now, there's an even more awesome thing: i've talked with another guy
> who coordinates the "team programming project" course for 3rd-year
> students (which results in undergraduate thesis for the team members).
> The thing is that the coordinator wants the projects to be
