Re: Confusing standard output

2015-12-25 Thread Thomas Morley
2015-12-26 3:09 GMT+01:00 John Gourlay : > I’ve noticed that LilyPond 2.19.35 on some valid ly files produces standard > output meaningless to me. In addition to the standard output saying, > “Processing”, "Parsing”, etc., it outputs two copies of a long list that > starts “(list ‘abs-fontsize-m

Confusing standard output

2015-12-25 Thread John Gourlay
I’ve noticed that LilyPond 2.19.35 on some valid ly files produces standard output meaningless to me. In addition to the standard output saying, “Processing”, "Parsing”, etc., it outputs two copies of a long list that starts “(list ‘abs-fontsize-markup”. These lists appear if the input ly file c

Re: [testlilyissues:issues] Ticket 2314 discussion

2015-12-25 Thread David Kastrup
"pkx166h" writes: > - **Patch**: push --> countdown > - **Comment**: > > Hold on ... I was a bit premature (Too many mince pies I expect!). I very much hope that the mince pies don't have more tangible prematurity effects. -- David Kastrup ___ lilyp

PATCHES: Ho! Ho! Ho! for December the 28th

2015-12-25 Thread James Lowe
Season's Greetings! Here is the current patch countdown list. The next countdown will be on December the 28th. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ Cheers! __ Push: No Patches to push at this time.

Re: Dont emit \space glyph as empty page number (issue 276570043 by pkx1...@gmail.com)

2015-12-25 Thread pkx166h
Patch on countdown for December 28th. https://codereview.appspot.com/276570043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: scm/markup.scm comment out debugging code (issue 282890044 by paulwmor...@gmail.com)

2015-12-25 Thread James Lowe
Hello, On 25/12/15 08:00, d...@gnu.org wrote: > I don't see a corresponding issue tracker entry but it isn't really > necessary. Can you push this to staging right away? I don't see how > anybody could not desire this one-line fix as fast as possible. > > https://codereview.appspot.com/282890044

Re: scm/markup.scm comment out debugging code (issue 282890044 by paulwmor...@gmail.com)

2015-12-25 Thread dak
I don't see a corresponding issue tracker entry but it isn't really necessary. Can you push this to staging right away? I don't see how anybody could not desire this one-line fix as fast as possible. https://codereview.appspot.com/282890044/ ___ lily