regression introduced with issue 5122 "Fix not scaling stem in note-by-number-markup"

2017-06-12 Thread Thomas Morley
As of https://sourceforge.net/p/testlilyissues/issues/5122/#99dc commit eee677c480c78d58a5215e246575aa94ba2d1897 introduced a regression. Not sure when I have the time to look deeper into it. At first sight I've no good idea for a proper fix. So I suggest to revert it. At least it should not go

Re: lilypond-manuals.css: edit color scheme and some spacing (issue 322070043 by paulwmor...@gmail.com)

2017-06-12 Thread Paul
On 06/12/2017 06:24 AM, fedel...@gmail.com wrote: I like a lot the new color scheme! More elegant and easier for the eyes. Thanks, glad you like it! ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypo

Re: lilypond-manuals.css: edit color scheme and some spacing

2017-06-12 Thread Paul
On 06/12/2017 03:02 PM, Flaming Hakama by Elaine wrote: CSS is happy with both properties set: width as a percentage and min-width as an absolute value. There is no conflict and they should work together well. Hi, yes, thanks, but... I glossed over the details. If you look at the css file y

Re: lilypond-manuals.css: edit color scheme and some spacing

2017-06-12 Thread Flaming Hakama by Elaine
> > I feel like the table of contents bar at the left is too wide. >> > > I agree; it can get a bit wide especially on wider monitors/windows. > (Note I have not changed its width in this patch.) Currently the size is a > percentage of the window width. We could make that smaller, but at the > ri

Re: lilypond-manuals.css: edit color scheme and some spacing (issue 322070043 by paulwmor...@gmail.com)

2017-06-12 Thread Paul
On 06/10/2017 07:30 PM, carl.d.soren...@gmail.com wrote: I don't feel strongly about the old design being bad. What got me motivated to work on it was the bright (fully saturated) colored borders around the code blocks, which I found distracting. The new design looks mostly fine to me. G

Re: Add on-page-greater-than, -less-than (on-the-fly) (issue 74540044)

2017-06-12 Thread dak
On 2017/06/10 19:36:30, pwm wrote: That's a nice consistency. I tried it out and the following works too: #(define (onpage proc nmbr) (markup-when ((page:page-number -1)) (proc page:page-number nmbr))) \paper { #(set-paper-size "a7landscape") oddFooterMarkup = \markup \on-the

Re: Initial work to support opentype font features (issue 323850043 by horndud...@gmail.com)

2017-06-12 Thread trueroad
On 2017/06/05 05:01:28, horndude77 wrote: Update minimum pango version If I understand correctly, LilyDev 4.1 cannot compile this patch. In my humble opinion, it is necessary that LilyDev 4.1 can compile it. I want to hear the opinions of LilyDev 4.1 users. If it is necessary, shall I create

Re: lilypond-manuals.css: edit color scheme and some spacing (issue 322070043 by paulwmor...@gmail.com)

2017-06-12 Thread fedelogy
I like a lot the new color scheme! More elegant and easier for the eyes. https://codereview.appspot.com/322070043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Create engravers for merging rests (issue 321930043 by horndud...@gmail.com)

2017-06-12 Thread dak
https://codereview.appspot.com/321930043/diff/160001/Documentation/notation/simultaneous.itely File Documentation/notation/simultaneous.itely (right): https://codereview.appspot.com/321930043/diff/160001/Documentation/notation/simultaneous.itely#newcode917 Documentation/notation/simultaneous.ite

Re: Create engravers for merging rests (issue 321930043 by horndud...@gmail.com)

2017-06-12 Thread thomasmorley65
One nit. See below. No need for a new patch-set, imho. You could change it right before pushing. Otherwise LGTM https://codereview.appspot.com/321930043/diff/160001/Documentation/notation/simultaneous.itely File Documentation/notation/simultaneous.itely (right): https://codereview.appspot.com/