Some 2.3.12 issues

2004-08-22 Thread Matthias Neeracher
Here's some issues I had to work around building 2.3.12 on MacOS: 1) gettext() not found: On MacOS, gettext() is not in the regular POSIX libraries, so lily-guile.cc needs: #include I'm sure this is not appropriate for all platforms, so I suppose some subtlety would be required to make this por

Re: changing page numbers

2004-08-22 Thread Pedro Kroger
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > how about firstPageNumber ? (or firstpagenumber) sounds good to me. I've changed to firstpagenumber. I commited the changes and updated the manual. Pedro ___ lilypond-devel mailing list [EMAIL PROTECTED]

Help Wanted: LilyPond templates chapter

2004-08-22 Thread Han-Wen Nienhuys
Hi Y'all, LilyPond development is gearing up towards a new, better, funkier glitzier stable release, and that is LilyPond 3.0. It will be easier to use than ever before, it has more capabilities, and the layout is so much improved that reading LilyPond 3.0 parts will instantaneously improve your

How to start to implement something?

2004-08-22 Thread Bertalan Fodor
I would like to implement a general solution for a new symbol: in keyboard music the lines that shows that something written in the lower staff should be played in the right hand. It suppose it is not so difficult to implement it as an engraver. However, I don't know how to start it. To give yo

Re: Two small patches for lilypond/cygwin

2004-08-22 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > OK, I'm trying. > > Thx, applied. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Two small patches for lilypond/cygwin

2004-08-22 Thread Bertalan Fodor
OK, I'm trying. Thx, Bert Han-Wen Nienhuys wrote: [EMAIL PROTECTED] writes: I resend these. The first is important for running bug-lilypond-cygwin, the second one simplifies releasing. (If I ever succeed :-) ) I think your mail reader formatted the patch. Can you send them as an attachment to

Re: changing page numbers

2004-08-22 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > > > [EMAIL PROTECTED] writes: > >> > >> Since the old `pagenumber' parameter of \paper is gone for the PS > >> backend (why?), what shall be used instead to make lilypond start on, > >> say, page 2? Looking into framewor

Re: What happened with lilypond-cvs@gnu.org ?

2004-08-22 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > Could you, please, add me to the list too? > > [EMAIL PROTECTED] done! > > TIA, > > Pedro > > > ___ > lilypond-devel mailing list > [EMAIL PROTECTED] > http://lists.gnu.org/mailman/listinfo/lilypond-devel -- Han-W

Re: What happened with lilypond-cvs@gnu.org ?

2004-08-22 Thread Pedro Kroger
Could you, please, add me to the list too? [EMAIL PROTECTED] TIA, Pedro ___ lilypond-devel mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: changing page numbers

2004-08-22 Thread Pedro Kroger
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > [EMAIL PROTECTED] writes: >> >> Since the old `pagenumber' parameter of \paper is gone for the PS >> backend (why?), what shall be used instead to make lilypond start on, >> say, page 2? Looking into framework-ps.scm, function >> `output-framework'

Re: bug report format change

2004-08-22 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > On Sunday 22 August 2004 13.28, Han-Wen Nienhuys wrote: > > Hi Eric, > > > > the bug collection has gotten rather large, and difficult for me to > > get an overview of. To help things, I'm adding a .ly -> .tely -> .texi > > -> conversion and a GNUmakefile, so I can get a

Re: bug report format change

2004-08-22 Thread Erik Sandberg
On Sunday 22 August 2004 13.28, Han-Wen Nienhuys wrote: > Hi Eric, > > the bug collection has gotten rather large, and difficult for me to > get an overview of. To help things, I'm adding a .ly -> .tely -> .texi > -> conversion and a GNUmakefile, so I can get a neat .HTML with > images, containing

Re: bug: old-relative.ly

2004-08-22 Thread Erik Sandberg
On Sunday 22 August 2004 13.01, Han-Wen Nienhuys wrote: > "The following gives no warning (it should; the first set-option is > superfluous. The problem occurs often in reality, through \include)" } > > I disagree. Not a bug, won't fix. ok. removed those bugs from cvs. erik

Re: bug report format change

2004-08-22 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > > Creating a makefile is a very good idea. I'm actually losing overview myself, > as well. > > Hm - while you are at it: Notice the format of the two first lines of each > file. The first line is a list of flags, the second line is a CC: field; > changes in the bug

Re: bug report format change

2004-08-22 Thread Erik Sandberg
On Sunday 22 August 2004 13.28, Han-Wen Nienhuys wrote: > Hi Eric, > > the bug collection has gotten rather large, and difficult for me to > get an overview of. To help things, I'm adding a .ly -> .tely -> .texi > -> conversion and a GNUmakefile, so I can get a neat .HTML with > images, containing

bug report format change

2004-08-22 Thread Han-Wen Nienhuys
Hi Eric, the bug collection has gotten rather large, and difficult for me to get an overview of. To help things, I'm adding a .ly -> .tely -> .texi -> conversion and a GNUmakefile, so I can get a neat .HTML with images, containing the status of all bugs. To make this feasible, the syntax of a lo

bug: old-relative.ly

2004-08-22 Thread Han-Wen Nienhuys
"The following gives no warning (it should; the first set-option is superfluous. The problem occurs often in reality, through \include)" } I disagree. Not a bug, won't fix. -- Han-Wen Nienhuys | [EMAIL PROTECTED] | http://www.xs4all.nl/~hanwen

Adding files to make

2004-08-22 Thread Han-Wen Nienhuys
[EMAIL PROTECTED] writes: > I'm trying to create a Fret_diagram_engraver. To do so, I am creating > the file fret-diagram-engraver.cc. > > How do I get the .cc file added to the make file? > > I'm not familiar with autoconf. I have grep'ed around looking for the > names of existing engravers. T