Re: Yet Another music macro proposal

2006-05-12 Thread Werner LEMBERG
> Your post just reminded me that I've written a version of \parallelMusic > with relative mode after a request by Werner (and I forgot about it > during holidays). Aaah! Is this mature enough that you can send it to the list? Werner ___ lilypo

system-count bugfix

2006-05-12 Thread Joe Neeman
Here is a patch for the bug found by Trent Johnston: 2006-05-13 Joe Neeman <[EMAIL PROTECTED]> * lily/constrained-breaking.cc (resize): give a default value for system-height Index: ChangeLog === RCS file: /sources/l

Re: Yet Another music macro proposal

2006-05-12 Thread Erik Sandberg
On 5/12/06, Nicolas Sceaux <[EMAIL PROTECTED]> wrote: Erik Sandberg <[EMAIL PROTECTED]> writes: > Hi, > > I have yet another suggestion for how \relative can be soft-coded in a generic > way. It's inspired by criticism of earlier attempts. It's similar, but not > identical, to a previous suggest

Re: implementation plan for music streams

2006-05-12 Thread Erik Sandberg
On 5/12/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Erik Sandberg schreef: > Hm, I guess the easiest/cleanest way would be to let the > percent-repeat-iterator create an implicit SequentialMusic around the music, > with the additional percent elements, and then to let process_music pretend >

Re: (doc/language help) resp?

2006-05-12 Thread Trevor Bača
On 5/12/06, Nicolas Sceaux <[EMAIL PROTECTED]> wrote: Werner LEMBERG <[EMAIL PROTECTED]> writes: >> Sorry, it was a French-ism, where it looks like the Swedish way: >> "A, respectivement B, ..." > > In German we have the same: `A bzw. B' (where `bzw.' is short for > `beziehungsweise'). Strange

Re: (doc/language help) resp?

2006-05-12 Thread Nicolas Sceaux
Werner LEMBERG <[EMAIL PROTECTED]> writes: >> Sorry, it was a French-ism, where it looks like the Swedish way: >> "A, respectivement B, ..." > > In German we have the same: `A bzw. B' (where `bzw.' is short for > `beziehungsweise'). Strange coincidence, I've made a peer review today on a spec wr

Re: Yet Another music macro proposal

2006-05-12 Thread Nicolas Sceaux
Erik Sandberg <[EMAIL PROTECTED]> writes: > Hi, > > I have yet another suggestion for how \relative can be soft-coded in a > generic > way. It's inspired by criticism of earlier attempts. It's similar, but not > identical, to a previous suggestion. > > Macros is that they operate on syntax, not

Re: Transformation experiments

2006-05-12 Thread Erlend Aasland
On 5/12/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: > Ok. New version attached. I've thrown in something for the SVG-backend> too, but that part is a bit buggy (I'll have to take a closer look at> the SVG spec next week). The C++ stuff and PS-backend should look good now. OK. If please commit w

Re: PPC vs. x86

2006-05-12 Thread Han-Wen Nienhuys
Graham Percival schreef: Would it be possible to include a small check in the OSX versions which would display an error message if people tried to run the wrong kind of binary? We've had two people trying to run the Intel version on a PPC chip, and the current error message is not at all helpf

Re: Transformation experiments

2006-05-12 Thread Han-Wen Nienhuys
Erlend Aasland schreef: Hi Han-Wen On 5/8/06, *Han-Wen Nienhuys* <[EMAIL PROTECTED] > wrote: Erlend Aasland wrote: > There are no bugs with the current code, so why rewrite it? Because it's not _obviously_ correct. Ok. New version attached. I've thrown

Re: (doc help) scheme: why not start with define-music-function ?

2006-05-12 Thread Erik Sandberg
On Friday 12 May 2006 02:03, Han-Wen Nienhuys wrote: > Mats Bengtsson schreef: > > A related question, how do you define a music function that takes > > a string or a markup as an argument? > > You don't. It has to take either a markup or a string. Actually, you can let it take a Scheme expression

Re: configure does not check for python version >=2.4

2006-05-12 Thread Karl Hammar
> Hi, > > On Fri, 12 May 2006, Karl Hammar wrote: > > > > make: *** [all] Error 2 > > > > > > Which fails due to missing module subprocess. > > > It was introduced recently: > > And it was discussed recently: > > http://article.gmane.org/gmane.comp.gnu.lilypond.devel/8996 Yes, but without a

Re: (doc help) scheme: why not start with define-music-function ?

2006-05-12 Thread Mats Bengtsson
Han-Wen Nienhuys wrote: Mats Bengtsson schreef: A related question, how do you define a music function that takes a string or a markup as an argument? You don't. It has to take either a markup or a string. That's a pity, since we have lots of properties, like text and instrument and also

Re: Yet Another music macro proposal

2006-05-12 Thread Erik Sandberg
On Friday 12 May 2006 10:27, Han-Wen Nienhuys wrote: > Erik Sandberg schreef: > > Hi, > > > > I have yet another suggestion for how \relative can be soft-coded in a > > generic way. It's inspired by criticism of earlier attempts. It's > > similar, but not identical, to a previous suggestion. > > >

PPC vs. x86

2006-05-12 Thread Graham Percival
Would it be possible to include a small check in the OSX versions which would display an error message if people tried to run the wrong kind of binary? We've had two people trying to run the Intel version on a PPC chip, and the current error message is not at all helpful. In bash script, I'd

Re: Contexts (Was Re: Set vs. Override - I'm confused)

2006-05-12 Thread Graham Percival
On 8-May-06, at 7:26 AM, Erik Sandberg wrote: On Saturday 06 May 2006 13:25, Graham Percival wrote: Erik, could I get a copy of Figure 10, illustrating Score, Staff, and Voice contexts? It's the first figure in appendix C. I think it would be good to add to the lilypond manual. I'm sendi

Re: configure does not check for python version >=2.4

2006-05-12 Thread Johannes Schindelin
Hi, On Fri, 12 May 2006, Karl Hammar wrote: > > make: *** [all] Error 2 > > > > Which fails due to missing module subprocess. > > It was introduced recently: And it was discussed recently: http://article.gmane.org/gmane.comp.gnu.lilypond.devel/8996 > Hm, configure.in seems better suited for

Re: Transformation experiments

2006-05-12 Thread Erlend Aasland
Hi Han-WenOn 5/8/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote: Erlend Aasland wrote:> There are no bugs with the current code, so why rewrite it?Because it's not _obviously_ correct.Ok. New version attached. I've thrown in something for the SVG-backend too, but that part is a bit buggy (I'll have

Re: implementation plan for music streams

2006-05-12 Thread Erik Sandberg
On Friday 12 May 2006 12:17, Han-Wen Nienhuys wrote: > Erik Sandberg schreef: > > eliminate the parser's need to wrap expressions inside \context Bottom. I > > can implement this when I've finished some more of the music stream > > refactorings. > > come to think of it, I'm still missing the define

Re: implementation plan for music streams

2006-05-12 Thread Han-Wen Nienhuys
Erik Sandberg schreef: eliminate the parser's need to wrap expressions inside \context Bottom. I can implement this when I've finished some more of the music stream refactorings. come to think of it, I'm still missing the define-event-classes.scm file. -- Han-Wen Nienhuys - [EMAIL PROTECTED]

Re: Yet Another music macro proposal

2006-05-12 Thread Han-Wen Nienhuys
Erik Sandberg schreef: Hi, I have yet another suggestion for how \relative can be soft-coded in a generic way. It's inspired by criticism of earlier attempts. It's similar, but not identical, to a previous suggestion. Macros is that they operate on syntax, not on music. And the parser spits

Re: implementation plan for music streams

2006-05-12 Thread Han-Wen Nienhuys
Erik Sandberg schreef: On Thursday 11 May 2006 00:54, Han-Wen Nienhuys wrote: 2006/5/10, Erik Sandberg <[EMAIL PROTECTED]>: Citerar Han-Wen Nienhuys <[EMAIL PROTECTED]>: Known issue: unfold-repeats will probably not work for percent I don't understand this. unfold-repeats is on the front end,

Re: Yet Another music macro proposal

2006-05-12 Thread Bertalan Fodor
Well, I'm a bit scared. It would be very valuable, if not only lilypond would be the only parser on the world which can parse a ly file. For example I had a very hard time to create my preliminary java parser, because lilypond's syntax is so free and so dynamic (the language itself can be redef