The following patches are on countdown until
Tuesday 2012-08-14 20:00 GMT+2.
2729,Patch: When cloning a lexer/parser, don't copy the scopes.
URL:http://code.google.com/p/lilypond/issues/detail?id=2729
2728,count pairs of brackets
URL:http://code.google.com/p/lilypond/issues/detail?id=2728
Not tested, but eyeballing LGTM
http://codereview.appspot.com/6461071/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2012-08-11 21:57, David Kastrup wrote:
Laura Conrad lcon...@laymusic.org writes:
Laura == Laura Conrad lcon...@laymusic.org writes:
Laura When run on the attached file, lilypond-book sets the line
Laura length of the music to be much less than the actual width of
Laura the
Not tested, either, but LGTM from reading the patch.
http://codereview.appspot.com/6461071/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
lgtm
http://codereview.appspot.com/6450113/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reinhold Kainhofer reinh...@kainhofer.com writes:
On 2012-08-11 21:57, David Kastrup wrote:
Fragments may use the
`papersize=STRING'
Where STRING is a paper size defined in `scm/paper.scm' i.e.
`a5', `quarto', `11x17' etc.
Values not defined in `scm/paper.scm' will be
Whoever has watched the repository closely will have noticed that there
is now a branch stable/2.16 corresponding to the last release 2.15.95.
The next release from that branch according to VERSION will be 2.15.96,
but it might also be 2.16.0.
VERSION in staging announces the next release to be
On Sun, Aug 12, 2012 at 02:48:05PM +0200, David Kastrup wrote:
Since it would be awkward (but not impossible) if 2.17.0 would be
released before 2.16.0, any patches now entering in master will not have
seen exposure in a development release before 2.16.0 is tentatively
released.
Actually,
http://codereview.appspot.com/6454139/diff/1/python/book_latex.py
File python/book_latex.py (right):
http://codereview.appspot.com/6454139/diff/1/python/book_latex.py#newcode262
python/book_latex.py:262: textwidth = (textwidth + columnsep) / columns
- columnsep
Why not use the value of
Hi David. OK, maybe word perfect was inappropriate. And yes, I have tried
Gonville. I think that flags look good there (to be honest, for me almost
every non-christmas-tree flag looks better than current LilyPond Flags).
But there is one problem with Gonville - it doesn't support many glyphs that
[lilypond commit 1dedaf12]
Mike,
is the problem `start and end points of slurs and ties don't fall
together' supposed to be fixed? This snippet
\version 2.17.0
\paper {
ragged-right = ##f
}
\relative c' {
\time 5/4 g'2.( ~ g8 a4. ~ |
a1) r4
}
still exhibits a
LGTM, and wow it's amazing that such an improvement in usability can
come from so few lines of code!
http://codereview.appspot.com/6450114/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
LGTM
http://codereview.appspot.com/6450113/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Reviewers: Graham Percival,
Message:
On 2012/08/12 14:32:01, Graham Percival wrote:
LGTM, and wow it's amazing that such an improvement in usability can
come from
so few lines of code!
It is probably even more amazing for how long people put up with the old
behavior.
Description:
Issue
Le dimanche 12 août 2012 à 14:16 +0100, Graham Percival a écrit :
Actually, there's an unforseen problem: the website can only
advertise VERSION_STABLE and VERSION_DEVEL. STABLE is obviously
2.14.2 until 2.16.0 is out. If we want testing for the
pre-releases (which we obviously do), then
On 12 août 2012, at 16:31, Werner LEMBERG w...@gnu.org wrote:
[lilypond commit 1dedaf12]
Mike,
is the problem `start and end points of slurs and ties don't fall
together' supposed to be fixed? This snippet
\version 2.17.0
\paper {
ragged-right = ##f
}
\relative
Odd...I'll look into it.
Thanks!
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
On Sun, Aug 12, 2012 at 09:28:45PM +0200, John Mandereau wrote:
Le dimanche 12 août 2012 à 14:16 +0100, Graham Percival a écrit :
Changing this would require a fair amount of hacking on the
website build process and documentation; not impossible, but not a
fun task either.
Do we want to
Your problem still has the basic problem of most music fonts, which is
that the outermost hook looks larger than the other ones.
Why don't we start this discussion by scanning a bunch of well done engravings?
Also, I think you sent this mail to just me.
On Thu, Aug 9, 2012 at 6:36 PM, Janek
John Mandereau john.mander...@gmail.com writes:
Le dimanche 12 août 2012 à 14:16 +0100, Graham Percival a écrit :
Actually, there's an unforseen problem: the website can only
advertise VERSION_STABLE and VERSION_DEVEL. STABLE is obviously
2.14.2 until 2.16.0 is out. If we want testing for
Le dimanche 12 août 2012 à 21:07 +0100, Graham Percival a écrit :
I don't think so. People can get 2.14 from the old releases if
they want.
Oh right.
I think that automatic patch tests are /far/ more important than
having multiple release versions on the website.
Agreed, it's also more
Le vendredi 10 août 2012 à 13:25 +0200, Reinhold Kainhofer a écrit :
I let a cronjob build origin/master from scratch every night at 01:30 am
CEST (UTC+2) and upload the docs to my server.
So your setup makes a clean build like Patchy, with the difference that
Patchy actually builds staging,
Le dimanche 12 août 2012 à 23:03 +0200, David Kastrup a écrit :
because I'd like to submit fixes for issues 2366 and 2529 and get them
committed in stable/2.16 branch.
2366 (update THANKS) is obviously ok.
Up to source tarball rolling (make dist), in this case it was easy:
Dear all, (especially David and Graham)
Contrary to all indications, I have actually been slowly (very slowly)
chugging away on this, developing on my netbook.
In order to achieve this, we'll need produce a series of patches. The
criterion for accepting the patch for guile V1 systems would, as
On 13 août 2012, at 02:44, Ian Hulin i...@hulin.org.uk wrote:
Dear all, (especially David and Graham)
Contrary to all indications, I have actually been slowly (very slowly)
chugging away on this, developing on my netbook.
In order to achieve this, we'll need produce a series of patches.
25 matches
Mail list logo
