Nicolas Sceaux <[EMAIL PROTECTED]> writes:
> for position = (if prev-line
> (+ prev-position
> (max distance
> (cond (prev-title? 0.0)
>(title?
> (- (
I've been investigating producing an index of commands, but it appears
that texinfo can only use each @findex once -- if I have an index of
@findex entries, then those entries won't appear in the general index
(despite my using @syncodeindex). I've asked for help on the texinfo
help list,
htt
Erik Sandberg schreef:
On 5/18/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Erik Sandberg schreef:
> If we use a separate module for syntax expressions, why not just say
foo?
> e.g.:
> (sequential-music .. )
> for a syntax expression that represents (and, incidentally, produces
music
>
On 5/18/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
Erik Sandberg schreef:
> If we use a separate module for syntax expressions, why not just say foo?
> e.g.:
> (sequential-music .. )
> for a syntax expression that represents (and, incidentally, produces music
> which represents) sequentia
Erik Sandberg schreef:
I realised that there's a thinko in this naming convention:
(make-syntax-foo ...) _is_ a syntax expression, and it _makes_ a music
expression.
yes.
If we use a separate module for syntax expressions, why not just say foo?
e.g.:
(sequential-music .. )
for a syntax e
On Wednesday 17 May 2006 19:28, Erik Sandberg wrote:
> On Wednesday 17 May 2006 17:31, Han-Wen Nienhuys wrote:
> > Erik Sandberg schreef:
> > > The next step in parser split-up is to move rules out to Scheme. There
> > > will be a lot of functions, so I suggest we create a new make-music.scm
> > >
Hi Han-WenOn 5/16/06, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
diff -u lilypond/lily/hairpin.cc:1.65 lilypond/lily/hairpin.cc:1.66--- lilypond/lily/hairpin.cc:1.65 Tue Apr 11 12:36:44 2006+++ lilypond/lily/hairpin.ccTue May 16 19:00:39 2006@@ -162,7 +162,7 @@
x_poin
