Reviewers: ,
Message:
Before pushing the stem patch (thanks to Trevor and Han Wen for the
LGTMs), I'd like to push this one. It allows for beam collision to
happen momentarily on the Voice level via an override. I will
subsequently integrate this into the quote.ly and quote-during.ly
regtests.
Warning for all new contributors: due to changes in the translations,
you must run
../configure
in your build directory in order to make lilypond again.
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailm
Sorry about the confusion on documentation -- I misread the initial
version. Yes, even though the current version is incorrect, let's just
go with it anyway.
(really, adding new features and writing documentation about them are
completely different things; there's no point holding back a new fea
Hi guys,
If you've put anything on rietveld recently, please go here:
http://codereview.appspot.com/mine
You'll probably see a bunch of issues under "created by me". If you
recognize anything that you pushed, could you go to that issue, click
on "edit issue", then click on "close" and save it?
On Wed, Apr 6, 2011 at 4:32 PM, m...@apollinemike.com
wrote:
> Hey all,
>
> I'd like to check in an engraver to see if two grobs were created in the same
> voice. Is this possible?
Have a look at the Grob_info class.
--
Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen
___
On 2011/04/06 21:47:34, Graham Percival wrote:
... no wait, we do! hmm... I'll look into this. It might be a bit
tricky, so
I'll handle it myself.
Yeah, it was a bit tricky. But done now:
http://git.savannah.gnu.org/gitweb/?p=lilypond.git;a=commit;h=66b49771545a61b591b529330797163ff42e2e8f
I don't think we want to add papersize_test.tely to the repository.
It's very important that we have such a file while evaluating the patch,
but I think it would be better sent as an attachment in an email to
-devel.
We certainly don't want to add it to build/foo, since that would mess up
the com
So I think this is a bug in the build of the installer rather than the
installer or LP itself -
but I'd defer to those that know more about building. It;s not a huge deal
but I'd be interested in what Phil's PATH looks like :) He says he has
installed over 22 versions.
I know there is a limit
URL: http://codereview.appspot.com/4368049
Added new Pagesize definition to paper.scm
Added 'c9landscape' to allow a very small @lilypond to be defined for
examples that need to show footers, tagelines and the like, without having to
1.define the paper size inside the @lilypond (and so make the
2011/4/6 James Lowe :
> Janek
>
> As I said that I do use add/remove and also if you read above it doesn't
> remove the path as I have so many 'C:\Program Files\LilyPond\usr\bin;'
> entries. I'd expect the uninstaller to remove the path, but that requires
> some 'scripting' when the installer is
Janek
From: Janek Warchoł [lemniskata.bernoull...@gmail.com]
Sent: 06 April 2011 19:07
To: James Lowe
Cc: lilypond-devel@gnu.org
Subject: Re: lilypond v2.13.54
James,
sorry - i forgot about your e-mail!
:(
2011/3/21 James Lowe
>
> Janek,
>
> )-Origin
Hey all,
I'd like to check in an engraver to see if two grobs were created in the same
voice. Is this possible?
Cheers,
MS
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
>> IMHO, VERSION_DEVEL should be be 2.13.58 also.
>
> No.
> http://lilypond.org/doc/v2.13/Documentation/contributor/minor-release-checklist
OK. Maybe it's a one-time glitch for unknown reasons (since I haven't
experienced this previously).
Werner
__
On Wed, Apr 06, 2011 at 03:13:00PM +0200, Werner LEMBERG wrote:
>
> -PATCH_LEVEL=57
> +PATCH_LEVEL=58
> MY_PATCH_LEVEL=
> VERSION_STABLE=2.12.3
> -VERSION_DEVEL=2.13.56
> +VERSION_DEVEL=2.13.57
>
>
> IMHO, VERSION_DEVEL should be be 2.13.58 also.
No.
http://lilypond.org/doc/v2.13/Documentatio
James,
sorry - i forgot about your e-mail!
:(
2011/3/21 James Lowe
>
> Janek,
>
> )-Original Message-
> )From: Janek Warchoł [mailto:lemniskata.bernoull...@gmail.com]
> )Sent: 21 March 2011 16:35
> )To: James Lowe
> )Subject: Re: lilypond v2.13.54
> )
> )2011/3/21 James Lowe
> )>
> )> J
Hello, gentle maintainer.
This is a message from the Translation Project robot.
A revised PO file for textual domain 'lilypond' has been submitted
by the French team of translators. The file is available at:
http://translationproject.org/latest/lilypond/fr.po
(We can arrange things so that
Hello
)-Original Message-
)From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
)[mailto:lilypond-devel-bounces+james.lowe=datacore@gnu.org] On
)Behalf Of Reinhold Kainhofer
)Sent: 06 April 2011 17:03
)To: LilyPond Development
)Subject: How to separate footnotes from the footer
It seems that I'm unable to increase the (way too narrow) spacing between a
footnote and the copyright line (or tagline) on the first page.
I have tried various combinations of last-bottom-spacing, markup-markup-
spacing etc, but nothing seems to have any influence on the space between the
footno
On Wed, Apr 6, 2011 at 9:36 AM, Reinhold Kainhofer
wrote:
> In figured bass, attaching a text script to a skip (because one has to mark
> tasto solo parts with "t.s.") works, but it is not possible to use the _
> direction indicator to print it below the staff. ^ and - work fine. Simple
> test cas
Han-Wen Nienhuys writes:
> On Tue, Apr 5, 2011 at 2:41 AM, David Kastrup wrote:
+nan.0 appears fine for that. But can we rely on it being available on
supported platforms? I don't find it in the sources of Lilypond, though
>>>
>>> It sounds a bit fishy especially since alterations ar
On Tue, Apr 5, 2011 at 2:41 AM, David Kastrup wrote:
>>> +nan.0 appears fine for that. But can we rely on it being available on
>>> supported platforms? I don't find it in the sources of Lilypond, though
>>
>> It sounds a bit fishy especially since alterations are normally
>> rational numbers.
LGTM
http://codereview.appspot.com/4337045/diff/18002/lily/beam-collision-engraver.cc
File lily/beam-collision-engraver.cc (right):
http://codereview.appspot.com/4337045/diff/18002/lily/beam-collision-engraver.cc#newcode108
lily/beam-collision-engraver.cc:108: skip_me = true;
i'd use
continue
In figured bass, attaching a text script to a skip (because one has to mark
tasto solo parts with "t.s.") works, but it is not possible to use the _
direction indicator to print it below the staff. ^ and - work fine. Simple
test case attached.
The problem happens in 2.12 as well as in 2.13.
AF
David Kastrup writes:
> Han-Wen Nienhuys writes:
>
>> On Mon, Apr 4, 2011 at 3:15 PM, David Kastrup wrote:
>>>
>>> Hi, I am trying to come up with an alteration value that does not match
>>> "normal" alterations but is neither positive nor negative (since
>>> otherwise a "change" will cause nat
This looks wrong to me:
-PATCH_LEVEL=57
+PATCH_LEVEL=58
MY_PATCH_LEVEL=
VERSION_STABLE=2.12.3
-VERSION_DEVEL=2.13.56
+VERSION_DEVEL=2.13.57
IMHO, VERSION_DEVEL should be be 2.13.58 also. I had to manually adjust
/usr/local/bin/convert-ly:
for d in ['/usr/local/share/lilypond/2.13.58',
2011/4/6 Francisco Vila :
> 2011/4/6 :
>> Uploading third patch.
>
> http://codereview.appspot.com/4277067/
>
> If it is done, could you push it by yourself before 2.14? I never
> know how long exactly to wait before pushing.
In addition, should I update Changes?
--
Francisco Vila. Badajoz (Sp
2011/4/6 :
> Uploading third patch.
http://codereview.appspot.com/4277067/
If it is done, could you push it by yourself before 2.14? I never
know how long exactly to wait before pushing.
--
Francisco Vila. Badajoz (Spain)
www.paconet.org , www.csmbadajoz.com
__
Uploading third patch.
http://codereview.appspot.com/4277067/diff/5001/Documentation/notation/input.itely
File Documentation/notation/input.itely (right):
http://codereview.appspot.com/4277067/diff/5001/Documentation/notation/input.itely#newcode1956
Documentation/notation/input.itely:1956: exce
On Apr 6, 2011, at 4:19 AM, Trevor Daniels wrote:
>
> mts...@gmail.com wrote Tuesday, April 05, 2011 10:35 PM
>
>
>> I'd like to get this pushed in the next 24 hours if possible (which will
>> require 2 LGTMs). This way, << { c'8 [ s c' ] } \\ { s c''8 s } >> will
>> be prettier.
>
> Here's
2011/4/4 Graham Percival
> Ah. Well, unfortunately we (as a developer community) do not tend
> to review patches very often.
>
> Think about it this way: how many times have you reviewed my build
> system patches, or Colin's documentation patches? The same
> reasons why you don't review those pa
mts...@gmail.com wrote Tuesday, April 05, 2011 10:35 PM
I'd like to get this pushed in the next 24 hours if possible
(which will
require 2 LGTMs). This way, << { c'8 [ s c' ] } \\ { s c''8 s }
>> will
be prettier.
Here's one. LGTM.
It certainly improves the revised regtest, but
I don't
Han-Wen Nienhuys writes:
> On Mon, Apr 4, 2011 at 3:15 PM, David Kastrup wrote:
>>
>> Hi, I am trying to come up with an alteration value that does not match
>> "normal" alterations but is neither positive nor negative (since
>> otherwise a "change" will cause naturals to be printed).
>>
>> +nan
32 matches
Mail list logo
