I've not tried following it, but it looks clear enough to me.
http://codereview.appspot.com/3823045/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On 2011/01/01 00:47:54, Graham Percival wrote:
Please review.
LGTM, apart a nitpick: I prefer to create build directory outside git
tree, i.e. if foo/lily is my git repo, I build in foo/build, to avoid
build/ appear to git as an untracked file.
http://codereview.appspot.com/3823045/
Hi, I'm quite new to Lilypond programming, but I thought I'd jump in at what
seemed to me to be pretty much the deep end, and try if I could get black
mensural notation implemented. Here's what I've come up with so far:
http://lukas-pietsch.de/Music/blackmensural.ly (source file)
2011/1/4 James Bailey derhindem...@googlemail.com:
Compiling this (...)
I see no attachment nor any code in e-mail.
Janek
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Tue, Jan 04, 2011 at 09:58:46AM +, john.mander...@gmail.com wrote:
LGTM, apart a nitpick: I prefer to create build directory outside git
tree, i.e. if foo/lily is my git repo, I build in foo/build, to avoid
build/ appear to git as an untracked file.
Check .gitignore. :)
I personally
Il giorno mar, 04/01/2011 alle 10.35 +, Graham Percival ha scritto:
On Tue, Jan 04, 2011 at 09:58:46AM +, john.mander...@gmail.com wrote:
LGTM, apart a nitpick: I prefer to create build directory outside git
tree, i.e. if foo/lily is my git repo, I build in foo/build, to avoid
Hi, I'm quite new to Lilypond programming, but I thought I'd jump in
at what seemed to me to be pretty much the deep end, and try if I
could get black mensural notation implemented. Here's what I've
come up with so far: http://lukas-pietsch.de/Music/blackmensural.ly
(source file)
On Mon, Jan 03, 2011 at 01:14:19PM -, Phil Holmes wrote:
version, but this looks fine. My intention was that, even if it
was a minor bug, then someone had put work in recently to fix it.
If someone else has just unpicked that, then this a Bad Thing and
should be corrected.
I don't want
Lukas:
Hi, I'm quite new to Lilypond programming, but I thought I'd jump in at what
seemed to me to be pretty much the deep end, and try if I could get black
mensural notation implemented. Here's what I've come up with so far:
http://lukas-pietsch.de/Music/blackmensural.ly (source file)
hi Lukas,
Hi, I'm quite new to Lilypond programming, but I thought I'd jump in at what
seemed to me to be pretty much the deep end, and try if I could get black
mensural notation implemented. Here's what I've come up with so far:
http://lukas-pietsch.de/Music/blackmensural.ly (source file)
Hello,
From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
[lilypond-devel-bounces+james.lowe=datacore@gnu.org] on behalf of Phil
Holmes [m...@philholmes.net]
Sent: 01 January 2011 12:10
To: Jonathan Kulp; Graham Percival
Cc: James Lowe;
The current output looks ok to me. You can recover the 2.12 output by
increasing the page-spacing-weight parameter, but I think the current output
still captures the point of the test.
Horizontally stretched means that the ideal horizontal spacing would be to
use 1 system per page, but lilypond
Am Dienstag, 4. Januar 2011, um 12:55:25 schrieb Benkő Pál:
I'll read your docs carefully (my first impression is: it's
absolutely stunning), but in the meantime I want to let you
know that I'm working on white mensural notation, and I've implemented
a preliminary version of coloratio (i.e.
Karl Hammar karl at aspodata.se writes:
On line 22 in the ly-file:
%% Accidentals are valid only once (same as
Shouldn't the accidental be valid for the next note and any same
repeted note, this has bothered me with the current white mesural
support. E.g. if you say bes bes bes,
Here's a patch that allows markup lines to be assigned to a variable:
http://codereview.appspot.com/3855043
So far, the following was invalid syntax:
mytext = \markuplines {
\justified-lines { Lorem ipsum dolor sit amet, ... } }
\markuplines \mytext
Okay to push?
Cheers,
Reinhold
--
Reinhold Kainhofer reinh...@kainhofer.com writes:
Here's a patch that allows markup lines to be assigned to a variable:
http://codereview.appspot.com/3855043
So far, the following was invalid syntax:
mytext = \markuplines {
\justified-lines { Lorem ipsum dolor sit amet, ... } }
Am Dienstag, 4. Januar 2011, um 15:22:38 schrieb David Kastrup:
Reinhold Kainhofer reinh...@kainhofer.com writes:
Here's a patch that allows markup lines to be assigned to a variable:
http://codereview.appspot.com/3855043
So far, the following was invalid syntax:
mytext =
On Tue, 2011-01-04 at 11:49 +0100, Werner LEMBERG wrote:
Very impressive! Could you try to make it work with the current
development version? The next steps could then be adding the missing
glyph shapes to the lilypond fonts, followed by either writing a new
engraver or
I'm currently trying to design a nice title page (as a separate bookpart using
vertical stretching). It consists of several \markup objects inside a
bookpart. To force some spacing, I've inserted several
To allow vertical stretching, I'm using
\paper {
markup-markup-spacing
Thanks, Keith for identifying the problem with bar numbers at the
beginning of the line.
I've fixed that problem, and I'm more confident in the logic of the box
extraction and padded skyline creation.
I've modified the regression test so it has 3 systems, and thus would
catch the problem that
Phil Holmes mail at philholmes.net writes:
\remove Hara_kiri_engraver
\consists Hara_kiri_engraver
I know I don't properly understand this stuff still, but doesn't the
\consists re-instate the previously removed engraver on the line above?
You are correct.
I looked at the history of
I've been creating a patch for the CG and wanted to test it. Early this
afternoon, I edited issues.itexi and compiled it locally, and the changes
were what I'd created. However, I'd missed a minor edit, so I updated it
and tried the make doc again. The change wasn't reflected in the local
On 1/4/11 2:06 PM, Phil Holmes m...@philholmes.net wrote:
I've been creating a patch for the CG and wanted to test it. Early this
afternoon, I edited issues.itexi and compiled it locally, and the changes
were what I'd created. However, I'd missed a minor edit, so I updated it
and tried the
Reviewers: Neil Puttock, joeneeman,
Message:
I wrote a conversion, inspired by Neil, a month ago, but have been
unable to make the regex match the variety of expressions that could
have set the old-style variable,
while behaving correctly in the case of a single-line-commented-out
variable
I tried to break it; it did not break. I say push it.
On 2011/01/02 05:19:57, joeneeman wrote:
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.
The existing docs are good enough, in
On 1/4/11 6:45 PM, k-ohara5...@oco.net k-ohara5...@oco.net wrote:
I tried to break it; it did not break. I say push it.
Thanks for trying! And thanks for your help in identifying the right place
to put in the call to the new function.
On 2011/01/02 05:19:57, joeneeman wrote:
I don't know
LGTM, and it builds everything fine from scratch.
http://codereview.appspot.com/3832046/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
On Tue, Jan 04, 2011 at 09:06:56PM -, Phil Holmes wrote:
I've been creating a patch for the CG and wanted to test it. Early
this afternoon, I edited issues.itexi and compiled it locally, and
the changes were what I'd created. However, I'd missed a minor
edit, so I updated it and tried
http://codereview.appspot.com/3793046/diff/1/python/convertrules.py
File python/convertrules.py (right):
http://codereview.appspot.com/3793046/diff/1/python/convertrules.py#newcode2957
python/convertrules.py:2957: @rule ((2, 13, 10),
you're changing the rules for the 2.13.10 conversion? hmm.
It looks like we're getting close to the first release candidate.
- could any new contributors check:
http://lilypond.org/authors.html
to make sure they're there? if you have git access, you should
be in development team, and choose your own title. If not,
you should be listed in current
30 matches
Mail list logo
