[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5273 Replace number-or-markup? with integer-or-markup?
- **labels**: --> Fixed_2_21_0 - **status**: Started --> Fixed - **Patch**: push --> - **Type**: Enhancement --> Defect - **Comment**: commit 1a983e3cdfc8135ead527a5f32b674c8fca8fdb8 (HEAD -> pushed/issue-5273-integer-or-markup, origin/staging) Author: Dan EbleDate: Sat Feb 10 10:40:23 2018 -0500 Issue 5273: Replace number-or-markup? with integer-or-markup? Note that \finger 3.14 used to succeed because of gracious formatting code, even though the underlying 'digit property is supposed to hold an integer. \finger 22/7 used to segfault. Giving non-integer numbers to \mark and \rightHandFinger used to cause errors; now the message focuses on syntax rather than internals. --- ** [issues:#5273] Replace number-or-markup? with integer-or-markup?** **Status:** Fixed **Labels:** Fixed_2_21_0 **Created:** Sun Feb 11, 2018 01:24 PM UTC by Dan Eble **Last Updated:** Sun Feb 18, 2018 11:40 AM UTC **Owner:** Dan Eble Replace number-or-markup? with integer-or-markup? Note that \finger 3.14 used to succeed because of gracious formatting code, even though the underlying 'digit property is supposed to hold an integer. \finger 22/7 used to segfault. Giving non-integer numbers to \mark and \rightHandFinger used to cause errors; now the message focuses on syntax rather than internals. http://codereview.appspot.com/336550043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5275 Avoid duplicate rehearsal marks in regression tests
- Description has changed: Diff: - **Needs**: --> - **Type**: Enhancement --> Maintainability --- ** [issues:#5275] Avoid duplicate rehearsal marks in regression tests** **Status:** Started **Created:** Sun Feb 18, 2018 01:45 PM UTC by Dan Eble **Last Updated:** Sun Feb 18, 2018 01:45 PM UTC **Owner:** Dan Eble Avoid duplicate rehearsal marks in regression tests Having multiple marks with the same sequence number is something that LilyPond might reasonably warn about in a future version. I suppose LilyPond might reasonably warn about out-of-sequence marks, but I haven't gone that far with this. Let me know if you think I should. http://codereview.appspot.com/334510043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5275 Avoid duplicate rehearsal marks in regression tests
--- ** [issues:#5275] Avoid duplicate rehearsal marks in regression tests** **Status:** Started **Created:** Sun Feb 18, 2018 01:45 PM UTC by Dan Eble **Last Updated:** Sun Feb 18, 2018 01:45 PM UTC **Owner:** nobody Avoid duplicate rehearsal marks in regression tests Having multiple marks with the same sequence number is something that LilyPond might reasonably warn about in a future version. I suppose LilyPond might reasonably warn about out-of-sequence marks, but I haven't gone that far with this. Let me know if you think I should. http://codereview.appspot.com/334510043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5274 GSoC 2018: Two new project ideas
- **Patch**: countdown --> push - **Comment**: Patch counted down - please push --- ** [issues:#5274] GSoC 2018: Two new project ideas** **Status:** Started **Created:** Mon Feb 12, 2018 06:25 PM UTC by Urs Liska **Last Updated:** Thu Feb 15, 2018 10:29 PM UTC **Owner:** Urs Liska GSoC 2018: Two new project ideas Since Frescobaldi hasn't been accepted for 2018 (but GNU has) This commit adds two project suggestions that had been posted on the Frescobaldi GSoC page. GSoC 2018: Add system-by-system project idea GSoC 2018: Add MusicXML project idea http://codereview.appspot.com/337570043 --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto
[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1493 Problem with horizontal beams
- **labels**: --> Fixed_2_21_0 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: ~~~ issue #1493: Problem with horizontal beams staging author Torsten HämmerleMon, 5 Feb 2018 20:20:16 + (21:20 +0100) committer James Lowe Sat, 17 Feb 2018 18:38:49 + (18:38 +) commit 30a874a29b81dbb174a60d185fc3f28bba85604c ~~~ Thank you Torsten. --- ** [issues:#1493] Problem with horizontal beams** **Status:** Fixed **Labels:** Fixed_2_21_0 **Created:** Wed Jan 26, 2011 12:21 PM UTC by Anonymous **Last Updated:** Thu Feb 15, 2018 10:28 PM UTC **Owner:** Torsten Hämmerle **Attachments:** - [beams.ly](https://sourceforge.net/p/testlilyissues/issues/1493/attachment/beams.ly) (807 Bytes; application/octet-stream) - [screenshot.png](https://sourceforge.net/p/testlilyissues/issues/1493/attachment/screenshot.png) (18.9 kB; image/png) *Originally created by:* *anonymous *Originally created by:* [ralphbug...@gmail.com](http://code.google.com/u/106131861630194758622/) James Lowe : There seems to be an inconsistency with setting horizontal beams. We have a snippet where we state that \override Beam \#'damping = \#+inf.0 Should generate horizontal beams in all cases. However the simple example attached shows some odd inconsistencies. \version "2.13.40" \relative c'' \{ \override Beam \#'damping = \#+inf.0 f16 g a b a c d g, a b a c d e f g, % all beams horizontal f16 g a b a c d g, a b a c d e f g, % all beams horizontal f16 g a b a c d g, a b a c d e f g, % 2nd and 4th group not Horizontal f16 g a b a c d g, a b a c d e f g, % 2nd and 4th group not Horizontal \} \relative c'' \{ \override Beam \#'damping = \#+inf.0 f16 g a b a c d g, a b a c d e f g, \break % 4th group not Horizontal f16 g a b a c d g, a b a c d e f g, \break % 2nd and 4th group not Horizontal f16 g a b a c d g, a b a c d e f g, \break % 2nd and 4th group not Horizontal f16 g a b a c d g, a b a c d e f g, \break % 2nd and 4th group not Horizontal \} Phil Holmes : I'd suggest the snippet is worth sorting out, too. What do you reckon - adding the commands \override Beam \#'details \#'damping-direction-penalty = \#0 \override Beam \#'details \#'round-to-zero-slope = \#0 to the existing snippet, or a new one pointed to by the old one, that says "if \override Beam \#'damping = \#+inf.0 doesn't do what you want, add the other commands too, as shown here"? --- Sent from sourceforge.net because testlilyissues-a...@lists.sourceforge.net is subscribed to https://sourceforge.net/p/testlilyissues/issues/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/testlilyissues/admin/issues/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.-- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ Testlilyissues-auto mailing list testlilyissues-a...@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/testlilyissues-auto