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

Patch counted down - please push. Knut, I'll push this for you. James https://codereview.appspot.com/276570043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

PATCHES: Countdown for December the 31st

Hello, Here is the current patch countdown list. The next countdown will be on December the 31st. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ __ Push: 4707 Doc: CG 5.7.1 (Documentation work) esp. build sub

Snippet 706: Generating custom flags

In the PDF version of the snippet above, the "fl" letters of "flag" are missing. I think this is probably because they are being converted to a ligatured glyph, and then not displaying. Anyone know how to prevent this from happening? ___ lilypond-d

Issue number in commit message (Fwd: [testlilyissues:issues] #4704 Improve beam count handling with subdivided beams)

Hi all, I've just pushed my patch for #4704, having reworked the branch to five discrete commits (removing detours but separating work on different files/tasks). However, I somehow managed to mix up the issue number in several commit messages, so only one commit out of the list quoted below featu

Re: Issue number in commit message (Fwd: [testlilyissues:issues] #4704 Improve beam count handling with subdivided beams)

Urs Liska writes: > Hi all, > > I've just pushed my patch for #4704, having reworked the branch to five > discrete commits (removing detours but separating work on different > files/tasks). > > However, I somehow managed to mix up the issue number in several commit > messages, so only one commit

Re: Change texi2html option order for fixing Japanese navigation bars (issue 281970043 by truer...@gmail.com)

I've uploaded Patch Set 3. It passes full make doc in my environment. https://codereview.appspot.com/281970043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Issue number in commit message (Fwd: [testlilyissues:issues] #4704 Improve beam count handling with subdivided beams)

Am 28.12.2015 um 16:33 schrieb David Kastrup: > Urs Liska writes: > >> Hi all, >> >> I've just pushed my patch for #4704, having reworked the branch to five >> discrete commits (removing detours but separating work on different >> files/tasks). >> >> However, I somehow managed to mix up the issu

Re: Snippet 706: Generating custom flags

> In the PDF version of the snippet above, the "fl" letters of "flag" are > missing. I think this is probably because they are being converted to a > ligatured glyph, and then not displaying. Anyone know how to prevent this > from happening? If I understand correctly, it is pdfTeX issue. In

Re: Improve note-by-number to deal better with flag-styles (issue 284000043 by thomasmorle...@gmail.com)

https://codereview.appspot.com/28443/diff/40001/scm/define-markup-commands.scm File scm/define-markup-commands.scm (right): https://codereview.appspot.com/28443/diff/40001/scm/define-markup-commands.scm#newcode3550 scm/define-markup-commands.scm:3550: @code{neomensural}. The latter two

git cl problem: Couldn’t create Allura issue

Hello, sorry, but I still don’t seem to get along with git cl. I just uploaded a patch and it went fine until: ~/lilypond-git (dev/doc)$ git cl upload origin/master Documentation/learning/common-notation.itely | 25 +++-- 1 file changed, 23 insertions(+), 2 d

Re: Confusing standard output

Harm and Paul, I’m sorry I’m slow to respond. I’m still busy with holiday activities. For what it’s worth, the patch in https://codereview.appspot.com/282890044/ does fix the problem I described. I’ll look at the Philomelos work and see if I can make sense of it. John > On Dec 26, 2015, at 9: