with point-stencil NoteHead and slur certain textscripts can't be written

2013-07-01 Thread Eluze
with version 2.17.21 the code: { \override NoteHead #'stencil = #point-stencil c'2.-po ( b8 a )-- g1- } produces: This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information. terminate called after

Re: robots.txt in git and online are not the same

2013-07-01 Thread Phil Holmes
- Original Message - From: Mark Polesky markpole...@yahoo.com To: Phil Holmes m...@philholmes.net; bug-lilypond@gnu.org Sent: Sunday, June 30, 2013 10:45 PM Subject: Re: robots.txt in git and online are not the same Sorry, I'm having trouble with my email client. My last post got

Markup in \tempo Is Broken with Lilypond 2.17.21

2013-07-01 Thread Russell Cook
\version 2.17.21 \score { \new Voice { \time 4/4 \tempo \markup { Rubato \concat { \smaller \general-align #Y #DOWN \note #4 #1 \medium = ca. 76 } } s1 * 4 } } Prior to version 2.17.21, the above code compiled without issues. As of 2.17.21, it only compiles if the string between the

Re: Markup in \tempo Is Broken with Lilypond 2.17.21

2013-07-01 Thread David Kastrup
Russell Cook astrop...@gmail.com writes: \version 2.17.21 \score { \new Voice { \time 4/4 \tempo \markup { Rubato \concat { \smaller \general-align #Y #DOWN \note #4 #1 \medium = ca. 76 } } s1 * 4 } } Prior to version 2.17.21, the above code compiled without issues. As of

Re: Markup in \tempo Is Broken with Lilypond 2.17.21

2013-07-01 Thread David Kastrup
Phil Holmes m...@philholmes.net writes: Russell Cook astrop...@gmail.com wrote in message news:loom.20130701t180125-...@post.gmane.org... \version 2.17.21 \score { \new Voice { \time 4/4 \tempo \markup { Rubato \concat { \smaller \general-align #Y #DOWN \note #4 #1 \medium = ca. 76 } }

another out-of-memory

2013-07-01 Thread Keith OHara
Another case that eats memory on Windows came up in the verification test for issue 2910. There was no problem on Linux, and small changes avoid the problem on Windows. I have not been able to minimize smaller than: {a'^This text is placed very close to the note c^This text is padded away

Re: Markup in \tempo Is Broken with Lilypond 2.17.21

2013-07-01 Thread Russell Cook
Phil Holmes mail at philholmes.net writes: Thanks for the report. On my Windows box, the even-much-more-tiny example below has the same effect: { \tempo \markup { 123 } s1 } Oops! I thought I tested a small \markup string alone, so thank you for pointing that out. – Russell

Re: Markup in \tempo Is Broken with Lilypond 2.17.21

2013-07-01 Thread David Kastrup
David Kastrup d...@gnu.org writes: Russell Cook astrop...@gmail.com writes: \version 2.17.21 \score { \new Voice { \time 4/4 \tempo \markup { Rubato \concat { \smaller \general-align #Y #DOWN \note #4 #1 \medium = ca. 76 } } s1 * 4 } } Prior to version 2.17.21, the above code

Re: another out-of-memory

2013-07-01 Thread David Kastrup
Keith OHara k-ohara5...@oco.net writes: Another case that eats memory on Windows came up in the verification test for issue 2910. There was no problem on Linux, and small changes avoid the problem on Windows. I have not been able to minimize smaller than: {a'^This text is placed very

Broken x-refs in translated docs

2013-07-01 Thread Jean-Charles Malahieude
Most of the cross-references between manuals are broken in the translated documentation, split version. I'm not able to work on this, but here is what I've diagnosed: For instance, in LM 2.1.2 Accidentals and key signatures in French from

Re: Markup in \tempo Is Broken with Lilypond 2.17.21

2013-07-01 Thread Thomas Scharkowski
{ \tempo \markup { 123 } s1 } Works fine on my just-compiled version on GNU/Linux using g++ 4.7.3. What version are the GUB-generated binaries compiled with? Can we get feedback about the MacOSX and/or the precompiled Linux and/or FreeBSD (?) or other versions? Works fine here with a

Re: another out-of-memory

2013-07-01 Thread Thomas Morley
2013/7/1 David Kastrup d...@gnu.org: Keith OHara k-ohara5...@oco.net writes: Another case that eats memory on Windows came up in the verification test for issue 2910. There was no problem on Linux, and small changes avoid the problem on Windows. I have not been able to minimize smaller

Re: Markup in \tempo Is Broken with Lilypond 2.17.21

2013-07-01 Thread Thomas Morley
2013/7/1 David Kastrup d...@gnu.org: David Kastrup d...@gnu.org writes: Russell Cook astrop...@gmail.com writes: \version 2.17.21 \score { \new Voice { \time 4/4 \tempo \markup { Rubato \concat { \smaller \general-align #Y #DOWN \note #4 #1 \medium = ca. 76 } } s1 * 4 } } Prior

Re: Markup in \tempo Is Broken with Lilypond 2.17.21

2013-07-01 Thread Phil Holmes
Thomas Morley thomasmorle...@gmail.com wrote in message news:CABsfGyWptjDX2DZY4amOwpZNebHec0_CvWboRvE8Hz=tqfp...@mail.gmail.com... 2013/7/1 David Kastrup d...@gnu.org: David Kastrup d...@gnu.org writes: Russell Cook astrop...@gmail.com writes: \version 2.17.21 \score { \new Voice {

Re: Broken x-refs in translated docs

2013-07-01 Thread Phil Holmes
Jean-Charles Malahieude lily...@orange.fr wrote in message news:51d1c959.4010...@orange.fr... Most of the cross-references between manuals are broken in the translated documentation, split version. Do you think this is a new 2.17.21 problem, or has it been around a while? -- Phil Holmes Bug

Re: Broken x-refs in translated docs

2013-07-01 Thread Federico Bruni
2013/7/1 Phil Holmes m...@philholmes.net Jean-Charles Malahieude lily...@orange.fr wrote in message news:51D1C959.4010108@orange.**fr... Most of the cross-references between manuals are broken in the translated documentation, split version. Do you think this is a new 2.17.21 problem, or

bug: \global section does not tolerate spacer rests

2013-07-01 Thread Karol Majewski
Hi, In 2.17.21 \global section does not tolerate spacer rests. That's why the following snippet won't compile: http://www.lilypond.org/doc/v2.17/Documentation/learning/solo-verse-and-two_002dpart-refrain I got: terminate called after throwing an instance of 'std::bad_alloc' what():

Re: bug: \global section does not tolerate spacer rests

2013-07-01 Thread Federico Bruni
2013/7/1 Karol Majewski karol.majew...@gmail.com Hi, In 2.17.21 \global section does not tolerate spacer rests. That's why the following snippet won't compile: http://www.lilypond.org/doc/v2.17/Documentation/learning/solo-verse-and-two_002dpart-refrain I got: terminate called after

Re: [translations] Broken x-refs in translated docs

2013-07-01 Thread Federico Bruni
2013/7/1 Jean-Charles Malahieude lily...@orange.fr For instance, in LM 2.1.2 Accidentals and key signatures in French from http://lilypond.org/doc/v2.17/**Documentation/learning/**

Re: Markup in \tempo Is Broken with Lilypond 2.17.21

2013-07-01 Thread Russell Cook
The precompiled binaries for Mac OS X (x86) also typeset this music without issues. It looks like the Windows binaries are the problem children. – Russell ___ bug-lilypond mailing list bug-lilypond@gnu.org

Re: Markup in \tempo Is Broken with Lilypond 2.17.21

2013-07-01 Thread Keith OHara
Phil Holmes mail at philholmes.net writes: Thanks for the report. On my Windows box, the even-much-more-tiny example below has the same effect: I tried to reduce today's bugs a little further, and opened issue 3432: skylined text alongside a staff consumes all memory under Windows

Re: bug: \global section does not tolerate spacer rests

2013-07-01 Thread Federico Bruni
keep the list in Cc 2013/7/2 Karol Majewski karol.majew...@gmail.com Sorry, I didn't mention that I use Windoews. 2013/7/2 Federico Bruni fedel...@gmail.com 2013/7/1 Karol Majewski karol.majew...@gmail.com Hi, In 2.17.21 \global section does not tolerate spacer rests. That's why the