Re: Manual File Problem

Richard S Dougall wrote: > > I have download the file > > lilypond.ps.gz > > which is suppose to be a gnu-zipped file. When I try to > unzip this with gunzip on the Univ. of Pittsburgh's unix > system, it tells me that this file is not a gzip file or > some similar messages. [...] > Do you hav

no flags replace broken beam

Hello, thank you for providing such a great tool as lilypond for free. The following behaviour in lilypond 1.6.7 is probably not intentional. If a line break is forced between two notes that are connected by a automatically generated beam, no flags replace the beam. Here is an example: melodi

Re: no flags replace broken beam

Mats Bengtsson wrote: > The automatic breaking of beams currently only takes the relative timing > within the current bar into account, see > http://lilypond.org/stable/Documentation/user/out-www/lilypond/Setting-automatic-beam-behavior.html > I dare say that your example is fairly non-standard.

Re: lilypond-1.8.0 d'ont compile

On Mon, 18 Aug 2003 05:23:34 -0700, Edmundo Marcelo Navarrete wrote: > I am runnning SuSE-8.2 , gcc-3.3 (from SuSE) guile-1.6.4 (tarball) and > flex-2.5.31 (tarball).- > 1) ./configure is OK > 2) the out oF "make all" is: [...] > libc-extension.cc: In function `int snprintf(char*, unsigned int, co

Re: lilypond-1.8.0 d'ont compile

On Mon, 18 Aug 2003 05:23:34 -0700, Edmundo Marcelo Navarrete wrote: > I am runnning SuSE-8.2 , gcc-3.3 (from SuSE) guile-1.6.4 (tarball) and > flex-2.5.31 (tarball).- > 1) ./configure is OK > 2) the out oF "make all" is: [...] > libc-extension.cc: In function `int snprintf(char*, unsigned int, co

stanza numbers and rest

Hello, I'm not sure whether this is a bug or an (undocumented) feature. If a song starts with a rest, the stanza numbers (or name of singers) are not printed. The following example shows it: \score { \addlyrics \notes \relative c'' \context Voice = duet { \time 3/4 r4 g4

Re: stanza numbers and rest

Mats Bengtsson wrote: > I definitely would call it a bug. A workaround is described in > http://mail.gnu.org/archive/html/lilypond-user/2003-05/msg00216.html > (and the earlier emails of the same thread). Oh sh.., now I remember this thread. Anyway, your suggestions didn't help in my case: \

Re: lilypond-1.8.0 d'ont compile

On Mon, Sep 22, 2003 at 02:51:03PM +0200, Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: > > > > I get the same error with SuSE-8.2 and lilypond 1.8.1. > > > > If I'm right, the problem is that the configure script concludes that > > snprintf is not provided by stdio.h although it is. If I

Re: noncritical: ftp.lilypond.org symlinks

Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: >> Hello, >> just wanted to note that the symlink >> stable still points to v1.6, and development to v1.7. > > thanks. Fixed. The symlink "stable" probably needs again an update ;-) Thomas P.S.: Thanks for the new version. -- aaa := ira _

noncritical: wrong directory for web-install

Hello, if you try "make web-install" the install process looks in the wrong directory for web.tar.gz. More precisely, the directory should be "out-www" instead of $(outdir). Workaround: unpack the archive out-www/web.tar.gz yourself in the desired directory Greetings Thomas _

\mark \default not working in 2.0.0

Hello, (at least) in 2.0.0, the default rehearsal mark does not work as expected. The first time you use "\mark \default" nothing is printed. The second time a large "1" is shown, and so on. See the regression test rehearsal-mark.ly for an example. Greetings Thomas

lily 2.0.0 crash (non-critical)

Hello, lilypond 2.0.0 (own compilation on SuSE Linux 8.2) kindly asks me to send my file to this list, because it crashes with signal 11. The funny thing about this problem is that it vanishes, if you change something non-trivial like using "--verbose", remove the midi part or delete a lyrics ex

Re: lily 2.0.0 crash (non-critical)

Han-Wen Nienhuys wrote: > [EMAIL PROTECTED] writes: >> Hello, >> >> lilypond 2.0.0 (own compilation on SuSE Linux 8.2) kindly asks me to >> send my file to this list, because it crashes with signal 11. The funny >> thing about this problem is that it vanishes, if you change something >> non-trivi

Re: lily 2.0.0 crash (non-critical)

Han-Wen Nienhuys wrote: > > Try this patch (or try CVS) This fixes the problem. Thanks for the fast response time! Thomas ___ Bug-lilypond mailing list [EMAIL PROTECTED] http://mail.gnu.org/mailman/listinfo/bug-lilypond

cmss14.pfa

Hello, lilypond 2.0.0 uses the font cmss14 for chord names in paper26.ly. In my tex environment (tetex 2.0.1, SuSE linux 8.2) this font is not included as type1 font (only 8,9,10,12,17). Lilypond provides cmss sized 5,6, and 7. Hence, the chord names are included with a bitmapped font. If the sa