[lilypond CVS 2004-02-28 5:30 MET]
The current compilation problem triggers a nasty bug in makeinfo 4.6:
LANG= \
makeinfo \
-I /home/sx0005/lilypond//Documentation/user/out \
--output=/home/sx0005/lilypond//Documentation/user/out/lilypond.info \
/home/sx0005/lilypond//Documentati
[CVS 2004-02-28 5:30 MET]
Currently, I see lines like
* GNU LilyPond: (./lilypond/lilypond).The GNU music typesetter.
^^^
Is this really correct? Shouldn't this be
* GNU LilyPond: (lilypond).The GNU music typesetter.
As it was previo
<>
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
<>
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
<>
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
[EMAIL PROTECTED] writes:
> http://lilypond.org/doc/v2.1/input/regression/out-www/lily-1485554506.ly
>
> Same as subject... only a bug report
Actually, it's ok, since the stretching space is equal.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
_
[EMAIL PROTECTED] writes:
>
> Why not to have commands \arpeggioup and \arpeggiodown?
> They would be handy.
Go ahead.
Please consider the capitalization standards, though.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
[EMAIL PROTECTED] writes:
> >
> > > Also, is it possible to use simulataneous music (<< >>)
> > > in \drums? It doesn't seem to work. This is really needed
> > > for practical drum notation, as habing two seperate voices
> > > is just too likely to be a source for errors.
> >
> > Please send faulty
[EMAIL PROTECTED] writes:
> % In the second note from the right ( a-. ) the staccato dot collides with
> % rows extension (dash)
thanks, fixed in CVS.
--
Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen
___
Lilypond-dev
[EMAIL PROTECTED] writes:
> > Yes, but it also takes me extra time. (I'm a lazy bum). You can
> > subscribe to [EMAIL PROTECTED] to get the latest scoops.
>
> Thanks for the tip. You should mention this list on
>
> http://lilypond.org/web/documentation.html
>
> where you should also change "Bugr
> Do you think that could actually be interesting? ie: should I go on
> implementing and documenting this?
This sort of thing is great. There's a lot of potential to implement
higher-level convenience stuff that LilyPond currently lacks, but that
doesn't need to be written into the core.
--
http
[EMAIL PROTECTED] writes:
> The goal of course is to help users (hmm, it cannot be only me, there
> must be few others!) creating scheme functions. Collateral damage:
> internal function definitions may also be simpler.
>
> Do you think that could actually be interesting? ie: should I go on
> impl
[EMAIL PROTECTED] writes:
> Han-Wen,
>
> You will find attached an archive with some patches:
> ly/dynamic-scripts-init.ly-patch
> scm/chord-entry.scm-patch
> scm/clef.scm-patch
> scm/music-functions.scm-patch
> scm/part-combiner.scm-patch
applied.
> If you prefer patches without coding sty
<>
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
<>
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
<>
___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel
Hello,
I am currently writing a lib that aims at easily building music
expressions. I took the manual from the first page to the last one and
collected the syntactic constructs that imho ought to have a dedicated
scheme function or macro. It looks like this (drums.ly):
\score {
<<
\ne
Han-Wen,
You will find attached an archive with some patches:
ly/dynamic-scripts-init.ly-patch
scm/chord-entry.scm-patch
scm/clef.scm-patch
scm/music-functions.scm-patch
scm/part-combiner.scm-patch
- in music-functions.scm, ly:grob-property and ly:music-property are
made procedure with set
18 matches
Mail list logo
