build logging: Improve METAFONT tracing. (issue 554810043 by lemzw...@googlemail.com)
LGTM. I love the comments helping to understand .metafont parameters. https://codereview.appspot.com/554810043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Fw: [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin
Found the original message ...
Trevor
-- Forwarded Message --
From: "Jean Abou Samra"
To: "[testlilyissues:issues] "
<4...@issues.testlilyissues.p.re.sourceforge.net>
Sent: 14/07/2019 21:07:26
Subject: [testlilyissues:issues] #4975 [Windows] Grace notes cause staff
to protrude into the margin
Also reported on Mac OS (at least 10.12.6 Sierra [me] and 10.13.6 High Sierra
[Michael Hendry]) with LilyPond 2.21.0, but _not_ LilyPond 2.19.83, quite
surprisingly as the bug appeared with 2.19.19 on Windows. Both above examples
are reproduced, and I can add a third one:
```
\version "2.21.0"
\relative {
c'1
\acciaccatura { bes8 } c1
}
```
Full outputs and logs on the three examples using 2.21.0, 2.19.83 and 2.18.2
are available in the attached archive.
Two additional remarks:
* On the first example, "mis-predicted force" programming errors show up, and
yet the output is perfectly normal, the staff doesn't protrude.
* On the last example, the bug is triggered as soon as the grace note is
altered, no matter the alteration and no matter wether \acciaccatura or \grace
is used.
Hope that helps!
---
** [issues:#4975] [Windows] Grace notes cause staff to protrude into the
margin**
**Status:** Started
**Created:** Sun Sep 18, 2016 11:07 PM UTC by Simon Albrecht
**Last Updated:** Sun Jul 14, 2019 07:23 PM UTC
**Owner:** Phil Holmes
http://lilypond.1069038.n5.nabble.com/Grace-notes-and-staff-miss-alignment-tp181529p188186.html
As reported by Karol and confirmed by Pierre, this code
:::TeX
\version "2.19.48"
\transpose c c' {
\repeat unfold 16 { e'8 a }
R1*8
}
\transpose c c' {
\repeat unfold 16 { \grace dis'8 e' \grace gis8 a }
R1*8
}
under Windows (at least 7 and 8) causes lots of `programming error:
mis-predicted force` and has the last staff flow into the margin.
Output at
The first bad version is 2.19.19.
---
Sent from sourceforge.net because you indicated interest in
Fw: [testlilyissues:issues] Moderation action required
Forwarding on behalf of Jean Abou Samra as I deleted the message in
SourceForge by mistake :( I don't know what the original subject line
was, and the attachment is lost. Sorry! Perhaps Jean could resubmit.
Trevor
-- Forwarded Message --
From: "Jean Abou Samra"
To: nore...@sourceforge.net
Sent: 14/07/2019 20:23:46
Subject: [testlilyissues:issues] Moderation action required
The following submission requires approval at
https://sourceforge.net/p/testlilyissues/issues/_discuss/moderate before it can
be approved for posting:'t
Also reported on Mac OS (at least 10.12.6 Sierra [me] and 10.13.6 High Sierra
[Michael Hendry]) with LilyPond 2.21.0, but _not_ LilyPond 2.19.83, quite
surprisingly as the bug appeared with 2.19.19 on Windows. Both above examples
are reproduced, and I can add a third one:
```
\version "2.21.0"
\relative {
c'1
\acciaccatura { bes8 } c1
}
```
Full outputs and logs on the three examples using 2.21.0, 2.19.83 and 2.18.2
are available in the attached archive.
Two additional remarks:
* On the first example, "mis-predicted force" programming errors show up, and
yet the output is perfectly normal, the staff doesn't protrude.
* On the last example, the bug is triggered as soon as the grace note is
altered, no matter the alteration and no matter wether \acciaccatura or \grace
is used.
Hope that helps!
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New function css-color (issue 580780043 by g...@ursliska.de)
Thank you for doing so. The thing is (as buried in a comment somewhere), these regular reminders served as an incentive for me not to forget that I wanted to push this only after documenting the new feature... ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCHES - Countdown for July 14th
Hello, Here is the current patch countdown list. The next countdown will be on July 16th A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ Push: 5303 layout-set-staff-space confuses chord note head placement in a certain situation - James Lowe https://sourceforge.net/p/testlilyissues/issues/5303 http://codereview.appspot.com/570830043 Countdown: 5533 Add tex/txi-pt.tex - Knut Petersen https://sourceforge.net/p/testlilyissues/issues/5533 http://codereview.appspot.com/562920043 5532 \ottava doesn’t confuse ambitus - Malte Meyn https://sourceforge.net/p/testlilyissues/issues/5532 http://codereview.appspot.com/580890043 Review: 5535 build logging: Improve METAFONT tracing. - Werner LEMBERG https://sourceforge.net/p/testlilyissues/issues/5535 http://codereview.appspot.com/554810043 5534 Improve content of tree.gittxt - Knut Petersen https://sourceforge.net/p/testlilyissues/issues/5534 http://codereview.appspot.com/564990043 New: No new patches at this time. *** Regards, James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: NR: 2.10 Arabic Music - inlcude references to hel-arabic.ly (issue 560790043 by pkxgnugi...@runbox.com)
~~~ NR: 2.10 Arabic Music - inlcude references to hel-arabic.ly staging author Hassan Elfatihi Sun, 30 Jun 2019 10:49:45 +0100 (10:49 +0100) committer James Lowe Sun, 14 Jul 2019 13:22:41 +0100 (13:22 +0100) commit c24f83991b772a65c15b6290cf70d725def117bd ~~~ Hassan did comment on the example used, but I will deal with that in a separate patch. Closing this one. https://codereview.appspot.com/560790043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: New function css-color (issue 580780043 by g...@ursliska.de)
This was stuck as 'please push' for weeks. I have retested the patch today and am pushing it on Ur's behalf - seems a shame to waste the work otherwise. ~~~ Enhancement - New function css-color staging author Urs Liska Sun, 14 Jul 2019 13:16:17 +0100 (13:16 +0100) committer James Lowe Sun, 14 Jul 2019 13:19:19 +0100 (13:19 +0100) commit a5e0b01b0c8251cf0244e05467938b813fc8fa0a ~~~ https://codereview.appspot.com/580780043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Use new syntax throughout the doc and examples (issue 572640043 by v.villen...@gmail.com)
This was stuck as 'please push' for weeks. I have retested the patch today and am pushing it on VV's behalf - seems a shame to waste the work otherwise. Doc: Use new syntax throughout all doc and examples staging author Valentin Villenave Sun, 14 Jul 2019 13:02:02 +0100 (13:02 +0100) committer James Lowe Sun, 14 Jul 2019 13:07:17 +0100 (13:07 +0100) commit 47f74e11cfdf3f7dfa54ca0b1d009da770d6aef5 https://codereview.appspot.com/572640043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Improve content of tree.gittxt (issue 564990043 by knup...@gmail.com)
>> What I would like to see for such branches is the ID of the commit >> where the branch is rooted in master, this is, if we have >> >> o---o---o branch >> / >> o---o---o---o---o master >> 0 1 2 3 4 >> >> I want to see ID 2 in this file, marked as the root of `branch'. > > So you ask for the equivalent of the output of the following script? I think so, yes — thanks! Not sure if everyone considers this useful, though... Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Improve content of tree.gittxt (issue 564990043 by knup...@gmail.com)
What I would like to see for such branches is the ID of the commit where the branch is rooted in master, this is, if we have o---o---o branch / o---o---o---o---o master 0 1 2 3 4 I want to see ID 2 in this file, marked as the root of `branch'. So you ask for the equivalent of the output of the following script? #!/bin/bash BR=`LANG=c git branch | grep "^\*" | sed -e "s|^* *||"` HD=`git rev-parse --verify HEAD` FP=`git merge-base --octopus master HEAD` echo "BRANCH: $BR" echo " HEAD: $HD" if [ ! -z $FP ]; then echo "MERGE_BASE: $FP" echo -e '\n HISTORY:\n \n'; git log --pretty=format:" HASH: %H%n SUBJECT: %s%n" $FP~1..HEAD | cat fi https://codereview.appspot.com/564990043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
