Hello,
Where should the documentation for #{ ... #} take place?
nicolas
PS: I have commited the changes for the \addlyrics \appoggiatura
\acciaccatura \grace \partcombine \autochange \applycontext
\applyoutput and \breathe music functions.
___
lilyp
Right now I've seen that some bug reports have been removed from
lily-bugs.
I strongly suggest to start a ChangeLog file to document changes in
the repository, mainly to avoid reporting the same errors again and
again.
Werner
___
lilypond-devel
Nicolas Sceaux writes:
> In the patch, I have left untouched the current \tag command, that is,
> no ly:make-music-function for it and no shift/reduce conflicts
> introduced. It is left TODO. make web is running.
Great.
> Oh, by the way, this ly:make-music-function was really the ultimate
> wiza
Sat, 15 May 2004 11:18:38 +0200, Jan a dit :
> Han-Wen Nienhuys writes:
>>> hm, my attempts introduce 39 shift/reduce conflicts...
> It looks very good, but we should find and fix these problems first,
> right?
In the patch, I have left untouched the current \tag command, that is,
no ly:mak
Han-Wen Nienhuys writes:
>> hm, my attempts introduce 39 shift/reduce conflicts...
It looks very good, but we should find and fix these problems first,
right?
> Looks good! If you can get the regtest to build, then please apply.
> Thanks!
--
Jan Nieuwenhuizen <[EMAIL PROTECTED]> | GNU LilyPon
