Look, we simply *cannot* offer users anything that would be
reasonable by most standards. We have highly embarrassing bugs
from 2006 that we're not even *pretending* to be working on. We've
been in release crunch mode for at least six months. The only
glimmer of hope on the horizon is
What we would need is a payed full-time developer.
I have forgotten to say that such a developer needs certain skills in
addition to C++ and Scheme, namely being a musician...
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
I'm not optimistic about that; I think a more realistic opportunity
would be to get some grant money from some artistic organization.
Mhmm. `Programming' in its broadest sense is research, thus getting
grants limits the number of persons enormously. However, the number
of music researchers
Graham Percival wrote Saturday, January 01, 2011 7:16 AM
Nope, for precisely the reason you gave earlier: our documentation
generally has zero input from programmers, so it's not at all a
good representation of what's intended.
We have a set of intended to be working examples. They're
2011/1/1 Werner LEMBERG w...@gnu.org:
What we would need is a payed full-time developer. However, this is
expensive. Assuming that the programmer has a family with children,
an appartment, etc., and to provide a reasonably good living for him
or her, this would be about 3000 Euros a month
On Sat, Jan 01, 2011 at 09:39:37AM +0100, Werner LEMBERG wrote:
I'm not optimistic about that; I think a more realistic opportunity
would be to get some grant money from some artistic organization.
Mhmm. `Programming' in its broadest sense is research, thus getting
grants limits the
Keith OHara k-ohara5...@oco.net writes:
On Fri, 31 Dec 2010 16:31:23 -0800, Trevor Daniels
t.dani...@treda.co.uk wrote:
... the concern I had was this. Quite a lot of the
documentation was written, not by inspecting the code
to see what was intended, but by experimenting and
writing up
Hello all!
First is first: thanks for a great piece of software.
This is a long standing feature request for me which you probably got from
hundreds of other users but I sent it anyway since I see it as a major pain.
When I run lilypond it is too noisy. It prints out lots of stuff (version,
Graham Percival gra...@percival-music.ca writes:
In my idle moments, I like to discourage myself by trying to
figure out how long it would take to achieve something
reasonable for users. Let's play this game now, and start
making some unrealistic-but-just-possible assumptions:
1. reasonable
On Sat, Jan 01, 2011 at 09:49:10AM +, Mark Veltzer wrote:
- version, progress and general messages which are not error messages should
go
to stdout and NOT stderr.
Good point; I've added this as
http://code.google.com/p/lilypond/issues/detail?id=1468
- a --quiet flag should be added to
Mark Veltzer mark.velt...@gmail.com writes:
First is first: thanks for a great piece of software.
This is a long standing feature request for me which you probably got from
hundreds of other users but I sent it anyway since I see it as a major pain.
When I run lilypond it is too noisy. It
Graham:
On Sat, Jan 01, 2011 at 09:10:49AM +0100, Werner LEMBERG wrote:
...
But maybe there is a group of LilyPond philanthropists who can afford
this and are willing to do so...
I'm not optimistic about that; I think a more realistic
opportunity would be to get some grant money from some
- Original Message -
From: Jonathan Kulp jonlancek...@gmail.com
To: Graham Percival gra...@percival-music.ca
Cc: James Lowe james.l...@datacore.com; lilypond-devel@gnu.org
Sent: Saturday, January 01, 2011 1:33 AM
Subject: Re: default .ly file in Windows Install seems to be
On Fri, Dec
Hello all,
This is in response to David Kastrup.
- startup and shutdown messages. These are not usually omitted to stderr, or at
least 99.99% of the tools out there do not do it. Most tools actually *have no*
startup and shutdown messages. If you have other info then I'd appreciate a list
of
Hi,
On Sat, 1 Jan 2011 10:19:18 +
Graham Percival gra...@percival-music.ca wrote:
On Sat, Jan 01, 2011 at 09:49:10AM +, Mark Veltzer wrote:
- version, progress and general messages which are not error
messages should go to stdout and NOT stderr.
Good point; I've added this as
Mark Veltzer mark.velt...@gmail.com writes:
- stderr is called stderr and not stddiag since it is intended for errors. I
agree that stdout is intended for further processing but lilypond *does not*
create any further data for further processing so stdout could be used for
version and other
On 31 December 2010 23:53, Graham Percival gra...@percival-music.ca wrote:
On Thu, Dec 30, 2010 at 05:35:43PM +0100, Sven Axelsson wrote:
Perhaps a starting point would be if someone could have a look at what
I'm doing in https://github.com/svenax/bagpipemusic/. The relevant
file is
On Sat, Jan 01, 2011 at 06:51:49AM +, Graham Percival wrote:
The next step in issue 1464 is just to create a backtrace.
See the blurb below this mail (no, I'm not going to sign up at google
for adding it there).
I don't know why gdb doesn't find paper-column.hh, but anyaway...
it looks
hi Joe,
do you think my patch is a good start?
Yes, but you need to be careful about what happens when bar-size is set.
Currently, your patch will break (for example) input/regression/drums.ly
because it ignores bar-size.
well, I admit I haven't run regtests, but I did now and (having found
On Sat, Jan 01, 2011 at 02:10:04PM +0100, Matthias Kilian wrote:
I don't know why gdb doesn't find paper-column.hh, but anyaway...
it looks like Item::get_column() returns NULL, because its parent's
get_column() returns NULL (I checked that the parent on the X_AXIS
itself is not NULL).
looks mostly ok, but I don't know what's up with those beaming rules.
http://codereview.appspot.com/3825043/diff/1/ly/bagpipe.ly
File ly/bagpipe.ly (right):
http://codereview.appspot.com/3825043/diff/1/ly/bagpipe.ly#newcode72
ly/bagpipe.ly:72: #(override-auto-beam-setting '(end * * * *) 1 2
On 2010-12-27, at 15:14 , Dan Eble wrote:
Here's some prototype code which works for me in 2.13.9.
Correction: 2.13.18.
--
Dan
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Reviewers: ,
Message:
Fixes a segfault, passes the regtest comparison, code by Matthias
Kilian.
Description:
Fix 1464 (segfault with R1 and metronome)
This code came from Mathias Kilian.
Please review this at http://codereview.appspot.com/3858041/
Affected files:
A
I have a patch for Issue 1290 that fixes the improper spacing.
I am currently doing a regression test.
Thanks,
Carl
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Sat, Jan 01, 2011 at 12:21:24PM +0100, m...@apollinemike.com wrote:
I have a flight on January 4th from London to New York. I would be happy to
devote the entire flight to solving two issues, but I do not want to
duplicate the work of someone else.
These are the current Critical
On Sun, Jan 2, 2011 at 2:14 AM, Matthias Kilian k...@outback.escape.dewrote:
On Sat, Jan 01, 2011 at 02:10:04PM +0100, Matthias Kilian wrote:
I don't know why gdb doesn't find paper-column.hh, but anyaway...
it looks like Item::get_column() returns NULL, because its parent's
get_column()
On Sat, Jan 01, 2011 at 02:25:57AM -0500, David Santamauro wrote:
On Sat, 1 Jan 2011 10:19:18 +
Graham Percival gra...@percival-music.ca wrote:
http://code.google.com/p/lilypond/issues/detail?id=1074
Patches appreciated. Unfortunately I doubt that anything will
happen unless you
On Fri, Dec 31, 2010 at 03:38:47PM +, James Lowe wrote:
In CG 5.4.3 Checking Cross References there is a para that refers to
Thanks, added as
http://code.google.com/p/lilypond/issues/detail?id=1469
Cheers,
- Graham
___
lilypond-devel mailing list
On Sat, Jan 01, 2011 at 01:06:04PM +0100, Karl Hammar wrote:
Graham:
Of course, writing artistic and research grants is a non-trivial
amount of work, and it's hardly guaranteed to have any results.
But I think that with the right angle -- be that collaborative
folk music archival, or
Reviewers: ,
Message:
Here is a patch to fix issue 1290.
It works, but it may need to be cleaned up. I'm not sure the code is as
elegant as it could be. I'm not really comfortable with all of the C++
syntax used in lilypond.
Please review it carefully, and let me know how it can be improved.
I don't know if it's important, but it may be worth mentioning somewhere
that skyline-horizontal-padding works differently for VerticalAxisGroup
and System. (Because in VerticalAxisGroup, skyline-horizontal-padding
takes effect while the outside-staff-grobs are being placed).
31 matches
Mail list logo
