[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5266 Add maximumFretStretch to the read properties of Tab_note_heads_engraver

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push



---

** [issues:#5266] Add maximumFretStretch to the read properties of 
Tab_note_heads_engraver **

**Status:** Started
**Created:** Thu Jan 25, 2018 11:16 PM UTC by Thomas Morley
**Last Updated:** Sun Jan 28, 2018 12:30 PM UTC
**Owner:** Thomas Morley


rebased

http://codereview.appspot.com/334430043


---

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] #5265 Allow left-handed fret-markups

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push.



---

** [issues:#5265] Allow left-handed fret-markups**

**Status:** Started
**Created:** Mon Jan 22, 2018 10:03 PM UTC by Thomas Morley
**Last Updated:** Sun Jan 28, 2018 12:29 PM UTC
**Owner:** Thomas Morley


Allow left-handed fret-markups

By adding a new boolean subproperty: left-handed.
- Extends Documentation/notation/fretted-strings.itely
- Extends Documentation/changes.tely
- Extenss scm/define-grob-properties.scm
- Adds regtest input/regression/fret-diagrams-left-handed.ly
- Disables the possibility to use negative string-distance

http://codereview.appspot.com/339270043


---

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] #5265 Allow left-handed fret-markups

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **labels**:  --> Fixed_2_19_21
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

pushed to staging as:
commit e10b92213c1a98e1e3b76df300a022b41e372c8b
Author: Thomas Morley 
Date:   Thu Jan 18 20:32:37 2018 +0100

Allow left-handed fret-markups

Issue 5265

By adding a new boolean subproperty: handedness.
- Extends Documentation/notation/fretted-strings.itely
- Extends Documentation/changes.tely
- Extenss scm/define-grob-properties.scm
- Adds regtest input/regression/fret-diagrams-left-handed.ly
- Disables the possibility to use negative string-distance




---

** [issues:#5265] Allow left-handed fret-markups**

**Status:** Fixed
**Labels:** Fixed_2_19_21 
**Created:** Mon Jan 22, 2018 10:03 PM UTC by Thomas Morley
**Last Updated:** Wed Jan 31, 2018 03:52 PM UTC
**Owner:** Thomas Morley


Allow left-handed fret-markups

By adding a new boolean subproperty: left-handed.
- Extends Documentation/notation/fretted-strings.itely
- Extends Documentation/changes.tely
- Extenss scm/define-grob-properties.scm
- Adds regtest input/regression/fret-diagrams-left-handed.ly
- Disables the possibility to use negative string-distance

http://codereview.appspot.com/339270043


---

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] #5266 Add maximumFretStretch to the read properties of Tab_note_heads_engraver

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **labels**:  --> Fixed_2_21_0
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

pushed to staging as:
commit dcaf6f7a95a04a6065f124ecee270975d5d3e4ab
Author: Thomas Morley 
Date:   Fri Jan 26 00:12:35 2018 +0100

Add maximumFretStretch to the read properties of Tab_note_heads_engraver




---

** [issues:#5266] Add maximumFretStretch to the read properties of 
Tab_note_heads_engraver **

**Status:** Fixed
**Labels:** Fixed_2_21_0 
**Created:** Thu Jan 25, 2018 11:16 PM UTC by Thomas Morley
**Last Updated:** Wed Jan 31, 2018 03:52 PM UTC
**Owner:** Thomas Morley


rebased

http://codereview.appspot.com/334430043


---

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] #5269 Create hard links instead of copies for certain documentation targets.

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- Description has changed:

Diff:







- **Needs**:  -->  
- **Type**: Enhancement --> Build



---

** [issues:#5269] Create hard links instead of copies for certain documentation 
targets.**

**Status:** Started
**Created:** Thu Feb 01, 2018 04:03 AM UTC by Dan Eble
**Last Updated:** Thu Feb 01, 2018 04:04 AM UTC
**Owner:** Dan Eble


Create hard links instead of copies for certain documentation targets.
This saves space.

http://codereview.appspot.com/336490043


---

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] #5267 Fix building with a source directory on a different device

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [issues:#5267] Fix building with a source directory on a different device**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:09 AM UTC by Dan Eble
**Last Updated:** Thu Feb 01, 2018 03:09 AM UTC
**Owner:** nobody


Fix building with a source directory on a different device


In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.


Run git diff in the *source* directory.


Ignore .DS_Store files created by macOS Finder. (Not part of fixing
the build, but mighty convenient for me.)

http://codereview.appspot.com/335520043


---

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] #5268 Simplify building with a read-only source directory

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [issues:#5268] Simplify building with a read-only source directory**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:53 AM UTC by Dan Eble
**Last Updated:** Thu Feb 01, 2018 03:53 AM UTC
**Owner:** nobody


Simplify building with a read-only source directory

autogen.sh: If the source directory is not writable, generate the
configure script into the current directory and tell the configure
script the source directory.

This is convenient for those would prefer to build in a container or
virtual machine with a read-only view of source stored on the host.

http://codereview.appspot.com/333580043


---

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] #5267 Fix building with a source directory on a different device

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- Description has changed:

Diff:







- **Needs**:  -->  
- **Type**: Enhancement --> Build



---

** [issues:#5267] Fix building with a source directory on a different device**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:09 AM UTC by Dan Eble
**Last Updated:** Thu Feb 01, 2018 03:10 AM UTC
**Owner:** Dan Eble


Fix building with a source directory on a different device


In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.


Run git diff in the *source* directory.


Ignore .DS_Store files created by macOS Finder. (Not part of fixing
the build, but mighty convenient for me.)

http://codereview.appspot.com/335520043


---

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] #5268 Simplify building with a read-only source directory

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- Description has changed:

Diff:







- **Needs**:  -->  
- **Type**: Enhancement --> Build



---

** [issues:#5268] Simplify building with a read-only source directory**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:53 AM UTC by Dan Eble
**Last Updated:** Thu Feb 01, 2018 03:53 AM UTC
**Owner:** Dan Eble


Simplify building with a read-only source directory

autogen.sh: If the source directory is not writable, generate the
configure script into the current directory and tell the configure
script the source directory.

This is convenient for those would prefer to build in a container or
virtual machine with a read-only view of source stored on the host.

http://codereview.appspot.com/333580043


---

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] #5269 Create hard links instead of copies for certain documentation targets.

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [issues:#5269] Create hard links instead of copies for certain documentation 
targets.**

**Status:** Started
**Created:** Thu Feb 01, 2018 04:03 AM UTC by Dan Eble
**Last Updated:** Thu Feb 01, 2018 04:03 AM UTC
**Owner:** nobody


Create hard links instead of copies for certain documentation targets.
This saves space.

http://codereview.appspot.com/336490043


---

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] #5267 Fix building with a source directory on a different device

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: new --> review
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#5267] Fix building with a source directory on a different device**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:09 AM UTC by Dan Eble
**Last Updated:** Thu Feb 01, 2018 04:13 AM UTC
**Owner:** Dan Eble


Fix building with a source directory on a different device


In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.


Run git diff in the *source* directory.


Ignore .DS_Store files created by macOS Finder. (Not part of fixing
the build, but mighty convenient for me.)

http://codereview.appspot.com/335520043


---

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] #5269 Create hard links instead of copies for certain documentation targets.

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: new --> review
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#5269] Create hard links instead of copies for certain documentation 
targets.**

**Status:** Started
**Created:** Thu Feb 01, 2018 04:03 AM UTC by Dan Eble
**Last Updated:** Thu Feb 01, 2018 04:14 AM UTC
**Owner:** Dan Eble


Create hard links instead of copies for certain documentation targets.
This saves space.

http://codereview.appspot.com/336490043


---

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] #5268 Simplify building with a read-only source directory

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: new --> review
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#5268] Simplify building with a read-only source directory**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:53 AM UTC by Dan Eble
**Last Updated:** Thu Feb 01, 2018 04:14 AM UTC
**Owner:** Dan Eble


Simplify building with a read-only source directory

autogen.sh: If the source directory is not writable, generate the
configure script into the current directory and tell the configure
script the source directory.

This is convenient for those would prefer to build in a container or
virtual machine with a read-only view of source stored on the host.

http://codereview.appspot.com/333580043


---

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] #5177 LilyPad for Windows' Simplified Chinese menu is broken

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

LilyPad for Windows in LilyPond 2.19.81 is fixed.
Simplified Chinese menu is not broken.



Attachments:

- 
[lilypad-sc-nobroken.png](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/6b4c86da/1c95/attachment/lilypad-sc-nobroken.png)
 (6.5 kB; image/png)


---

** [issues:#5177] LilyPad for Windows' Simplified Chinese menu is broken**

**Status:** Fixed
**Labels:** Fixed_2_19_81 
**Created:** Sun Aug 20, 2017 01:26 PM UTC by Masamichi Hosoda
**Last Updated:** Sun Feb 04, 2018 02:45 AM UTC
**Owner:** Masamichi Hosoda


Mark Jack reported that LilyPad for Windows' Simplified Chinese menu is broken.
http://lists.gnu.org/archive/html/bug-lilypond/2017-08/msg00019.html



---

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] #1862 Misleading clef placement at the end of a volta

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

I think this should be treated as a bug rather than as an ugly. It's positively 
misleading to the player to be told of a clef change which shouldn't happen.


---

** [issues:#1862] Misleading clef placement at the end of a volta**

**Status:** Accepted
**Created:** Sun Sep 04, 2011 03:01 AM UTC by Anonymous
**Last Updated:** Sat Feb 03, 2018 07:01 PM UTC
**Owner:** nobody
**Attachments:**

- 
[ClefPlacement.png](https://sourceforge.net/p/testlilyissues/issues/1862/attachment/ClefPlacement.png)
 (12.4 kB; image/png)


*Originally created by:* *anonymous

*Originally created by:* 
[philehol...@googlemail.com](http://code.google.com/u/112417728497802969867/)

>From Bertrand Bordage:


:::TeX
\markup "This gives the impression that the repeat should be done with a F
clef."
{
  \clef F r2 r4 \clef G r8 a
  \repeat volta 2 { \repeat unfold 8 d'4 }
  \alternative {
{ d' r4 r r8 a }
{ \clef F d4 d d d }
  }
}

\markup "This is what should be engraved."
{
  \clef F r2 r4 \clef G r8 a
  \repeat volta 2 { \repeat unfold 8 d'4 }
  \alternative {
{ d' r4 r r8 a }
{
  \override Score.Clef #'break-align-symbol = #'time-signature
  \clef F d4 d d d
}
  }
}

There's a similar problem with time signatures.


---

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] #5270 Let parser use define-markup-command-internal

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [issues:#5270] Let parser use define-markup-command-internal**

**Status:** Started
**Created:** Sun Feb 04, 2018 12:13 AM UTC by David Kastrup
**Last Updated:** Sun Feb 04, 2018 12:13 AM UTC
**Owner:** nobody


Let parser use define-markup-command-internal

Macros/syntax are quirky to use from C++.


Also:

Split out define-markup-command-internal

http://codereview.appspot.com/334460043


---

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] #5177 LilyPad for Windows' Simplified Chinese menu is broken

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **labels**:  --> Fixed_2_19_81



---

** [issues:#5177] LilyPad for Windows' Simplified Chinese menu is broken**

**Status:** Fixed
**Labels:** Fixed_2_19_81 
**Created:** Sun Aug 20, 2017 01:26 PM UTC by Masamichi Hosoda
**Last Updated:** Wed Nov 08, 2017 02:09 PM UTC
**Owner:** Masamichi Hosoda


Mark Jack reported that LilyPad for Windows' Simplified Chinese menu is broken.
http://lists.gnu.org/archive/html/bug-lilypond/2017-08/msg00019.html



---

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] #5270 Let parser use define-markup-command-internal

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Make do completely without primitive-eval for macro definitions

http://codereview.appspot.com/334460043


---

** [issues:#5270] Let parser use define-markup-command-internal**

**Status:** Started
**Created:** Sun Feb 04, 2018 12:13 AM UTC by David Kastrup
**Last Updated:** Sun Feb 04, 2018 04:55 PM UTC
**Owner:** David Kastrup


Let parser use define-markup-command-internal

Macros/syntax are quirky to use from C++.


Also:

Split out define-markup-command-internal

http://codereview.appspot.com/334460043


---

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] #5271 Make emacs C++ style setting work for me

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [issues:#5271] Make emacs C++ style setting work for me**

**Status:** Started
**Created:** Sun Feb 04, 2018 08:08 PM UTC by Dan Eble
**Last Updated:** Sun Feb 04, 2018 08:08 PM UTC
**Owner:** nobody


Make emacs C++ style setting work for me

In the .dir-locals.el file for emacs, instead of setting c-default-style, set 
c-file-style.  The former was not setting the style for the files I opened.

http://codereview.appspot.com/333600043


---

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] #5270 Let parser use define-markup-command-internal

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Fix result of make-...-markup-list to return a list as the strange API requires

http://codereview.appspot.com/334460043


---

** [issues:#5270] Let parser use define-markup-command-internal**

**Status:** Started
**Created:** Sun Feb 04, 2018 12:13 AM UTC by David Kastrup
**Last Updated:** Mon Feb 05, 2018 01:20 AM UTC
**Owner:** David Kastrup


Let parser use define-markup-command-internal

Macros/syntax are quirky to use from C++.


Also:

Split out define-markup-command-internal

http://codereview.appspot.com/334460043


---

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] #5270 Let parser use define-markup-command-internal

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- Description has changed:

Diff:







- **Needs**:  -->  
- **Patch**: new --> review
- **Type**:  --> Enhancement
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#5270] Let parser use define-markup-command-internal**

**Status:** Started
**Created:** Sun Feb 04, 2018 12:13 AM UTC by David Kastrup
**Last Updated:** Mon Feb 05, 2018 01:20 AM UTC
**Owner:** David Kastrup


Let parser use define-markup-command-internal

Macros/syntax are quirky to use from C++.


Also:

Split out define-markup-command-internal

http://codereview.appspot.com/334460043


---

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] #5271 Make emacs C++ style setting work for me

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- Description has changed:

Diff:







- **Needs**:  -->  
- **Patch**: new --> review
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#5271] Make emacs C++ style setting work for me**

**Status:** Started
**Created:** Sun Feb 04, 2018 08:08 PM UTC by Dan Eble
**Last Updated:** Sun Feb 04, 2018 08:09 PM UTC
**Owner:** Dan Eble


Make emacs C++ style setting work for me

In the .dir-locals.el file for emacs, instead of setting c-default-style, set 
c-file-style.  The former was not setting the style for the files I opened.

http://codereview.appspot.com/333600043


---

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] #5271 Make emacs C++ style setting work for me

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> countdown
- **Comment**:

patch on countdown for Feb 9th



---

** [issues:#5271] Make emacs C++ style setting work for me**

**Status:** Started
**Created:** Sun Feb 04, 2018 08:08 PM UTC by Dan Eble
**Last Updated:** Mon Feb 05, 2018 03:08 PM UTC
**Owner:** Dan Eble


Make emacs C++ style setting work for me

In the .dir-locals.el file for emacs, instead of setting c-default-style, set 
c-file-style.  The former was not setting the style for the files I opened.

http://codereview.appspot.com/333600043


---

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] #5269 Create hard links instead of copies for certain documentation targets.

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> countdown
- **Comment**:

Patch on countdown for Feb 9th.



---

** [issues:#5269] Create hard links instead of copies for certain documentation 
targets.**

**Status:** Started
**Created:** Thu Feb 01, 2018 04:03 AM UTC by Dan Eble
**Last Updated:** Fri Feb 02, 2018 05:52 PM UTC
**Owner:** Dan Eble


Create hard links instead of copies for certain documentation targets.
This saves space.

http://codereview.appspot.com/336490043


---

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] #5270 Let parser use define-markup-command-internal

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> countdown
- **Comment**:

Patch on countdown for Feb 9th.



---

** [issues:#5270] Let parser use define-markup-command-internal**

**Status:** Started
**Created:** Sun Feb 04, 2018 12:13 AM UTC by David Kastrup
**Last Updated:** Mon Feb 05, 2018 01:45 PM UTC
**Owner:** David Kastrup


Let parser use define-markup-command-internal

Macros/syntax are quirky to use from C++.


Also:

Split out define-markup-command-internal

http://codereview.appspot.com/334460043


---

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] #5268 Simplify building with a read-only source directory

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Comment**:

Patch on countdown for Feb 9th.



---

** [issues:#5268] Simplify building with a read-only source directory**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:53 AM UTC by Dan Eble
**Last Updated:** Sat Feb 03, 2018 12:30 PM UTC
**Owner:** Dan Eble


Simplify building with a read-only source directory

autogen.sh: If the source directory is not writable, generate the
configure script into the current directory and tell the configure
script the source directory.

This is convenient for those would prefer to build in a container or
virtual machine with a read-only view of source stored on the host.

http://codereview.appspot.com/333580043


---

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] #5267 Fix building with a source directory on a different device

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> countdown
- **Comment**:

Patch on countdown for Feb 9th.



---

** [issues:#5267] Fix building with a source directory on a different device**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:09 AM UTC by Dan Eble
**Last Updated:** Fri Feb 02, 2018 06:18 PM UTC
**Owner:** Dan Eble


Fix building with a source directory on a different device


In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.


Run git diff in the *source* directory.


Ignore .DS_Store files created by macOS Finder. (Not part of fixing
the build, but mighty convenient for me.)

http://codereview.appspot.com/335520043


---

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] #5267 Fix building with a source directory on a different device

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: countdown --> needs_work
- **Comment**:

Dan,  I have to take this back. I just went over my lists of patches and see 
that made a mistake here by not testing this as I thought I seem to have tested 
one of the othe rissues you submitted at the same time twice by mistake.

So I went back to test this patch and it fails on the make doc part (all other 
make 'tests' pass including reg test).

The errors that get posted are:

~~~
make -C css out=www WWW-1
make[3]: Entering directory '/home/jlowe/lilypond-git/build/Documentation/css'
mkdir -p ./out-www
touch ./out-www/dummy.dep
echo '*' > ./out-www/.gitignore
/home/jlowe/lilypond-git/Documentation/css/lilypond-manuals-ie-fixes.css 
out-www/lilypond-manuals-ie-fixes.css
make[3]: execvp: 
/home/jlowe/lilypond-git/Documentation/css/lilypond-manuals-ie-fixes.css: 
Permission denied
/home/jlowe/lilypond-git/./Documentation/css/GNUmakefile:24: recipe for target 
'out-www/lilypond-manuals-ie-fixes.css' failed
make[3]: *** [out-www/lilypond-manuals-ie-fixes.css] Error 127
make[3]: Leaving directory '/home/jlowe/lilypond-git/build/Documentation/css'
/home/jlowe/lilypond-git/./Documentation/GNUmakefile:226: recipe for target 
'out-www/css' failed
make[2]: *** [out-www/css] Error 2
make[2]: *** Waiting for unfinished jobs
/home/jlowe/lilypond-git/build/scripts/build/out/yyout2grammar 
./out-www/parser.output out-www/ly-grammar.txt
make[2]: Leaving directory '/home/jlowe/lilypond-git/build/Documentation'
/home/jlowe/lilypond-git/stepmake/stepmake/generic-targets.make:166: recipe for 
target 'WWW-1' failed
make[1]: *** [WWW-1] Error 2
make[1]: Leaving directory '/home/jlowe/lilypond-git/build'
/home/jlowe/lilypond-git/stepmake/stepmake/generic-targets.make:182: recipe for 
target 'doc-stage-1' failed
make: *** [doc-stage-1] Error 2

~~~

I assume it is the 'permission denied' error which is causing this although I 
don't know why I'd get this kind of error as I have permissions toi write into 
this dir after the fact - I checked.

So I tried it (making doc) without using an 'out of tree' build and it seems to 
work.

I therefore wonder if the problem is the 'path' you are setting/linking to in 
that css file. There's no reason it should not work in an out of tree build is 
there otherwise?

James



---

** [issues:#5267] Fix building with a source directory on a different device**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:09 AM UTC by Dan Eble
**Last Updated:** Tue Feb 06, 2018 07:17 PM UTC
**Owner:** Dan Eble


Fix building with a source directory on a different device


In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.


Run git diff in the *source* directory.


Ignore .DS_Store files created by macOS Finder. (Not part of fixing
the build, but mighty convenient for me.)

http://codereview.appspot.com/335520043


---

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] Re: #5267 Fix building with a source directory on a different device

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Hi James,
I recently tested issues 5267, 5268, 5269, 5270, all on top of each other, in 
one go, with guilev2.
I've got a successful make and make doc
Maybe a dependency-problem?


---

** [issues:#5267] Fix building with a source directory on a different device**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:09 AM UTC by Dan Eble
**Last Updated:** Tue Feb 06, 2018 07:57 PM UTC
**Owner:** Dan Eble


Fix building with a source directory on a different device


In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.


Run git diff in the *source* directory.


Ignore .DS_Store files created by macOS Finder. (Not part of fixing
the build, but mighty convenient for me.)

http://codereview.appspot.com/335520043


---

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] Re: #5267 Fix building with a source directory on a different device

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

James, 

The following should have been either a link or a copy command, but the command 
name is missing.

/home/jlowe/lilypond-git/Documentation/css/lilypond-manuals-ie-fixes.css 
out-www/lilypond-manuals-ie-fixes.css
make[3]: execvp: 
/home/jlowe/lilypond-git/Documentation/css/lilypond-manuals-ie-fixes.css: 
Permission denied

This is the rule I modified:

 $(outdir)/%.css: $(top-src-dir)/Documentation/css/%.css
 $(LN_SRC_TO_BUILD) $< $@

LN_SRC_TO_BUILD should have been determined by configure. Therefore, if you 
don't mind, please rerun autogen.sh and configure before building.  I think it 
will fix the problem.


---

** [issues:#5267] Fix building with a source directory on a different device**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:09 AM UTC by Dan Eble
**Last Updated:** Tue Feb 06, 2018 07:57 PM UTC
**Owner:** Dan Eble


Fix building with a source directory on a different device


In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.


Run git diff in the *source* directory.


Ignore .DS_Store files created by macOS Finder. (Not part of fixing
the build, but mighty convenient for me.)

http://codereview.appspot.com/335520043


---

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] #5272 Add \depart

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [issues:#5272] Add \depart **

**Status:** Started
**Created:** Wed Feb 07, 2018 01:33 AM UTC by Dan Eble
**Last Updated:** Wed Feb 07, 2018 01:33 AM UTC
**Owner:** nobody


Add \depart 

Add \depart  command to make it unnecessary to continue abusing 
rehearsal marks for instructions such as "D.C."  It solves these problems that 
rehearsal marks alone could not solve:

* It is possible to change the default direction of departure marks
  without changing the default direction of rehearsal marks.

* It is possible to use a departure mark and a rehearsal mark at the
  same moment.

http://codereview.appspot.com/337520043


---

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] #5272 Add a command and grob type for instructions like D.C.

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **summary**: Add \depart  --> Add a command and grob type for 
instructions like D.C.
- Description has changed:

Diff:



--- old
+++ new
@@ -1,5 +1,3 @@
-Add \depart 
-
 Add \depart  command to make it unnecessary to continue abusing 
rehearsal marks for instructions such as "D.C."  It solves these problems that 
rehearsal marks alone could not solve:
 
 * It is possible to change the default direction of departure marks



- **Needs**:  -->  
- **Patch**: new --> needs_work



---

** [issues:#5272] Add a command and grob type for instructions like D.C.**

**Status:** Started
**Created:** Wed Feb 07, 2018 01:33 AM UTC by Dan Eble
**Last Updated:** Wed Feb 07, 2018 01:33 AM UTC
**Owner:** Dan Eble


Add \depart  command to make it unnecessary to continue abusing 
rehearsal marks for instructions such as "D.C."  It solves these problems that 
rehearsal marks alone could not solve:

* It is possible to change the default direction of departure marks
  without changing the default direction of rehearsal marks.

* It is possible to use a departure mark and a rehearsal mark at the
  same moment.

http://codereview.appspot.com/337520043


---

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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

I've spent a lot of time on thinking about what to write. On the one hand, I 
didn't want to write screeds and screeds, on the other hand I wanted to supply 
background information to underpin my favoured solution.

For those not interested in the details, please skip to "Proposed solutions".


# Numerical precision: rounding problem
Starting off with a completely undamped beam, damping is implemented by raising 
one end and lowering the other end of the beam.
Let dy be the vertical distance between left and right end of the completely 
undamped beam. With infinite damping, LilyPond will raise the lower end by dy/2 
and raise the lower end by dy/2. Theoretically, this will lead to two end 
points with the exact same y value, i.e. a horizontal beam.

**Problem:** due to limited numerical precision there may be tiny rounding 
problems when dividing by 2 and adding.
Even the slightest vertical distance between the end points, however, will 
later be quantized (i.e. increased) to valid sit/straddle/hang positions and 
thus yield noticeable slopes.
The numeric rounding issue may even overcompensate the slope so that the beam's 
direction flips.
That's what happened when we see a raising beam that really should be 
descending (or, ideally, be  horizontal).

All these calculations are very sensitive to the slightest deviations and 
highly depend on beam slope, beam span, stave size, line width, indent, etc.

**One solution would be to avoid the precision problem.**

In the following list, DELTA unquanted_y is the remaining vertical distance 
(should be 0) of both ends of the beam.
As you can see, even the original dy sign may flip and the numeric "error" is 
so small I had to use exponential notation:

~~~
original dy = -0.680277, DELTA unquanted_y =  5.5511e-17
original dy = -0.431074, DELTA unquanted_y =  2.7756e-17
original dy =  1.301622, DELTA unquanted_y =  0.e+00
original dy = -0.680277, DELTA unquanted_y = -5.5511e-17
original dy = -0.431074, DELTA unquanted_y =  2.7756e-17
original dy =  1.301622, DELTA unquanted_y =  0.e+00
original dy =  1.303842, DELTA unquanted_y =  0.e+00
original dy = -0.428570, DELTA unquanted_y = -2.7756e-17
original dy = -0.679738, DELTA unquanted_y =  5.5511e-17
original dy =  1.303842, DELTA unquanted_y =  0.e+00
original dy = -0.428570, DELTA unquanted_y =  2.7756e-17
original dy = -0.679738, DELTA unquanted_y =  5.5511e-17
~~~

The sligthest deviation between left and right beam end Y position will be 
drastically amplified by quanting to valid sit/straddle/hang positions later on.

After avoiding the rounding problem, there are no unwanted DELTAs left in the 
case of  infinite damping:

~~~
original dy = -0.680277, DELTA unquanted_y =  0.e+00
original dy = -0.431074, DELTA unquanted_y =  0.e+00
original dy =  1.301622, DELTA unquanted_y =  0.e+00
original dy = -0.680277, DELTA unquanted_y =  0.e+00
original dy = -0.431074, DELTA unquanted_y =  0.e+00
original dy =  1.301622, DELTA unquanted_y =  0.e+00
original dy =  1.303842, DELTA unquanted_y =  0.e+00
original dy = -0.428570, DELTA unquanted_y =  0.e+00
original dy = -0.679738, DELTA unquanted_y =  0.e+00
original dy =  1.303842, DELTA unquanted_y =  0.e+00
original dy = -0.428570, DELTA unquanted_y =  0.e+00
original dy = -0.679738, DELTA unquanted_y =  0.e+00
~~~



# Damping mechanism
Beam damping is needed because "beam angles should not deviate far from the 
horizontal" (Gould).
Starting off with the slope of a straight line that links the outer noteheads 
of the beam, LilyPond applies a rather simple damping formula to the slope:

**`slope = 0.6 * tanh (slope) / (damping + concaveness);`**

Let's have a look a the numerator first:

**Numerator**
One may wonder about the hyperbolic tangent (tanh), but it turns out to be very 
suitable as a damping factor:
![](https://upload.wikimedia.org/wikipedia/commons/8/87/Hyperbolic_Tangent.svg)

* It's symmetric to the origin and can be used both for positive and negative 
slopes
* For small |x|, there is practically no damping at all
* |tanh(x)| will never become greater than 1, however large x may be.
* For values of |x| > 3, tanh(x) is practically 1.

Consequently, the numerator of the damping term 0.6 * tanh(slope) an never 
exceed the value of 0.6 (i.e. an angle of 31°).

**Denominator**
damping has a default value of 1, concaveness is 0 for non-concave beams.
Concave groups of notes should always have a horizontal beam - independent of 
damping.So S So that's a special case we'll set aside for the moment.

By specifying damping values other than 1, we can increase damping (damping > 
1) to get flatter beams 

From a purely mathematical point of view, damping and concaveness play a very 
similar role, because the tanh-damped numerator is divided by the sum of 
damping and concaveness.

The idea of achieving horizontal beams by dividing a denominator (that can 
never becom greater than 0.6) by an infinite damp

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5262 LM: incorrect staff-staff-spacing example (regression)

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **status**: Accepted --> Started
- **assigned_to**: Torsten Hämmerle
- **Comment**:

A critical error sounds pretty intimidating, but nevertheless, I've had a 
look...

#What's the goal?
By default, when a score has to vertically streched, LilyPond will keep grouped 
staves closer together and allow bigger gaps between the groups.
In organ music, however, the three staves should equally spaced, even if the 
two manual staves are grouped by a PianoStaff.

The example coding attemps to reduce the stretchability between manual two and 
pedal stave.

# Analysis
In the LilyPond documentation coding, only one single property of 
staff-staff-spacing is set:

`\override VerticalAxisGroup.staff-staff-spacing.stretchability = 5`

That way, all the other sub properties still are unset and so we have a 0 
basic-distance, a 0 minimum-distance and 0 padding.
**Result:** Manual two stave and pedal stave stick together.

We definitely have to specify a full set of sub properties and everything will 
work as desired.
~~~
\override VerticalAxisGroup.staff-staff-spacing = #'((basic-distance . 9)
 (minimum-distance . 7)
 (padding . 1)
 (stretchability . 5))
~~~

#Why did it "work" in 2.18.2?
The plain truth is that it actually didn't work at all in 2.18.2!
I've even re-installed an old 2.14.2 LilyPond to see that it didn't work there, 
either.

In fact, the
`\override VerticalAxisGroup.staff-staff-spacing.stretchability = 5`
statement didn't have any effect, because the attempetd \override was 
unsuccessful: 

**Reason:**
The assignment of VerticalAxisGroup.staff-staff-spacing.stretchabiliy failed.
See log:
~~~
warning: type check for `staff-staff-spacing' failed; value `5' must be of type 
`list'
~~~
As a result, staff-staff-spacing hasn't been changed and therefore, the staves 
didn't collapse. The stretchability wasn't changed as desired, either.

Now, in version 2.19, this syntax works and the effect of 0 distance is much 
more strinking than the unsuccessful stretchability override of former releases.

# Solution
**Specify a full set of staff-staff-spacing sub properties.** as proposed in 
"Analysis".
I'll upload a patch shortly.
I had to re-install my LilyDev due to virtual disk problems that prevented me 
from complilng the documentation. Let's see...

By the way: the German explanatory text (and only the German as far as I've 
seen) even mentions the fact that a full set of variables has to be supplied:
*"Im Moment kann man nicht nur die strechability {sic!] 
(Spreizbarkeit)-Untereigenschaft verändern, darum müssen hier auch die anderen 
Untereigenschaften kopiert werden."*

All the best,
Torsten



---

** [issues:#5262] LM: incorrect staff-staff-spacing example (regression)**

**Status:** Started
**Created:** Wed Jan 17, 2018 08:53 PM UTC by Simon Albrecht
**Last Updated:** Wed Jan 17, 2018 08:53 PM UTC
**Owner:** Torsten Hämmerle
**Attachments:**

- 
[2.18.2.png](https://sourceforge.net/p/testlilyissues/issues/5262/attachment/2.18.2.png)
 (16.8 kB; image/png)
- 
[2.19.80.png](https://sourceforge.net/p/testlilyissues/issues/5262/attachment/2.19.80.png)
 (21.7 kB; image/png)


[Reported by Paul 
Hodges:](https://lists.gnu.org/archive/html/bug-lilypond/2018-01/msg00014.html)

>In the example on the documentation page 

>http://lilypond.org/doc/v2.19/Documentation/learning/building-a-score-from-scratch
> 
the command
  `\override VerticalAxisGroup.staff-staff-spacing.stretchability = 5`
is used to modify the spacing of the pedal staff in an organ score.

>The result shown on the documentation page (which I also get at home
with 2.19.80) does not match the result on the corresponding page for
2.18, and is clearly wrong.


---

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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Because you asked: I introduced `tanh` many, many years ago based on analyzing 
stem damping data in Helene Wanske's book...  This function fit best :-)

I favour solution (1).  This looks very TeX-like, and I trust Knuth that he had 
good reasons to design similar bounds for solving paragraph layout and the like.


---

** [issues:#1493] Problem with horizontal beams**

**Status:** Started
**Created:** Wed Jan 26, 2011 12:21 PM UTC by Anonymous
**Last Updated:** Thu Feb 08, 2018 03:50 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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5268 Simplify building with a read-only source directory

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> countdown



---

** [issues:#5268] Simplify building with a read-only source directory**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:53 AM UTC by Dan Eble
**Last Updated:** Tue Feb 06, 2018 07:17 PM UTC
**Owner:** Dan Eble


Simplify building with a read-only source directory

autogen.sh: If the source directory is not writable, generate the
configure script into the current directory and tell the configure
script the source directory.

This is convenient for those would prefer to build in a container or
virtual machine with a read-only view of source stored on the host.

http://codereview.appspot.com/333580043


---

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] #5267 Fix building with a source directory on a different device

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: needs_work --> new
- **Comment**:

Returning to "new" to get James' attention.  Please see my earlier comment.



---

** [issues:#5267] Fix building with a source directory on a different device**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:09 AM UTC by Dan Eble
**Last Updated:** Tue Feb 06, 2018 07:57 PM UTC
**Owner:** Dan Eble


Fix building with a source directory on a different device


In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.


Run git diff in the *source* directory.


Ignore .DS_Store files created by macOS Finder. (Not part of fixing
the build, but mighty convenient for me.)

http://codereview.appspot.com/335520043


---

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] #5267 Fix building with a source directory on a different device

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: new --> countdown
- **Comment**:

Dan,

Passes make, make check and a full make doc.

I re-tested this as asked and it does work after all - this is one of those 
patches that the normal patch test workflow cannot easily cope with (I think) 
whereby you need to run the make test-baseline off of current master and then 
run make check against the applied patch. However if one needs to re-run 
autogen.sh and configure again, to make doc, I don't know if that would work 
without having to make disclean in between, thereby effectively destroying the 
make check results.

Anyway, I'll jump this up to 'Countdown for February 12th' just to give others 
a chance to comment without delaying this more by only setting to review.

Thanks for your patience.



---

** [issues:#5267] Fix building with a source directory on a different device**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:09 AM UTC by Dan Eble
**Last Updated:** Fri Feb 09, 2018 03:20 AM UTC
**Owner:** Dan Eble


Fix building with a source directory on a different device


In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.


Run git diff in the *source* directory.


Ignore .DS_Store files created by macOS Finder. (Not part of fixing
the build, but mighty convenient for me.)

http://codereview.appspot.com/335520043


---

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] #5270 Let parser use define-markup-command-internal

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push.



---

** [issues:#5270] Let parser use define-markup-command-internal**

**Status:** Started
**Created:** Sun Feb 04, 2018 12:13 AM UTC by David Kastrup
**Last Updated:** Tue Feb 06, 2018 07:17 PM UTC
**Owner:** David Kastrup


Let parser use define-markup-command-internal

Macros/syntax are quirky to use from C++.


Also:

Split out define-markup-command-internal

http://codereview.appspot.com/334460043


---

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] #5268 Simplify building with a read-only source directory

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push.



---

** [issues:#5268] Simplify building with a read-only source directory**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:53 AM UTC by Dan Eble
**Last Updated:** Thu Feb 08, 2018 06:01 PM UTC
**Owner:** Dan Eble


Simplify building with a read-only source directory

autogen.sh: If the source directory is not writable, generate the
configure script into the current directory and tell the configure
script the source directory.

This is convenient for those would prefer to build in a container or
virtual machine with a read-only view of source stored on the host.

http://codereview.appspot.com/333580043


---

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] #5271 Make emacs C++ style setting work for me

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push.

Dan, perhaps change the commit message slightly so it doesn't quite look like a 
'fix-just-for-Dans-own-config-settings' patch in the git history? (I saw the 
rietveld comments).



---

** [issues:#5271] Make emacs C++ style setting work for me**

**Status:** Started
**Created:** Sun Feb 04, 2018 08:08 PM UTC by Dan Eble
**Last Updated:** Tue Feb 06, 2018 07:16 PM UTC
**Owner:** Dan Eble


Make emacs C++ style setting work for me

In the .dir-locals.el file for emacs, instead of setting c-default-style, set 
c-file-style.  The former was not setting the style for the files I opened.

http://codereview.appspot.com/333600043


---

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] #5269 Create hard links instead of copies for certain documentation targets.

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push.



---

** [issues:#5269] Create hard links instead of copies for certain documentation 
targets.**

**Status:** Started
**Created:** Thu Feb 01, 2018 04:03 AM UTC by Dan Eble
**Last Updated:** Tue Feb 06, 2018 07:17 PM UTC
**Owner:** Dan Eble


Create hard links instead of copies for certain documentation targets.
This saves space.

http://codereview.appspot.com/336490043


---

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] #5270 Let parser use define-markup-command-internal

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **labels**:  --> Fixed_2_21_0
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

~~~
Issue 5270/1: Let make-markup accept symbols as markup function name
author  David Kastrup 
Sun, 4 Feb 2018 13:40:14 + (14:40 +0100)
committer   David Kastrup 
Fri, 9 Feb 2018 09:56:05 + (10:56 +0100)
commit  e81286f37254ade568846628800ecb4b655482ca
~~~

~~~
Issue 5270/2: Split out define-markup-command-internal
author  David Kastrup 
Sun, 4 Feb 2018 00:11:46 + (01:11 +0100)
committer   David Kastrup 
Fri, 9 Feb 2018 09:56:13 + (10:56 +0100)
commit  084a54d5734111d4dca6bf4950c76be35a618175
~~~

~~~
Issue 5270/3: Let parser use define-markup-command-internal master staging
author  David Kastrup 
Sun, 4 Feb 2018 00:12:10 + (01:12 +0100)
committer   David Kastrup 
Fri, 9 Feb 2018 09:56:17 + (10:56 +0100)
commit  85673408352f1e11ce03bf94850a0d9aa7d0ed34
~~~



---

** [issues:#5270] Let parser use define-markup-command-internal**

**Status:** Fixed
**Labels:** Fixed_2_21_0 
**Created:** Sun Feb 04, 2018 12:13 AM UTC by David Kastrup
**Last Updated:** Fri Feb 09, 2018 07:57 AM UTC
**Owner:** David Kastrup


Let parser use define-markup-command-internal

Macros/syntax are quirky to use from C++.


Also:

Split out define-markup-command-internal

http://codereview.appspot.com/334460043


---

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] #5268 Simplify building with a read-only source directory

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **labels**:  --> Fixed_2_21_0
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

commit edb80ace4df074fcb8a4976f452aabd2238cf733 (HEAD -> 
dev/issue-5268-autogen-ro-srcdir, origin/staging)
Author: Dan Eble 
Date:   Sat Jan 27 13:04:49 2018 -0500

Issue 5268: simplify building with a read-only source directory

autogen.sh: If the source directory is not writable, generate the
configure script into the current directory and tell the configure
script the source directory.

This is convenient for those would prefer to build in a container or
virtual machine with a read-only view of source stored on the host.




---

** [issues:#5268] Simplify building with a read-only source directory**

**Status:** Fixed
**Labels:** Fixed_2_21_0 
**Created:** Thu Feb 01, 2018 03:53 AM UTC by Dan Eble
**Last Updated:** Fri Feb 09, 2018 07:56 AM UTC
**Owner:** Dan Eble


Simplify building with a read-only source directory

autogen.sh: If the source directory is not writable, generate the
configure script into the current directory and tell the configure
script the source directory.

This is convenient for those would prefer to build in a container or
virtual machine with a read-only view of source stored on the host.

http://codereview.appspot.com/333580043


---

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] #5271 Fix Emacs C++ indentation style

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **labels**:  --> Fixed_2_21_0
- **summary**: Make emacs C++ style setting work for me --> Fix Emacs C++ 
indentation style
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Type**: Enhancement --> Other
- **Comment**:

commit d4a7cc6a9a86615fbd6dc5d9360ccefc19c57a51 (HEAD -> 
pushed/issue-5271-emacs-c-file-style, origin/staging)
Author: Dan Eble 
Date:   Sun Feb 4 14:20:59 2018 -0500

Issue 5271: Fix Emacs C++ indentation style

In the .dir-locals.el file for Emacs, instead of setting
c-default-style, set c-file-style.  I found that the former was indeed
setting the default, but not the style itself.




---

** [issues:#5271] Fix Emacs C++ indentation style**

**Status:** Fixed
**Labels:** Fixed_2_21_0 
**Created:** Sun Feb 04, 2018 08:08 PM UTC by Dan Eble
**Last Updated:** Fri Feb 09, 2018 08:00 AM UTC
**Owner:** Dan Eble


Make emacs C++ style setting work for me

In the .dir-locals.el file for emacs, instead of setting c-default-style, set 
c-file-style.  The former was not setting the style for the files I opened.

http://codereview.appspot.com/333600043


---

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] #5269 Create more hard links in documentation build

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **labels**:  --> Fixed_2_21_0
- **summary**: Create hard links instead of copies for certain documentation 
targets. --> Create more hard links in documentation build
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

commit 3d7534e511a11b62db94fceb69f650e2432fbc56 (HEAD -> 
pushed/issue-5269-build-more-hard-links, origin/staging)
Author: Dan Eble 
Date:   Tue Jan 30 22:01:38 2018 -0500

Issue 5269: Create more hard links in documentation build

Create hard links instead of copies.  This saves space.




---

** [issues:#5269] Create more hard links in documentation build**

**Status:** Fixed
**Labels:** Fixed_2_21_0 
**Created:** Thu Feb 01, 2018 04:03 AM UTC by Dan Eble
**Last Updated:** Fri Feb 09, 2018 07:57 AM UTC
**Owner:** Dan Eble


Create hard links instead of copies for certain documentation targets.
This saves space.

http://codereview.appspot.com/336490043


---

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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

issue #1493: Problem with horizontal beams

file: lily/beam-quanting.cc

In spite of infinite damping, due to numeric precision problems
(rounding/adding) the resulting beams arbitrarily still had a
remaining non-zero slope, sometimes even in the "wrong" direction.

In good TeX manner and in line with concaveness (already implemented),
we'll use a threshold value of 1 for forcing horizontal beams.

http://codereview.appspot.com/337560043


---

** [issues:#1493] Problem with horizontal beams**

**Status:** Started
**Created:** Wed Jan 26, 2011 12:21 PM UTC by Anonymous
**Last Updated:** Sat Feb 10, 2018 12:08 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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1493 Problem with horizontal beams

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Needs**:  -->  
- **Patch**: new --> review
- **Type**:  --> Enhancement
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#1493] Problem with horizontal beams**

**Status:** Started
**Created:** Wed Jan 26, 2011 12:21 PM UTC by Anonymous
**Last Updated:** Sat Feb 10, 2018 12:08 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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1493 Problem with horizontal beams

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

off-topic check for division by 0 added

http://codereview.appspot.com/337560043


---

** [issues:#1493] Problem with horizontal beams**

**Status:** Started
**Created:** Wed Jan 26, 2011 12:21 PM UTC by Anonymous
**Last Updated:** Sat Feb 10, 2018 02:38 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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1493 Problem with horizontal beams

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Needs**:  -->  
- **Patch**: new --> review
- **Type**:  --> Enhancement
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#1493] Problem with horizontal beams**

**Status:** Started
**Created:** Wed Jan 26, 2011 12:21 PM UTC by Anonymous
**Last Updated:** Sat Feb 10, 2018 02:38 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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5273 Replace number-or-markup? with integer-or-markup?

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [issues:#5273] Replace number-or-markup? with integer-or-markup?**

**Status:** Started
**Created:** Sun Feb 11, 2018 01:24 PM UTC by Dan Eble
**Last Updated:** Sun Feb 11, 2018 01:24 PM UTC
**Owner:** nobody


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] #5273 Replace number-or-markup? with integer-or-markup?

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- Description has changed:

Diff:







- **Needs**:  -->  
- **Patch**: new --> review
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#5273] Replace number-or-markup? with integer-or-markup?**

**Status:** Started
**Created:** Sun Feb 11, 2018 01:24 PM UTC by Dan Eble
**Last Updated:** Sun Feb 11, 2018 01:24 PM 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] #5267 Fix building with a source directory on a different device

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push.



---

** [issues:#5267] Fix building with a source directory on a different device**

**Status:** Started
**Created:** Thu Feb 01, 2018 03:09 AM UTC by Dan Eble
**Last Updated:** Fri Feb 09, 2018 07:22 AM UTC
**Owner:** Dan Eble


Fix building with a source directory on a different device


In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.


Run git diff in the *source* directory.


Ignore .DS_Store files created by macOS Finder. (Not part of fixing
the build, but mighty convenient for me.)

http://codereview.appspot.com/335520043


---

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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> countdown
- **Comment**:

Patch on countdown for Feb 15th.



---

** [issues:#1493] Problem with horizontal beams**

**Status:** Started
**Created:** Wed Jan 26, 2011 12:21 PM UTC by Anonymous
**Last Updated:** Sat Feb 10, 2018 06:59 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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5274 GSoC 2018: Two new project ideas

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [issues:#5274] GSoC 2018: Two new project ideas**

**Status:** Started
**Created:** Mon Feb 12, 2018 06:25 PM UTC by Urs Liska
**Last Updated:** Mon Feb 12, 2018 06:25 PM UTC
**Owner:** nobody


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] #5267 Fix building with a source directory on a different device

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **labels**:  --> Fixed_2_21_0
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

commit c6dc1d63b49d83400082bc9395292037478dad6f (HEAD -> 
dev/issue-5267-srcdir-on-other-device, origin/staging)
Author: Dan Eble 
Date:   Mon Jan 29 22:33:40 2018 -0500

Issue 5267/2: Fix hard links between build and source dirs

In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.

commit 7d6205e68a4f78a5948542e3e8f4fce733522736
Author: Dan Eble 
Date:   Sat Jan 27 13:03:54 2018 -0500

Issue 5267/1: Run git diff in the *source* directory

commit 2f2e14d9b29637c7b11edb8a6809a07183eb8eff
Author: Dan Eble 
Date:   Fri Jan 26 22:47:29 2018 -0500

Ignore .DS_Store files created by macOS Finder
(Reviewed among changes for Issue 5267.)





---

** [issues:#5267] Fix building with a source directory on a different device**

**Status:** Fixed
**Labels:** Fixed_2_21_0 
**Created:** Thu Feb 01, 2018 03:09 AM UTC by Dan Eble
**Last Updated:** Mon Feb 12, 2018 05:39 PM UTC
**Owner:** Dan Eble


Fix building with a source directory on a different device


In configure, check whether hard links between files in the source and
build directories can be created.  If not, fall back on copying.  This
supports building with the source and build directories on different
devices.


Run git diff in the *source* directory.


Ignore .DS_Store files created by macOS Finder. (Not part of fixing
the build, but mighty convenient for me.)

http://codereview.appspot.com/335520043


---

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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Passes make, make check and a full make doc.


---

** [issues:#5274] GSoC 2018: Two new project ideas**

**Status:** Started
**Created:** Mon Feb 12, 2018 06:25 PM UTC by Urs Liska
**Last Updated:** Mon Feb 12, 2018 06:25 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] Re: #5274 GSoC 2018: Two new project ideas

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

What do you think, do I really have to wait for the full review cycle 
for these additions?


Am 13.02.2018 um 14:41 schrieb pkx166h:
>
> Passes make, make check and a full make doc.
>
> 
>
> *[issues:#5274] 
>  GSoC 2018: Two 
> new project ideas*
>
> *Status:* Started
> *Created:* Mon Feb 12, 2018 06:25 PM UTC by Urs Liska
> *Last Updated:* Mon Feb 12, 2018 06:25 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 you indicated interest in 
> https://sourceforge.net/p/testlilyissues/issues/5274/
>
> To unsubscribe from further messages, please visit 
> https://sourceforge.net/auth/subscriptions/
>




---

** [issues:#5274] GSoC 2018: Two new project ideas**

**Status:** Started
**Created:** Mon Feb 12, 2018 06:25 PM UTC by Urs Liska
**Last Updated:** Tue Feb 13, 2018 01:41 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] #5274 GSoC 2018: Two new project ideas

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> countdown
- **Comment**:

Patch on countdown for Feb 18th



---

** [issues:#5274] GSoC 2018: Two new project ideas**

**Status:** Started
**Created:** Mon Feb 12, 2018 06:25 PM UTC by Urs Liska
**Last Updated:** Wed Feb 14, 2018 07:24 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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push. Torsten, if you do not have commit access 
please create a git formatted patch against current master and I can push it 
for you if you like.



---

** [issues:#1493] Problem with horizontal beams**

**Status:** Started
**Created:** Wed Jan 26, 2011 12:21 PM UTC by Anonymous
**Last Updated:** Mon Feb 12, 2018 05:40 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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5273 Replace number-or-markup? with integer-or-markup?

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> countdown
- **Comment**:

Patch on countdown for Feb 15th



---

** [issues:#5273] Replace number-or-markup? with integer-or-markup?**

**Status:** Started
**Created:** Sun Feb 11, 2018 01:24 PM UTC by Dan Eble
**Last Updated:** Mon Feb 12, 2018 02:52 PM 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] Re: #1493 Problem with horizontal beams

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Hi James,
Patch file attached - please push it for me.
Thanks,
Torsten


---

** [issues:#1493] Problem with horizontal beams**

**Status:** Started
**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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #1493 Problem with horizontal beams

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **labels**:  --> Fixed_2_21_0
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

~~~
issue #1493: Problem with horizontal beams staging
author  Torsten Hämmerle  
Mon, 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

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5274 GSoC 2018: Two new project ideas

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **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] #5273 Replace number-or-markup? with integer-or-markup?

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **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 Eble 
Date:   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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [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] #5275 Avoid duplicate rehearsal marks in regression tests

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- 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] #5276 Stop spurious bar lines for large \partial commands

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [issues:#5276] Stop spurious bar lines for large \partial commands**

**Status:** Started
**Created:** Mon Feb 19, 2018 08:55 PM UTC by David Kastrup
**Last Updated:** Mon Feb 19, 2018 08:55 PM UTC
**Owner:** nobody


Stop spurious bar lines for large \partial commands

Previously \partial commands exceeding one bar of length led to
gratuitous bar lines inserted at multiples of the current bar length.
This stops the Default_bar_line_engraver from inserting bars in these
situations.  This allows using \partial for inserting large
intermediate bars without requiring meter changes.

http://codereview.appspot.com/336570043


---

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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Passes make, make check and a full make doc.

Reg test diff attached


Attachments:

- 
[Reg_test.png](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/9a9947df/a87e/attachment/Reg_test.png)
 (101.8 kB; image/png)


---

** [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 02:15 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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: new --> review



---

** [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:** Mon Feb 19, 2018 04:35 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] #5273 Replace number-or-markup? with integer-or-markup?

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push.



---

** [issues:#5273] Replace number-or-markup? with integer-or-markup?**

**Status:** Started
**Created:** Sun Feb 11, 2018 01:24 PM UTC by Dan Eble
**Last Updated:** Thu Feb 15, 2018 10:28 PM 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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

It's no problem Dan to re-run the test.

Passes make, make check and a full make doc.




Attachments:

- 
[Reg_test_21Feb.png](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/9a9947df/6929/attachment/Reg_test_21Feb.png)
 (105.1 kB; image/png)


---

** [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:** Tue Feb 20, 2018 05:53 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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Needs**:  -->  
- **Patch**: new --> review
- **Type**:  --> Enhancement



---

** [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:** Wed Feb 21, 2018 01:20 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] #5276 Stop spurious bar lines for large \partial commands

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Passes make, make check and a full make doc.

Reg test diff here - https://cloud.indie.host/s/rMFVfrFz17aI1Ng (~350kb zip)


---

** [issues:#5276] Stop spurious bar lines for large \partial commands**

**Status:** Started
**Created:** Mon Feb 19, 2018 08:55 PM UTC by David Kastrup
**Last Updated:** Tue Feb 20, 2018 07:41 PM UTC
**Owner:** David Kastrup


Stop spurious bar lines for large \partial commands

Previously \partial commands exceeding one bar of length led to
gratuitous bar lines inserted at multiples of the current bar length.
This stops the Default_bar_line_engraver from inserting bars in these
situations.  This allows using \partial for inserting large
intermediate bars without requiring meter changes.

http://codereview.appspot.com/336570043


---

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] #5276 Stop spurious bar lines for large \partial commands

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Needs**:  -->  
- **Patch**: new --> review
- **Type**:  --> Enhancement



---

** [issues:#5276] Stop spurious bar lines for large \partial commands**

**Status:** Started
**Created:** Mon Feb 19, 2018 08:55 PM UTC by David Kastrup
**Last Updated:** Wed Feb 21, 2018 06:28 PM UTC
**Owner:** David Kastrup


Stop spurious bar lines for large \partial commands

Previously \partial commands exceeding one bar of length led to
gratuitous bar lines inserted at multiples of the current bar length.
This stops the Default_bar_line_engraver from inserting bars in these
situations.  This allows using \partial for inserting large
intermediate bars without requiring meter changes.

http://codereview.appspot.com/336570043


---

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] #5276 Stop spurious bar lines for large \partial commands

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> needs_work
- **Comment**:

Oh, it's only every \partial at the beginning of a piece now.  Sorry for this.  
I think I should really create a regtest to go along with this and make sure at 
least the regtest works fine.



---

** [issues:#5276] Stop spurious bar lines for large \partial commands**

**Status:** Started
**Created:** Mon Feb 19, 2018 08:55 PM UTC by David Kastrup
**Last Updated:** Wed Feb 21, 2018 06:44 PM UTC
**Owner:** David Kastrup


Stop spurious bar lines for large \partial commands

Previously \partial commands exceeding one bar of length led to
gratuitous bar lines inserted at multiples of the current bar length.
This stops the Default_bar_line_engraver from inserting bars in these
situations.  This allows using \partial for inserting large
intermediate bars without requiring meter changes.

http://codereview.appspot.com/336570043


---

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] #5277 add glyphs for 256th, 512th and 1024th flags and rests

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

*2nd attempt - previous post deleted because of messed-up formatting*

Hi Malte

Good work!

* consequent and logical extension of the existing flags and rests
* by adapting some Metafont parameters (most notably flagspace, 
hip_depth_ratio) you managed to maintain the overall "look and feel" even of 
the downstem flags.
* The dot position problem is a mystery yet unsolved and is not "your" new 
flags' fault.
* Stem alignment etc ok
* Stem lengths ok
* Downstem inner flag/notehead positioning consistent 
* Rest positioning ok

**Donwstem flags**
The inner flag has to cope with the notehead, that's why they are slightly 
wider than the upstem flags. This difference in width gradually vanishes 
further away from the notehead, that's why the fiddling with flag parameters in 
Metafont is needed.
I've played around with the values myself and came to about the same solutions 
as you did.
The differences are barely visible, and, in typography, if it looks equal, it 
is equal.

All the best,
Torsten


---

** [issues:#5277] add glyphs for 256th, 512th and 1024th flags and rests**

**Status:** Started
**Created:** Wed Feb 21, 2018 02:15 PM UTC by Malte Meyn
**Last Updated:** Wed Feb 21, 2018 10:16 PM UTC
**Owner:** Malte Meyn


add glyphs for 256th, 512th and 1024th flags and rests

This post on lilypond-user asks for small rhythmic values (though it doesn’t 
explicitely mention rests and unbeamed/flagged notes): 
https://lists.gnu.org/archive/html/lilypond-user/2018-02/msg00614.html

1024th is the shortest duration suggested by SMuFL.

Needs special focus in review:
• forms of downstem flags

Needs improvement but I don’t know how to do:
• dot position for very short rests (see regtest)

Contains also:
• adjust stem lengths for 256th, 512th, and 1024th flags
• Notation Reference: change shortest value from 128th to 1024th
• add very short rests to regtest

http://codereview.appspot.com/336590043


---

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] #5277 add glyphs for 256th, 512th and 1024th flags and rests

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Hi Malte,
good work!
* consequent and logical extension of the existing flags and rests
* by adapting some Metafont parameters (most notably flagspace, 
hip_depth_ratio) you managed to maintain the overall "look and feel" even of 
the downstem flags.
* The dot position problem is a mystery yet unsolved and is not "your" new 
flags' falut.
* Stem alignment etc ok
* Stem lengths ok
* Downstem inner flag/notehead positioning consistent 
* Rest positioning ok

**Donwstem flags**
The inner flag has to cope with the notehead, that's why they are slightly 
wider than the upstem flags. This difference in width gradually vanishes 
further away from the notehead, that's why the fiddling with flag parameters in 
Metafont is needed.
I've played around with the values myself and came to about the same solutions 
as you did.
The differences are barely visible, and, in typography, if it looks equal, it 
is equal.

All the best,
Torsten




---

** [issues:#5277] add glyphs for 256th, 512th and 1024th flags and rests**

**Status:** Started
**Created:** Wed Feb 21, 2018 02:15 PM UTC by Malte Meyn
**Last Updated:** Wed Feb 21, 2018 02:15 PM UTC
**Owner:** Malte Meyn


add glyphs for 256th, 512th and 1024th flags and rests

This post on lilypond-user asks for small rhythmic values (though it doesn’t 
explicitely mention rests and unbeamed/flagged notes): 
https://lists.gnu.org/archive/html/lilypond-user/2018-02/msg00614.html

1024th is the shortest duration suggested by SMuFL.

Needs special focus in review:
• forms of downstem flags

Needs improvement but I don’t know how to do:
• dot position for very short rests (see regtest)

Contains also:
• adjust stem lengths for 256th, 512th, and 1024th flags
• Notation Reference: change shortest value from 128th to 1024th
• add very short rests to regtest

http://codereview.appspot.com/336590043


---

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] #5277 add glyphs for 256th, 512th and 1024th flags and rests

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- Description has changed:

Diff:







- Attachments has changed:

Diff:



--- old
+++ new
@@ -0,0 +1 @@
+reg_test_diff_22FEB.png (70.3 kB; image/png)



- **Needs**:  -->  
- **Patch**: new --> review
- **Comment**:

Passes make, make check and a full make doc - some comments on Rietveld too - 
reg test diff attached



---

** [issues:#5277] add glyphs for 256th, 512th and 1024th flags and rests**

**Status:** Started
**Created:** Wed Feb 21, 2018 02:15 PM UTC by Malte Meyn
**Last Updated:** Wed Feb 21, 2018 10:19 PM UTC
**Owner:** Malte Meyn
**Attachments:**

- 
[reg_test_diff_22FEB.png](https://sourceforge.net/p/testlilyissues/issues/5277/attachment/reg_test_diff_22FEB.png)
 (70.3 kB; image/png)


add glyphs for 256th, 512th and 1024th flags and rests

This post on lilypond-user asks for small rhythmic values (though it doesn’t 
explicitely mention rests and unbeamed/flagged notes): 
https://lists.gnu.org/archive/html/lilypond-user/2018-02/msg00614.html

1024th is the shortest duration suggested by SMuFL.

Needs special focus in review:
• forms of downstem flags

Needs improvement but I don’t know how to do:
• dot position for very short rests (see regtest)

Contains also:
• adjust stem lengths for 256th, 512th, and 1024th flags
• Notation Reference: change shortest value from 128th to 1024th
• add very short rests to regtest

http://codereview.appspot.com/336590043


---

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] #2199 Mark_engraver in StaffGroup misplaces marks at top of Score

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **assigned_to**: Dan Eble



---

** [issues:#2199] Mark_engraver in StaffGroup misplaces marks at top of Score**

**Status:** Accepted
**Created:** Sat Jan 07, 2012 11:50 AM UTC by Anonymous
**Last Updated:** Wed Sep 09, 2015 02:06 PM UTC
**Owner:** Dan Eble


*Originally created by:* *anonymous

*Originally created by:* 
[janek.li...@gmail.com](http://code.google.com/u/100525084317801742451/)

This has been reported 
[two](http://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00395.html) 
[times](http://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00111.html) 
in lilypond-user.

"Mark\_engraver" or "Metronome\_mark\_engraver" should be moveable to the
StaffGroup \(and alike: GrandStaff, ChoirStaff, etc.\) context \(and work\!\!\).


:::TeX
 Snippet

\version "2.13.24"

music = \repeat unfold 5 {
  \repeat unfold 5 c'1
  \mark \default
}

\score {
  <<
\new Staff {
  s1*0^"Marks should NOT be above this Staff (i.e. above the Score)!"
  \music
}
\new StaffGroup {
  <<
\new Staff {
  s1*0^"Marks should be above the StaffGroup"
  \music
}
\new Staff {
  \music
}
  >>
}
  >>
  \layout {
\context {
  \Score
  \remove "Mark_engraver"
  % same for "Metronome_mark_engraver"
  \remove "Staff_collecting_engraver"
}
\context {
  \StaffGroup
  \consists "Mark_engraver"
  \consists "Staff_collecting_engraver"
  % same for "Metronome_mark_engraver"
}
  }
}


%% Note that it works if we move it to the Staff level (instead of the
%% StaffGroup).  But engravers at the StaffGroup level is required for
%% example if the first staff of the StaffGroup is removed, using
%% \RemoveEmptyStaves (Frenched score).

\score {
  <<
\new Staff {
  s1*0^"Marks are not above the score"
  \music
}
\new StaffGroup {
  <<
\new Staff \with {
  \consists "Mark_engraver"
} {
  s1*0^"Marks are above this Staff"
  \music
}
\new Staff {
  \music
}
  >>
}
  >>
  \layout {
\context {
  \Score
  \remove "Mark_engraver"
  \remove "Staff_collecting_engraver"
}
\context {
  \Staff
  % \consists "Mark_engraver"
  % We add this engraver to the second Staff only
  \consists "Staff_collecting_engraver"
}
  }
}

 End of the snippet



---

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] Re: #5277 add glyphs for 256th, 512th and 1024th flags and rests

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

I'll have to admit that when commenting about dot column placement, I didn't 
take a closer look and only had the weird multi-voice effect random placement 
effect in mind.

The dot placement for the new ultra-short rests has to be adapted, too, because 
currently, the dots will be placed too low (see attachment).
I'll drop a note in rieveld (scm/output-lib.scm has to be adapted for duration 
logs > 7).

All the best
Torsten


---

** [issues:#5277] add glyphs for 256th, 512th and 1024th flags and rests**

**Status:** Started
**Created:** Wed Feb 21, 2018 02:15 PM UTC by Malte Meyn
**Last Updated:** Fri Feb 23, 2018 11:08 AM UTC
**Owner:** Malte Meyn
**Attachments:**

- 
[reg_test_diff_22FEB.png](https://sourceforge.net/p/testlilyissues/issues/5277/attachment/reg_test_diff_22FEB.png)
 (70.3 kB; image/png)


add glyphs for 256th, 512th and 1024th flags and rests

This post on lilypond-user asks for small rhythmic values (though it doesn’t 
explicitely mention rests and unbeamed/flagged notes): 
https://lists.gnu.org/archive/html/lilypond-user/2018-02/msg00614.html

1024th is the shortest duration suggested by SMuFL.

Needs special focus in review:
• forms of downstem flags

Needs improvement but I don’t know how to do:
• dot position for very short rests (see regtest)

Contains also:
• adjust stem lengths for 256th, 512th, and 1024th flags
• Notation Reference: change shortest value from 128th to 1024th
• add very short rests to regtest

http://codereview.appspot.com/336590043


---

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] #5277 add glyphs for 256th, 512th and 1024th flags and rests

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> needs_work



---

** [issues:#5277] add glyphs for 256th, 512th and 1024th flags and rests**

**Status:** Started
**Created:** Wed Feb 21, 2018 02:15 PM UTC by Malte Meyn
**Last Updated:** Thu Feb 22, 2018 02:39 PM UTC
**Owner:** Malte Meyn
**Attachments:**

- 
[reg_test_diff_22FEB.png](https://sourceforge.net/p/testlilyissues/issues/5277/attachment/reg_test_diff_22FEB.png)
 (70.3 kB; image/png)


add glyphs for 256th, 512th and 1024th flags and rests

This post on lilypond-user asks for small rhythmic values (though it doesn’t 
explicitely mention rests and unbeamed/flagged notes): 
https://lists.gnu.org/archive/html/lilypond-user/2018-02/msg00614.html

1024th is the shortest duration suggested by SMuFL.

Needs special focus in review:
• forms of downstem flags

Needs improvement but I don’t know how to do:
• dot position for very short rests (see regtest)

Contains also:
• adjust stem lengths for 256th, 512th, and 1024th flags
• Notation Reference: change shortest value from 128th to 1024th
• add very short rests to regtest

http://codereview.appspot.com/336590043


---

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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> countdown
- **Comment**:

Patch on countdown for Feb 27th



---

** [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:** Wed Feb 21, 2018 01:20 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] #2199 Mark_engraver in StaffGroup misplaces marks at top of Score

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Issue 2199: align outside-staff grobs vertically in staff groups

In any context in which a Vertical_align_engraver creates a
StaffGrouper, it also sees to it that all outside-staff grobs created
in the immediate context become y-axis children of the StaffGrouper.

Any such grobs which are later processed by the after-line-breaking
callback ly:side-position-interface::move_to_extremal_staff are moved
to the extremal staff of the group, not of the entire system.

http://codereview.appspot.com/331650043


---

** [issues:#2199] Mark_engraver in StaffGroup misplaces marks at top of Score**

**Status:** Started
**Created:** Sat Jan 07, 2012 11:50 AM UTC by Anonymous
**Last Updated:** Sun Feb 25, 2018 03:16 AM UTC
**Owner:** Dan Eble


*Originally created by:* *anonymous

*Originally created by:* 
[janek.li...@gmail.com](http://code.google.com/u/100525084317801742451/)

This has been reported 
[two](http://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00395.html) 
[times](http://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00111.html) 
in lilypond-user.

"Mark\_engraver" or "Metronome\_mark\_engraver" should be moveable to the
StaffGroup \(and alike: GrandStaff, ChoirStaff, etc.\) context \(and work\!\!\).


:::TeX
 Snippet

\version "2.13.24"

music = \repeat unfold 5 {
  \repeat unfold 5 c'1
  \mark \default
}

\score {
  <<
\new Staff {
  s1*0^"Marks should NOT be above this Staff (i.e. above the Score)!"
  \music
}
\new StaffGroup {
  <<
\new Staff {
  s1*0^"Marks should be above the StaffGroup"
  \music
}
\new Staff {
  \music
}
  >>
}
  >>
  \layout {
\context {
  \Score
  \remove "Mark_engraver"
  % same for "Metronome_mark_engraver"
  \remove "Staff_collecting_engraver"
}
\context {
  \StaffGroup
  \consists "Mark_engraver"
  \consists "Staff_collecting_engraver"
  % same for "Metronome_mark_engraver"
}
  }
}


%% Note that it works if we move it to the Staff level (instead of the
%% StaffGroup).  But engravers at the StaffGroup level is required for
%% example if the first staff of the StaffGroup is removed, using
%% \RemoveEmptyStaves (Frenched score).

\score {
  <<
\new Staff {
  s1*0^"Marks are not above the score"
  \music
}
\new StaffGroup {
  <<
\new Staff \with {
  \consists "Mark_engraver"
} {
  s1*0^"Marks are above this Staff"
  \music
}
\new Staff {
  \music
}
  >>
}
  >>
  \layout {
\context {
  \Score
  \remove "Mark_engraver"
  \remove "Staff_collecting_engraver"
}
\context {
  \Staff
  % \consists "Mark_engraver"
  % We add this engraver to the second Staff only
  \consists "Staff_collecting_engraver"
}
  }
}

 End of the snippet



---

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] Re: #2199 Mark_engraver in StaffGroup misplaces marks at top of Score

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

If there is more wrong than the dot placement, I would be grateful for some 
clarification.


---

** [issues:#2199] Mark_engraver in StaffGroup misplaces marks at top of Score**

**Status:** Started
**Created:** Sat Jan 07, 2012 11:50 AM UTC by Anonymous
**Last Updated:** Sun Feb 25, 2018 12:06 PM UTC
**Owner:** Dan Eble


*Originally created by:* *anonymous

*Originally created by:* 
[janek.li...@gmail.com](http://code.google.com/u/100525084317801742451/)

This has been reported 
[two](http://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00395.html) 
[times](http://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00111.html) 
in lilypond-user.

"Mark\_engraver" or "Metronome\_mark\_engraver" should be moveable to the
StaffGroup \(and alike: GrandStaff, ChoirStaff, etc.\) context \(and work\!\!\).


:::TeX
 Snippet

\version "2.13.24"

music = \repeat unfold 5 {
  \repeat unfold 5 c'1
  \mark \default
}

\score {
  <<
\new Staff {
  s1*0^"Marks should NOT be above this Staff (i.e. above the Score)!"
  \music
}
\new StaffGroup {
  <<
\new Staff {
  s1*0^"Marks should be above the StaffGroup"
  \music
}
\new Staff {
  \music
}
  >>
}
  >>
  \layout {
\context {
  \Score
  \remove "Mark_engraver"
  % same for "Metronome_mark_engraver"
  \remove "Staff_collecting_engraver"
}
\context {
  \StaffGroup
  \consists "Mark_engraver"
  \consists "Staff_collecting_engraver"
  % same for "Metronome_mark_engraver"
}
  }
}


%% Note that it works if we move it to the Staff level (instead of the
%% StaffGroup).  But engravers at the StaffGroup level is required for
%% example if the first staff of the StaffGroup is removed, using
%% \RemoveEmptyStaves (Frenched score).

\score {
  <<
\new Staff {
  s1*0^"Marks are not above the score"
  \music
}
\new StaffGroup {
  <<
\new Staff \with {
  \consists "Mark_engraver"
} {
  s1*0^"Marks are above this Staff"
  \music
}
\new Staff {
  \music
}
  >>
}
  >>
  \layout {
\context {
  \Score
  \remove "Mark_engraver"
  \remove "Staff_collecting_engraver"
}
\context {
  \Staff
  % \consists "Mark_engraver"
  % We add this engraver to the second Staff only
  \consists "Staff_collecting_engraver"
}
  }
}

 End of the snippet



---

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] Re: #2199 Mark_engraver in StaffGroup misplaces marks at top of Score

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Hi Dan,
rest-dot-position.ly will always pop up until the cause for random behaviour is 
fixed.
See:
https://sourceforge.net/p/testlilyissues/issues/5226/
Here the cause is hunted down:
https://sourceforge.net/p/testlilyissues/issues/5217/#125c




---

** [issues:#2199] Mark_engraver in StaffGroup misplaces marks at top of Score**

**Status:** Started
**Created:** Sat Jan 07, 2012 11:50 AM UTC by Anonymous
**Last Updated:** Mon Feb 26, 2018 08:20 AM UTC
**Owner:** Dan Eble


align outside-staff grobs vertically in staff groups

In any context in which a Vertical_align_engraver creates a
StaffGrouper, it also sees to it that all outside-staff grobs created
in the immediate context become y-axis children of the StaffGrouper.

Any such grobs which are later processed by the after-line-breaking
callback ly:side-position-interface::move_to_extremal_staff are moved
to the extremal staff of the group, not of the entire system.

http://codereview.appspot.com/331650043



*Originally created by:* *anonymous

*Originally created by:* 
[janek.li...@gmail.com](http://code.google.com/u/100525084317801742451/)

This has been reported 
[two](http://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00395.html) 
[times](http://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00111.html) 
in lilypond-user.

"Mark\_engraver" or "Metronome\_mark\_engraver" should be moveable to the
StaffGroup \(and alike: GrandStaff, ChoirStaff, etc.\) context \(and work\!\!\).


:::TeX
 Snippet

\version "2.13.24"

music = \repeat unfold 5 {
  \repeat unfold 5 c'1
  \mark \default
}

\score {
  <<
\new Staff {
  s1*0^"Marks should NOT be above this Staff (i.e. above the Score)!"
  \music
}
\new StaffGroup {
  <<
\new Staff {
  s1*0^"Marks should be above the StaffGroup"
  \music
}
\new Staff {
  \music
}
  >>
}
  >>
  \layout {
\context {
  \Score
  \remove "Mark_engraver"
  % same for "Metronome_mark_engraver"
  \remove "Staff_collecting_engraver"
}
\context {
  \StaffGroup
  \consists "Mark_engraver"
  \consists "Staff_collecting_engraver"
  % same for "Metronome_mark_engraver"
}
  }
}


%% Note that it works if we move it to the Staff level (instead of the
%% StaffGroup).  But engravers at the StaffGroup level is required for
%% example if the first staff of the StaffGroup is removed, using
%% \RemoveEmptyStaves (Frenched score).

\score {
  <<
\new Staff {
  s1*0^"Marks are not above the score"
  \music
}
\new StaffGroup {
  <<
\new Staff \with {
  \consists "Mark_engraver"
} {
  s1*0^"Marks are above this Staff"
  \music
}
\new Staff {
  \music
}
  >>
}
  >>
  \layout {
\context {
  \Score
  \remove "Mark_engraver"
  \remove "Staff_collecting_engraver"
}
\context {
  \Staff
  % \consists "Mark_engraver"
  % We add this engraver to the second Staff only
  \consists "Staff_collecting_engraver"
}
  }
}

 End of the snippet



---

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] #5282 Web: update wording on Bug reports page

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Maybe mention the Nabble interface for bug-lilypond?
http://lilypond.1069038.n5.nabble.com/Bugs-f58488.html


---

** [issues:#5282] Web: update wording on Bug reports page**

**Status:** Started
**Created:** Mon Feb 26, 2018 06:43 PM UTC by Simon Albrecht
**Last Updated:** Mon Feb 26, 2018 06:44 PM UTC
**Owner:** Simon Albrecht


Web: update wording on Bug reports page

The current wording is somewhat mishapen since the option
of using the gmane interface was just removed without adapting
the context.

http://codereview.appspot.com/331660043


---

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] #5282 Web: update wording on Bug reports page

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [issues:#5282] Web: update wording on Bug reports page**

**Status:** Started
**Created:** Mon Feb 26, 2018 06:43 PM UTC by Simon Albrecht
**Last Updated:** Mon Feb 26, 2018 06:43 PM UTC
**Owner:** nobody


Web: update wording on Bug reports page

The current wording is somewhat mishapen since the option
of using the gmane interface was just removed without adapting
the context.

http://codereview.appspot.com/331660043


---

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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: countdown --> push
- **Comment**:

Patch counted down - please push



---

** [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:** Sat Feb 24, 2018 03:16 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] #2199 Mark_engraver in StaffGroup misplaces marks at top of Score

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> countdown
- **Comment**:

Patch on countdown for March 2nd.



---

** [issues:#2199] Mark_engraver in StaffGroup misplaces marks at top of Score**

**Status:** Started
**Created:** Sat Jan 07, 2012 11:50 AM UTC by Anonymous
**Last Updated:** Mon Feb 26, 2018 08:20 AM UTC
**Owner:** Dan Eble


align outside-staff grobs vertically in staff groups

In any context in which a Vertical_align_engraver creates a
StaffGrouper, it also sees to it that all outside-staff grobs created
in the immediate context become y-axis children of the StaffGrouper.

Any such grobs which are later processed by the after-line-breaking
callback ly:side-position-interface::move_to_extremal_staff are moved
to the extremal staff of the group, not of the entire system.

http://codereview.appspot.com/331650043



*Originally created by:* *anonymous

*Originally created by:* 
[janek.li...@gmail.com](http://code.google.com/u/100525084317801742451/)

This has been reported 
[two](http://lists.gnu.org/archive/html/lilypond-user/2011-12/msg00395.html) 
[times](http://lists.gnu.org/archive/html/lilypond-user/2012-01/msg00111.html) 
in lilypond-user.

"Mark\_engraver" or "Metronome\_mark\_engraver" should be moveable to the
StaffGroup \(and alike: GrandStaff, ChoirStaff, etc.\) context \(and work\!\!\).


:::TeX
 Snippet

\version "2.13.24"

music = \repeat unfold 5 {
  \repeat unfold 5 c'1
  \mark \default
}

\score {
  <<
\new Staff {
  s1*0^"Marks should NOT be above this Staff (i.e. above the Score)!"
  \music
}
\new StaffGroup {
  <<
\new Staff {
  s1*0^"Marks should be above the StaffGroup"
  \music
}
\new Staff {
  \music
}
  >>
}
  >>
  \layout {
\context {
  \Score
  \remove "Mark_engraver"
  % same for "Metronome_mark_engraver"
  \remove "Staff_collecting_engraver"
}
\context {
  \StaffGroup
  \consists "Mark_engraver"
  \consists "Staff_collecting_engraver"
  % same for "Metronome_mark_engraver"
}
  }
}


%% Note that it works if we move it to the Staff level (instead of the
%% StaffGroup).  But engravers at the StaffGroup level is required for
%% example if the first staff of the StaffGroup is removed, using
%% \RemoveEmptyStaves (Frenched score).

\score {
  <<
\new Staff {
  s1*0^"Marks are not above the score"
  \music
}
\new StaffGroup {
  <<
\new Staff \with {
  \consists "Mark_engraver"
} {
  s1*0^"Marks are above this Staff"
  \music
}
\new Staff {
  \music
}
  >>
}
  >>
  \layout {
\context {
  \Score
  \remove "Mark_engraver"
  \remove "Staff_collecting_engraver"
}
\context {
  \Staff
  % \consists "Mark_engraver"
  % We add this engraver to the second Staff only
  \consists "Staff_collecting_engraver"
}
  }
}

 End of the snippet



---

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] #5282 Web: update wording on Bug reports page

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Stop assuming the reader knew about gmane.

http://codereview.appspot.com/331660043


---

** [issues:#5282] Web: update wording on Bug reports page**

**Status:** Started
**Created:** Mon Feb 26, 2018 06:43 PM UTC by Simon Albrecht
**Last Updated:** Tue Feb 27, 2018 11:09 AM UTC
**Owner:** Simon Albrecht


Web: update wording on Bug reports page

The current wording is somewhat mishapen since the option
of using the gmane interface was just removed without adapting
the context.

http://codereview.appspot.com/331660043


---

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] #5276 Stop spurious bar lines for large \partial commands

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Passes make, make check and a full make doc.

A lot of reg test diffs

You can download them from here

https://cloud.indie.host/s/2Jm75jHAKu8oxcq (~9mb zip file)


---

** [issues:#5276] Stop spurious bar lines for large \partial commands**

**Status:** Started
**Created:** Mon Feb 19, 2018 08:55 PM UTC by David Kastrup
**Last Updated:** Mon Feb 19, 2018 08:55 PM UTC
**Owner:** David Kastrup


Stop spurious bar lines for large \partial commands

Previously \partial commands exceeding one bar of length led to
gratuitous bar lines inserted at multiples of the current bar length.
This stops the Default_bar_line_engraver from inserting bars in these
situations.  This allows using \partial for inserting large
intermediate bars without requiring meter changes.

http://codereview.appspot.com/336570043


---

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] #5282 Web: update wording on Bug reports page

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- Description has changed:

Diff:







- **Needs**:  -->  
- **Patch**: new --> review
- **Type**:  --> Documentation
- **Comment**:

Passes make, make check and a full make doc.



---

** [issues:#5282] Web: update wording on Bug reports page**

**Status:** Started
**Created:** Mon Feb 26, 2018 06:43 PM UTC by Simon Albrecht
**Last Updated:** Tue Feb 27, 2018 11:09 AM UTC
**Owner:** Simon Albrecht


Web: update wording on Bug reports page

The current wording is somewhat mishapen since the option
of using the gmane interface was just removed without adapting
the context.

http://codereview.appspot.com/331660043


---

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] Re: #5276 Stop spurious bar lines for large \partial commands

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

David, never worry about that. I understand the full make test-baseline/check 
is rather an arduous task for most devs.


---

** [issues:#5276] Stop spurious bar lines for large \partial commands**

**Status:** Started
**Created:** Mon Feb 19, 2018 08:55 PM UTC by David Kastrup
**Last Updated:** Tue Feb 20, 2018 07:41 PM UTC
**Owner:** David Kastrup


Stop spurious bar lines for large \partial commands

Previously \partial commands exceeding one bar of length led to
gratuitous bar lines inserted at multiples of the current bar length.
This stops the Default_bar_line_engraver from inserting bars in these
situations.  This allows using \partial for inserting large
intermediate bars without requiring meter changes.

http://codereview.appspot.com/336570043


---

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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **labels**:  --> 2_21_0
- **status**: Started --> Fixed
- **Patch**: push -->  
- **Comment**:

~~~

author  Urs Liska 
Mon, 12 Feb 2018 18:23:41 + (19:23 +0100)
committer   Urs Liska 
Mon, 19 Feb 2018 09:35:05 + (10:35 +0100)
commit  00a7322aeea83fb3888dc871a1b19256dc4ce8dd
~~~



---

** [issues:#5274] GSoC 2018: Two new project ideas**

**Status:** Fixed
**Labels:** 2_21_0 
**Created:** Mon Feb 12, 2018 06:25 PM UTC by Urs Liska
**Last Updated:** Sun Feb 18, 2018 11:41 AM 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] #5277 add glyphs for 256th, 512th and 1024th flags and rests

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

---

** [issues:#5277] add glyphs for 256th, 512th and 1024th flags and rests**

**Status:** Started
**Created:** Wed Feb 21, 2018 02:15 PM UTC by Malte Meyn
**Last Updated:** Wed Feb 21, 2018 02:15 PM UTC
**Owner:** nobody


add glyphs for 256th, 512th and 1024th flags and rests

This post on lilypond-user asks for small rhythmic values (though it doesn’t 
explicitely mention rests and unbeamed/flagged notes): 
https://lists.gnu.org/archive/html/lilypond-user/2018-02/msg00614.html

1024th is the shortest duration suggested by SMuFL.

Needs special focus in review:
• forms of downstem flags

Needs improvement but I don’t know how to do:
• dot position for very short rests (see regtest)

Contains also:
• adjust stem lengths for 256th, 512th, and 1024th flags
• Notation Reference: change shortest value from 128th to 1024th
• add very short rests to regtest

http://codereview.appspot.com/336590043


---

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

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Fix expected value in test description

http://codereview.appspot.com/334510043


---

** [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:** Tue Feb 20, 2018 05:53 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] #5276 Stop spurious bar lines for large \partial commands

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- Description has changed:

Diff:







- **Needs**:  -->  
- **Patch**: new --> review



---

** [issues:#5276] Stop spurious bar lines for large \partial commands**

**Status:** Started
**Created:** Mon Feb 19, 2018 08:55 PM UTC by David Kastrup
**Last Updated:** Tue Feb 20, 2018 07:17 PM UTC
**Owner:** David Kastrup


Stop spurious bar lines for large \partial commands

Previously \partial commands exceeding one bar of length led to
gratuitous bar lines inserted at multiples of the current bar length.
This stops the Default_bar_line_engraver from inserting bars in these
situations.  This allows using \partial for inserting large
intermediate bars without requiring meter changes.

http://codereview.appspot.com/336570043


---

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] #5276 Stop spurious bar lines for large \partial commands

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

Fix non-bar when some material takes a multiple of whole measures

http://codereview.appspot.com/336570043


---

** [issues:#5276] Stop spurious bar lines for large \partial commands**

**Status:** Started
**Created:** Mon Feb 19, 2018 08:55 PM UTC by David Kastrup
**Last Updated:** Tue Feb 20, 2018 07:41 PM UTC
**Owner:** David Kastrup


Stop spurious bar lines for large \partial commands

Previously \partial commands exceeding one bar of length led to
gratuitous bar lines inserted at multiples of the current bar length.
This stops the Default_bar_line_engraver from inserting bars in these
situations.  This allows using \partial for inserting large
intermediate bars without requiring meter changes.

http://codereview.appspot.com/336570043


---

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] #5276 Stop spurious bar lines for large \partial commands

[Auto mailings of changes to Lily Issues via Testlilyissues-auto]

- **Patch**: review --> needs_work
- **Type**: Enhancement --> Defect
- **Comment**:

Oh wow, this looks really bad.  Sorry for not testing more thoroughly: putting 
down a test baseline and then making a comparison is such a large task for my 
computer...



---

** [issues:#5276] Stop spurious bar lines for large \partial commands**

**Status:** Started
**Created:** Mon Feb 19, 2018 08:55 PM UTC by David Kastrup
**Last Updated:** Tue Feb 20, 2018 07:18 PM UTC
**Owner:** David Kastrup


Stop spurious bar lines for large \partial commands

Previously \partial commands exceeding one bar of length led to
gratuitous bar lines inserted at multiples of the current bar length.
This stops the Default_bar_line_engraver from inserting bars in these
situations.  This allows using \partial for inserting large
intermediate bars without requiring meter changes.

http://codereview.appspot.com/336570043


---

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