[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2020-02-06 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
It seems that Issue 5725 (and Issue 4943) has fixed this issue in LilyPond 2.19.84. Here is the results of my experiment on Windows 10 1909 (64 bit). * lilypond-2.19.83-1.mingw.exe from lilypond.org + https://sourceforge.net/p/testlilyissues/issues/4975/ - reproduced (programming erro

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2020-01-29 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
The cause of this issue and Issue 4943 seems to be the same. I've tried `x87mant53.dll` showed in the german forum. https://lilypondforum.de/index.php/topic,609.msg3443.html#msg3443 It solved not only Issue 4943 but also Issue 4975. I guess that these issues do not only occur on Windows, but on al

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2019-11-17 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
Interesting that the bug occurs on all major platforms except GNU/Linux. Actually it's a chance that it is present on Mac OS because in theory you can compile LilyPond natively on a Mac. Unfortunately I'm no longer using a Mac and anyway my compilation attempts were all unsucessful at the time a

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2019-11-16 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
Here's another MWE. This gives mis-directed force messages without affecting the layout. As with Jean's example, it makes no difference if \grace, \appoggiatura or \acciaccatura are used. But it does make a difference if the staff size is changed. This example gives different numbers of errors

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2019-07-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto
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"

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2016-11-19 Thread Auto mailings of changes to Lily Issues
Another example reported by Ralph: :::TeX \version "2.19.40" \include "english.ly" tune = \relative c'' { \clef treble \key a \minor \time 6/8 e8 a a a4 \key a \major e8 | \acciaccatura b'8 a8 gs a a, cs e | } \score { \tune } --- ** [issues:#4975] [Windows] Grac

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2016-10-22 Thread Auto mailings of changes to Lily Issues
>From what I understand, we do know which commit is the culprit but we don't >know which files from this commit are responsible for the issue (i.e. >reverting which files fixes the issue). There are 140 files changed in this >commit, so reverting them one by one would be a time consuming process

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2016-10-01 Thread Auto mailings of changes to Lily Issues
If I understand correctly, it is not a compiler problem. First, I've tried some other environment on Windows 10 64bit. lilypond-2.19.46-1.mingw.exe (from lilypond.org): Reproduced. Cygwin 64 bit + lilypond-2.19.42 (from cygwin package): No problem. Cygwin 32 bit + lilypond-2.19.42 (from cy

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2016-09-30 Thread Auto mailings of changes to Lily Issues
The bug still exists with lily-guile-macros.hh manually reverted to its previous state. The config.log and config.hh are attached - please let me know if this doesn't work for downloading them and I'll email them over. Attachments: - [config.tar.gz](https://sourceforge.net/p/testlilyissues/i

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2016-09-29 Thread Auto mailings of changes to Lily Issues
Ok, so I reviewed all of the commit. There are few changes which are not strictly equivalent (but should be functionally equivalent), and If I remember correctly, most of them were likely proposed by me during review. Cough cough. However, pretty much all of them should not be in code triggere

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2016-09-29 Thread Auto mailings of changes to Lily Issues
OK - I've compiled a windows binary with just the single line "if (p == ly_symbol2scm ("force"))" restored (see the git branch dev/philh) and this does not fix the grace note/line length bug. So there is something deeper at work with that commit. --- ** [issues:#4975] [Windows] Grace notes c

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2016-09-28 Thread Auto mailings of changes to Lily Issues
Please really check that reverting only the change in `lily/simple-spacer.cc` is sufficient for removing the problem. Because if it is, we have a far larger problem either involving a fundamental Guile bug or a GCC compiler bug: the change in `simple-spacer.cc` is just diff --git a/lily/si

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2016-09-28 Thread Auto mailings of changes to Lily Issues
- **status**: Accepted --> Started - **assigned_to**: Phil Holmes - **Comment**: OK - I've spent quite a lot of the last week tracking this down. Short summary: commit e0af94bb8939bc6f4998db6294010baa77139092 (Replace C++ (in)equality checks with proper SCM syntax) is definitely the culprit. I

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2016-09-19 Thread Auto mailings of changes to Lily Issues
Later versions throw an assertion pointing to simple-spanner.cc. This file was edited in commit http://git.savannah.gnu.org/cgit/lilypond.git/commit/lily/simple-spacer.cc?id=e0af94bb8939bc6f4998db6294010baa77139092 which looks far more likely to the culprit. Can anyone who understands this st

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4975 [Windows] Grace notes cause staff to protrude into the margin

2016-09-18 Thread Auto mailings of changes to Lily Issues
--- ** [issues:#4975] [Windows] Grace notes cause staff to protrude into the margin** **Status:** Accepted **Created:** Sun Sep 18, 2016 11:07 PM UTC by Simon Albrecht **Last Updated:** Sun Sep 18, 2016 11:07 PM UTC **Owner:** nobody http://lilypond.1069038.n5.nabble.com/Grace-notes-and-sta