Re: Release text (was Re: Lilypond code/feature freeze for 2.12)

I've folded in this and all the other comments. I think we're nearly there! How does the "thanks" bit get added? Trevor - Original Message - From: "Han-Wen Nienhuys" <[EMAIL PROTECTED]> To: "Carl D. Sorensen" <[EMAIL PROTECTED]> Cc: "Graham Percival" <[EMAIL PROTECTED]>; "Trevor Dani

Re: Release text (was Re: Lilypond code/feature freeze for 2.12)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 23. September 2008 schrieb Han-Wen Nienhuys: > On Mon, Sep 22, 2008 at 9:42 PM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote: > >> I don't. Yes, fret diagrams are very important to guitar players. > >> But dodecaphonic accidentals are very

* Add midi-extension command line option.

Reviewers: Neil Puttock, Message: LGTM Description: -if operating system is windows, change default to .mid. -recode PLATFORM variable using utsname:sysname. Please review this at http://codereview.appspot.com/5692 Affected files: M lily/performance.cc M scm/lily.scm M scm/midi.scm _

Re: Release text (was Re: Lilypond code/feature freeze for 2.12)

On Mon, Sep 22, 2008 at 9:42 PM, Carl D. Sorensen <[EMAIL PROTECTED]> wrote: >> I don't. Yes, fret diagrams are very important to guitar players. >> But dodecaphonic accidentals are very important to twelve-tone >> composers. Harp pedals are very important to harpists. Arbitrary >> microtonal a

Re: Release text (was Re: Lilypond code/feature freeze for 2.12)

On 9/22/08 5:54 PM, "Graham Percival" <[EMAIL PROTECTED]> wrote: > On Mon, 22 Sep 2008 17:07:16 -0600 > "Carl D. Sorensen" <[EMAIL PROTECTED]> wrote: > >> On 9/22/08 4:39 PM, "Trevor Daniels" <[EMAIL PROTECTED]> wrote: >> >>> Here's a version with fret diagrams, Reinhold's >>> suggestion and a fe

Re: lilypond -dhelp

Yeah, still same problem. I even moved the program to the Applications directory. vanessa_imac:/Applications/LilyPond.app/Contents/Resources/bin jamesebailey$ ./lilypond -dhelp GNU LilyPond 2.11.59 warning: not relocating, no 2.11.59/ or current/ found under /Applications/LilyPond.app/Contents/R

Re: lilypond -dhelp

Interesting. Works here on 10.4.11 intel. tsubasa:~ gperciva$ lilypond -dhelp GNU LilyPond 2.11.59 Options supported by ly:set-option anti-alias-factor (1) ... Could you try deleting the LilyPond.app and installing it again? Cheers, - Graham On Tue, 23 Sep 2008 01:49:38 +0200 "James E.

Re: Release text (was Re: Lilypond code/feature freeze for 2.12)

On Mon, 22 Sep 2008 17:07:16 -0600 "Carl D. Sorensen" <[EMAIL PROTECTED]> wrote: > On 9/22/08 4:39 PM, "Trevor Daniels" <[EMAIL PROTECTED]> wrote: > > > Here's a version with fret diagrams, Reinhold's > > suggestion and a few other tweaks. Is this > > better? > > > I like it I don't. Yes, fret

Re: [PATCH] MIDI command line option

Hi Han-Wen, I've uploaded this patch to Rietveld: http://codereview.appspot.com/5692 Is it OK to apply? Regards, Neil ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel

lilypond -dhelp

On osx 10.4, using the 2.11.59-1 intel binary, I get the following: vanessa_imac:~/Desktop/LilyPond.app/Contents/Resources/bin jamesebailey$ ./lilypond -dhelp GNU LilyPond 2.11.59 warning: not relocating, no 2.11.59/ or current/ found under /Users/jamesebailey/Desktop/LilyPond.app/Contents/Resour

Re: Lilypond code/feature freeze for 2.12

On Mon, 22 Sep 2008 12:08:29 -0300 "Han-Wen Nienhuys" <[EMAIL PROTECTED]> wrote: > On Mon, Sep 22, 2008 at 12:01 PM, John Mandereau > <[EMAIL PROTECTED]> wrote: > > > The conversion rules written with decorator syntax. It's certainly > > a lot easier and faster to revert this change and write th

Re: Release text (was Re: Lilypond code/feature freeze for 2.12)

I like it -- but instead of "countless" new features, can we say "more than a dozen", or "more than 50" or "dozens of" -- something to give an estimate of the order of magnitude? I counted 28 new features listed in NEWS. So perhaps we should say "nearly 30 new features" or "more than two dozen ne

Release text (was Re: Lilypond code/feature freeze for 2.12)

Here's a version with fret diagrams, Reinhold's suggestion and a few other tweaks. Is this better? Trevor - Original Message - From: "Carl D. Sorensen" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]>; "Trevor Daniels" <[EMAIL PROTECTED]> Cc: "lily-devel" Sent: Monday, September 22, 2008

Re: [PATCH] Two variations on the double repeat sign

2008/9/15 Han-Wen Nienhuys <[EMAIL PROTECTED]>: > LGTM - I wonder whether it would be nicer to put the string -> stencil > code in Scheme, though. Oh definitely, but it's probably best to leave it until after 2.12. I've done a few tests, and it's likely to add a few seconds to compile times. Reg

Re: Lilypond code/feature freeze for 2.12

On Sep 22, 2008, at 23:13 , John Mandereau wrote: On 2008/09/22, Matthias Neeracher wrote: In VocalEasel, I have some code which tests for the presence of python 2.4 and if not found shows an alert taking the user to the download page; I'd be happy to donate this to lilypond, but it's writte

Re: Lilypond code/feature freeze for 2.12

On 2008/09/22, Matthias Neeracher wrote: > From: "Trevor Daniels" <[EMAIL PROTECTED]> > > Do we -really- want to issue a new stable release > > containing masses of syntax changes with a broken > > convert-ly for many Mac users? > > The MacOS Python pages actu

Re: delete-intermediate-files

On Monday, September 22, 2008, at 09:20AM, "Graham Percival" <[EMAIL PROTECTED]> wrote: >Is there a good reason to have > delete-intermediate-files (#f) > delete unusable PostScript files >disabled by default? > >Cheers, >- Graham I don't know if there is, but I wa

Re: Lilypond code/feature freeze for 2.12

On 9/22/08 9:49 AM, "Han-Wen Nienhuys" <[EMAIL PROTECTED]> wrote: > > I was referring to Joe's page breaking, which will put page breaks in > sane places for multipage pieces, but I was mistaken. We shipped it > in 2.10. I'm not sure if we more earthshattering changes beyond gdp > and skylini

Re: Lilypond code/feature freeze for 2.12

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Montag, 22. September 2008 schrieb Trevor Daniels: > a huge number of bugs have been fixed, and countless >  exciting new features have been implemented. I would reverse these, so that the positive thing (new feature) comes before the bug fixes (w

Re: Lilypond code/feature freeze for 2.12

From: "Trevor Daniels" <[EMAIL PROTECTED]> John Mandereau Monday, September 22, 2008 12:02 AM On 2008/09/20 18:49 -0700, Graham Percival wrote: Forgot something: we should probably add warnings in the docs (or the download page) about the sorry state of OSX. 10.4 and 10.3: broken lilypond-bo

Re: Lilypond code/feature freeze for 2.12

Done; attached. Trevor - Original Message - From: "Han-Wen Nienhuys" <[EMAIL PROTECTED]> To: "Trevor Daniels" <[EMAIL PROTECTED]> Cc: "Valentin Villenave" <[EMAIL PROTECTED]>; "lily-devel" Sent: Monday, September 22, 2008 4:49 PM Subject: Re: Lilypond code/feature freeze for 2.12

Re: Lilypond code/feature freeze for 2.12

I'd drop Translation teams have also been working hard everywhere in the world: Since we can't decide which ones you'll enjoy the most, - Page-breaking has been improved with a new function designed to help with the production of books with many pages or lots of text, and the manual contro

Re: Lilypond code/feature freeze for 2.12

Han-Wen Nienhuys Monday, September 22, 2008 3:50 PM On Mon, Sep 22, 2008 at 5:53 AM, Valentin Villenave <[EMAIL PROTECTED]> wrote: I've read plenty of release announcements, but my reaction is different -- marketing make feel greasy and icky. I had five years of training to be as precise as po

Re: Lilypond code/feature freeze for 2.12

On Mon, Sep 22, 2008 at 12:18 PM, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > Google analytics says that 30% of macos visitors are on PPC; analytics does not distinguish between os versions. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen _

Re: Lilypond code/feature freeze for 2.12

On Mon, Sep 22, 2008 at 12:08 PM, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: >> The conversion rules written with decorator syntax. It's certainly a >> lot easier and faster to revert this change and write the syntax rules >> added after this change than shipping Python 2.4 with Darwin-PPC >> bi

Re: Lilypond code/feature freeze for 2.12

On Mon, Sep 22, 2008 at 12:01 PM, John Mandereau <[EMAIL PROTECTED]> wrote: >> can someone refresh my mind? I'm generally against catering for >> broken/old platforms, but maybe we can make an exception for >> convert-ly ; what broke for python 2.4 ? > > The conversion rules written with decorat

Re: Lilypond code/feature freeze for 2.12

Han-Wen Nienhuys wrote Monday, September 22, 2008 3:45 PM On Sun, Sep 21, 2008 at 8:02 PM, John Mandereau <[EMAIL PROTECTED]> wrote: 10.4 and 10.3: broken lilypond-book and convert-ly. The broken convert-ly is particularly unfortunate given the syntax changes between 2.10 and 2.12. These Py

Re: Lilypond code/feature freeze for 2.12

On 2008/09/22 11:45 -0300, Han-Wen Nienhuys wrote: > On Sun, Sep 21, 2008 at 8:02 PM, John Mandereau > <[EMAIL PROTECTED]> wrote: > > These Python scripts require Python 2.4, which is not provided in 10.3 > > and 10.4; ideally we should cross-compile Python and ship it in GUB > > binaries, but it c

Re: Lilypond code/feature freeze for 2.12

On Mon, Sep 22, 2008 at 5:53 AM, Valentin Villenave <[EMAIL PROTECTED]> wrote: >> I've read plenty of release announcements, but my reaction is >> different -- marketing make feel greasy and icky. I had five >> years of training to be as precise as possible in my analytic >> philosophy degree; I h

Re: Lilypond code/feature freeze for 2.12

On Sun, Sep 21, 2008 at 8:02 PM, John Mandereau <[EMAIL PROTECTED]> wrote: >> 10.4 and 10.3: broken lilypond-book and convert-ly. The broken >> convert-ly is particularly unfortunate given the syntax changes between >> 2.10 and 2.12. > > These Python scripts require Python 2.4, which is not provi

Re: Lilypond code/feature freeze for 2.12

John Mandereau Monday, September 22, 2008 12:02 AM On 2008/09/20 18:49 -0700, Graham Percival wrote: Forgot something: we should probably add warnings in the docs (or the download page) about the sorry state of OSX. 10.4 and 10.3: broken lilypond-book and convert-ly. The broken convert-ly i

Re: Lilypond code/feature freeze for 2.12

Thanks Valentin, LGTM. I've made a few tweaks, attached, which I think sharpen it a bit. Trevor - Original Message - From: "Valentin Villenave" <[EMAIL PROTECTED]> To: "Graham Percival" <[EMAIL PROTECTED]> Cc: "lily-devel" Sent: Monday, September 22, 2008 9:53 AM Subject: Re: Lilypon

Re: GUB experiments on linux-64

On za, 2008-09-20 at 14:04 -0300, Han-Wen Nienhuys wrote: Hi, > Regarding odcctools, I have no idea; I think Jan was using a mixed > 32/64 environment for building gub. Jan? Yes, and it was fully automagical too. Run GUB on x64, and an x64->ix86 cross compiler would gets built for building the

Re: Lilypond code/feature freeze for 2.12

2008/9/22 Graham Percival <[EMAIL PROTECTED]>: > I've read plenty of release announcements, but my reaction is > different -- marketing make feel greasy and icky. I had five > years of training to be as precise as possible in my analytic > philosophy degree; I hate empty phrases like "50 new feat

Re: Lilypond code/feature freeze for 2.12

On Mon, 22 Sep 2008 00:29:25 +0200 John Mandereau <[EMAIL PROTECTED]> wrote: > On 2008/09/21 02:30 -0700, Graham Percival wrote: > > Again, I had that initially, but removed it due to length > > considerations. The syntax changes for every new release, and > > it's listed in the NEWS, so I think

Re: Lilypond code/feature freeze for 2.12

On Sun, 21 Sep 2008 17:09:05 +0200 "Valentin Villenave" <[EMAIL PROTECTED]> wrote: > 2008/9/21 Graham Percival <[EMAIL PROTECTED]>: > > > Let me put it this way: when you read an announcement of a new > > release in some other software (say, audacity or freeciv), how > > much do you want to read?

Re: Lilypond code/feature freeze for 2.12

On Mon, 22 Sep 2008 01:02:32 +0200 John Mandereau <[EMAIL PROTECTED]> wrote: > The only solution on short term is asking users to install Python 2.4 > or 2.5 manually; IIRC Python scripts and/or their wrappers also need > to be edited to make them call the right Python, don't they? Yes. Point us

delete-intermediate-files

Is there a good reason to have delete-intermediate-files (#f) delete unusable PostScript files disabled by default? Cheers, - Graham ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/lis