On Sun, Jun 5, 2011 at 4:01 PM, Graham Percival
wrote:
>
> Proposal: let’s follow PEP-8.
> http://www.python.org/dev/peps/pep-0008/
>
> * use 4 spaces per indentation level
> * never max tabs and spaces
> * Code indented with a mixture of tabs and spaces should be
> converted to usin
HOORAY!! WOOT! YEEHAR!
Well done to all Lilypond contributors, especially to Graham for being
Releasemeister and all the project management stuff.
Hoping to contribute more to 2.15/16 now I'm out of hospital.
Cheers,
Ian
On 06/06/11 00:00, Graham Percival wrote:
> It is now 00:00:10 BST on 06 J
On 06/06/11 00:01, Graham Percival wrote:
> Proposal website:
> http://lilypond.org/~graham/gop/gop_1.html
>
>
> (this proposal will be rushed because nobody will argue against
> it. Initial discussion 6 June, summary and tentative decision 8
> June, implementation 10 June)
>
> Proposal: let’s f
On Mon, 6 Jun 2011, Graham Percival wrote:
* never max tabs and spaces
max = mix ?
--
MT
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Congratulations everybody!
Janek
2011/6/6 Graham Percival
> It is now 00:00:10 BST on 06 June, 2011. I see precisely zero
> open Critical issues, and precisely zero Critical issues waiting
> to be verified.
>
> If you have been holding your breath, you can exhale.
>
> Cheers,
> - Graham
>
> ___
> HOORAY!
>
> :)
Thanks A LOT especially to you, Graham, for your hard work on it! And
kudos to all the other more active developers who have made this
release possible.
Werner
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://list
> Proposal: let’s follow PEP-8.
> http://www.python.org/dev/peps/pep-0008/
>
> * use 4 spaces per indentation level
I prefer 2 spaces (this allows for longer lines while staying in the
80 char line length limit), but since all python code already uses 4
spaces, this is OK with me.
Just curio
Yeayyy!!! Thanks for all the hard work!!
Paul Scott
On 06/05/2011 04:00 PM, Graham Percival wrote:
It is now 00:00:10 BST on 06 June, 2011. I see precisely zero
open Critical issues, and precisely zero Critical issues waiting
to be verified.
If you have been holding your breath, you can exh
> "Graham" == Graham Percival writes:
Graham> On Mon, Jun 06, 2011 at 10:06:31AM +1000, Peter Chubb wrote:
>> Grabbed from git this morning, very simple file:
Graham> ick.
I've fixed it. The problem was that the VERSION file in the toplevel
doesn't depend on whatever it is that sets the ve
On Mon, Jun 06, 2011 at 10:06:31AM +1000, Peter Chubb wrote:
> Grabbed from git this morning, very simple file:
ick.
However, I'm happy to report that 2.14.0 does not have this
problem. :)
Cheers,
- Graham
___
lilypond-devel mailing list
lilypond-dev
Grabbed from git this morning, very simple file:
\version "2.15.0"
notes=\relative c' {
4
}
\score {
\context Staff \notes
}
I see:
GNU LilyPond 2.15.0
Processing `x.ly'
Parsing...
Interpreting music... *** glibc detected *** lilypond: double free or
corruption (out): 0x000
On Sun, Jun 05, 2011 at 07:42:56PM -0400, Michael Welsh Duggan wrote:
> Graham Percival writes:
>
> > * Code indented with a mixture of tabs and spaces should be
> > converted to using spaces exclusively
>
> For the purposes of consistency (both within Lilypond's sources, and
> within
Graham Percival writes:
> Proposal website:
> http://lilypond.org/~graham/gop/gop_1.html
>
>
> (this proposal will be rushed because nobody will argue against
> it. Initial discussion 6 June, summary and tentative decision 8
> June, implementation 10 June)
>
> Proposal: let’s follow PEP-8.
> http
HOORAY!
:)
From: lilypond-devel-bounces+james.lowe=datacore@gnu.org
[lilypond-devel-bounces+james.lowe=datacore@gnu.org] on behalf of Graham
Percival [gra...@percival-music.ca]
Sent: 06 June 2011 00:00
To: lilypond-devel@gnu.org
Subject: 06 June,
To whoever enjoys this stuff,
1) please check that stable/2.14 has no useful commits that are not
in master. I think the only difference is in VERSION and
various disasters concerning Documentation/web/news-front.itexi,
but I'd like to be safe.
2) make release/unstable be exactly what we h
Proposal website:
http://lilypond.org/~graham/gop/gop_1.html
(this proposal will be rushed because nobody will argue against
it. Initial discussion 6 June, summary and tentative decision 8
June, implementation 10 June)
Proposal: let’s follow PEP-8.
http://www.python.org/dev/peps/pep-0008/
*
The below is copied from
http://lilypond.org/~graham/gop/
There are a number of policy decisions -- some of them fairly
important -- which we have been postponing for a few years. Now
that 2.14 is out, we will finally begin tackling them
More background is here:
http://lilypond.org/doc/v2.13/Doc
It is now 00:00:10 BST on 06 June, 2011. I see precisely zero
open Critical issues, and precisely zero Critical issues waiting
to be verified.
If you have been holding your breath, you can exhale.
Cheers,
- Graham
___
lilypond-devel mailing list
lilyp
thanks all, this is now pushed.
http://codereview.appspot.com/4373046/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
k...@aspodata.se (Karl Hammar) writes:
> David:
>> Offlist http://www.haumacher.de/svg-import/> has been suggested to
>> me. The JAR file mentioned in there works for converting lilypond-book
>> images placed into PDF, extracted with preview.sty, converted with
>> pdf2svg to SVG to .odg files (Op
David:
> Offlist http://www.haumacher.de/svg-import/> has been suggested to
> me. The JAR file mentioned in there works for converting lilypond-book
> images placed into PDF, extracted with preview.sty, converted with
> pdf2svg to SVG to .odg files (OpenOffice Draw Graphics?) as OLE links
> into a
Offlist http://www.haumacher.de/svg-import/> has been suggested to
me. The JAR file mentioned in there works for converting lilypond-book
images placed into PDF, extracted with preview.sty, converted with
pdf2svg to SVG to .odg files (OpenOffice Draw Graphics?) as OLE links
into an OpenOffice doc
On 28/05/11 17:16, Graham Percival wrote:
> On Sat, May 28, 2011 at 04:54:57PM +0100, Phil Holmes wrote:
>> - Original Message - From: "Graham Percival"
>>
>>> Why not redirect the compile-output from each .ly to the
>>> appropriate .log file? I mean, we *already* have a .log for each
>>>
If I understand well, there's no need anymore for manual beams in
cross-staff cases ?
If so, I suggest you remove the manual beams from
input/regression/beam-collision-cross-staff.ly.
You should also remove the knownissues in keyboard.itely and the last
part of changes.tely's entry.
Thanks,
Bertr
Ok, I'll change these. What about 'No.' ? '№', 'N°' or '&N°;' ?
http://codereview.appspot.com/4553056/
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Hi Mike
Shouldn't you be using the TupletNumber grob?
Trevor
- Original Message -
From:
To:
Sent: Sunday, June 05, 2011 12:00 PM
Subject: Outside staff priority for tuplet bracket and tuplet number
Hey all,
I'm running into a problem with the following snippet of code and,
befo
Hey all,
I'm running into a problem with the following snippet of code and, before I try
to fix it, I was wondering if anyone knew why these two bits of code yielded
the same result:
\relative c'' { \override Staff . TupletBracket #'outside-staff-priority = #0
\override Staff . Script #'outside
On Jun 4, 2011, at 5:16 PM, n.putt...@gmail.com wrote:
> On 2011/06/04 12:50:55, MikeSol wrote:
>
>> This, in combination with my stem-attachment patch, allows for the
> small notes
>> above harmonics that give the sounding pitch to be typset well.
>
> I think you should consider making the soun
On Jun 2, 2011, at 9:00 PM, n.putt...@gmail.com wrote:
>
> http://codereview.appspot.com/4527086/diff/7002/scm/output-lib.scm
> File scm/output-lib.scm (right):
>
> http://codereview.appspot.com/4527086/diff/7002/scm/output-lib.scm#newcode795
> scm/output-lib.scm:795: (define-public (glissando::
29 matches
Mail list logo
