Re: About lilypond's build problem with debian
Han-Wen Nienhuys [EMAIL PROTECTED] writes: Thomas Bushnell BSG schreef: I'm distressed that nobody has bothered to fix the bug since then. In the thread on the mailing list you can see that if LILYPONDPREFIX is set correctly, the bug goes away. This issue has been addressed in a more robust manner in the 2.9 series, and I would welcome a backport of the changes; we haven't found the time to do it. Good to hear. I think for Debian's purposes, setting LILYPONDPREFIX properly is probably the simplest solution. I look forward to 2.10 having a bettr fix in place. Thomas ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: About lilypond's build problem with debian
On Tue, Jul 25, 2006 at 02:08:03AM -0700, Thomas Bushnell BSG wrote: Han-Wen Nienhuys [EMAIL PROTECTED] writes: Thomas Bushnell BSG schreef: I'm distressed that nobody has bothered to fix the bug since then. In the thread on the mailing list you can see that if LILYPONDPREFIX is set correctly, the bug goes away. This issue has been addressed in a more robust manner in the 2.9 series, and I would welcome a backport of the changes; we haven't found the time to do it. Good to hear. I think for Debian's purposes, setting LILYPONDPREFIX properly is probably the simplest solution. I look forward to 2.10 having a bettr fix in place. It doesn't work in 2.9 series, I have tested tomorrow. Actually, the only one solution that I found is to make an symbolic link of pythons scripts in python/ - scripts/ When I did that, the bug seems to go away, and help2man seem to make correctly his job. There is a problem for scripts in scripts/ for finding files in python, and when I put them in the same directory, the problem goes away. I think there is a problem again, the new implementation of LILYPONDPREFIX in 2.9 series doesn't seem to correct the problem. -- .---. Ludovic RESLINGER / \ [EMAIL PROTECTED]@./ Trumpet Student in CNR /`\_/`\ Free Software Developer // )X( \\ | \ : )|_ _,'| .''`. /`\_` _/ \ @==TTT=::_ | : :' : \__/'---'\__/ ((_=HHH___)) `.| `. `'` `---UUU---'= `- signature.asc Description: Digital signature ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: About lilypond's build problem with debian
Thomas Bushnell BSG schreef: The problem is that lilypond's build system assumes that lilypond is already installed on the system. Han-Wen Nienhuys said no, it uses LILYPONDPREFIX, but as I point out in the thread, it is setting LILYPONDPREFIX *incorrectly*, and the reason the builds are working for Han-Wen is that he already has lilypond installed. this is false BTW, as I don't have lilypond installed at all. I always run from the development tree. I would welcome a usable bugreport about this, as Ludovic has so far declined to produce one. -- Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen LilyPond Software Design -- Code for Music Notation http://www.lilypond-design.com ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bug or Feature?
Alle 21:02, mercoledì 19 luglio 2006, hai scritto:
Please read the section on Automatic accidentals in the manual.
/Mats
modern
This rule corresponds to the common practice in the 20th century. This rule
prints the same accidentals as default, but temporary accidentals also are
canceled in other octaves. Furthermore, in the same octave, they also get
canceled in the following measure
I already red it, and I think this behaviour is not correct. When playing you
feel stronger the sharp in the same measure than the unsharp of the previous
one. The previous one unsharp should not override the diesis in the same
measure don't you think?
Anyway the problem is still more annoying, this happens also if the first note
is measures far away...
\version 2.8.0
\score {
\new Staff {
\relative c' {
#(set-accidental-style 'modern)
\clef bass
\partial 4
c |
g a g f |
e f g a |
b a g a |
cis,, cis' c' c,
}
}
}
___
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: page breaking (again)
Joe Neeman [EMAIL PROTECTED] writes: Here is my latest patch to add a new page-breaker. May you not abbreviate that much variable names in scheme code? It's usual to write full names, eg. paper-book and page-number, iso. p-book and p-num. nicolas ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: About lilypond's build problem with debian
Re, I have found why it builed for you and not on my system. The python version installed on my system was a 2.4 version. I had backported on a 2.3 version, and the problem seem solved. It will be interesting to know why there is this problem with new versions of python, because if one day Python is 2.4 by default, the bug could be a problem to build. I don't know if it is a problem of Debian Package or if it is a general problem of python 2.4. I will test more... So, for Thomas BUSHNELL: I don't know if it is really a good idea to wait Python 2.4 by default to release lilypond in debian :) I hope that you will be satisfy of my report, this time :). -- .---. Ludovic RESLINGER / \ [EMAIL PROTECTED]@./ Trumpet Student in CNR /`\_/`\ Free Software Developer // )X( \\ | \ : )|_ _,'| .''`. /`\_` _/ \ @==TTT=::_ | : :' : \__/'---'\__/ ((_=HHH___)) `.| `. `'` `---UUU---'= `- signature.asc Description: Digital signature ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: page breaking (again)
On Tue, 2006-07-25 at 16:43 +0200, Nicolas Sceaux wrote: Joe Neeman [EMAIL PROTECTED] writes: Here is my latest patch to add a new page-breaker. May you not abbreviate that much variable names in scheme code? It's usual to write full names, eg. paper-book and page-number, iso. p-book and p-num. OK, fixed. Joe ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: About lilypond's build problem with debian
Han-Wen Nienhuys [EMAIL PROTECTED] writes: Thomas Bushnell BSG schreef: The problem is that lilypond's build system assumes that lilypond is already installed on the system. Han-Wen Nienhuys said no, it uses LILYPONDPREFIX, but as I point out in the thread, it is setting LILYPONDPREFIX *incorrectly*, and the reason the builds are working for Han-Wen is that he already has lilypond installed. this is false BTW, as I don't have lilypond installed at all. I always run from the development tree. On April 27 I submitted a bug report for 2.8.1, and explained the fix that solves the problem. I have no idea about 2.9 and what changes you say have been made there. Thomas ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: No Bug nor Feature?
On Tue, 25 Jul 2006 16:36:17 +0200 Marco Gusy [EMAIL PROTECTED] wrote: I already red it, and I think this behaviour is not correct. When playing you feel stronger the sharp in the same measure than the unsharp of the previous one. The previous one unsharp should not override the diesis in the same measure don't you think? Anyway the problem is still more annoying, this happens also if the first note is measures far away... Don't be annoyed, you can get your money back if you want;-) Music-notation is annoying anyway you look at it and demands a great effort on the behalf of the writer (even with pen and paper, which I used for 20 years or more.) Well, try to live with it, use ! or something like that to explicit specify accidentals. Good luck and happy writing, /Donald Axel -- http://d-axel.dk/ -- Donald Axel, Consultant -- [EMAIL PROTECTED] ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Bug or Feature?
On Tue, 2006-07-25 at 16:36 +0200, Marco Gusy wrote: Alle 21:02, mercoledì 19 luglio 2006, hai scritto: Please read the section on Automatic accidentals in the manual. /Mats modern This rule corresponds to the common practice in the 20th century. This rule prints the same accidentals as default, but temporary accidentals also are canceled in other octaves. I may be reading the documentation wrong, but to me this suggests that there _should_ be a natural on the high C (as Marco says). Are the docs wrong, is the implementation wrong or am I reading it wrong? ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
using new fall and doit features in 2.9.13
Can someone tell me how to use the new fall and doit features. I guessed incorrectly \fall and \doit. TIA, Paul Scott ___ lilypond-devel mailing list lilypond-devel@gnu.org http://lists.gnu.org/mailman/listinfo/lilypond-devel
