[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5639 compile with -std=c++11

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
fix typo https://codereview.appspot.com/553310045 --- ** [issues:#5639] compile with -std=c++11** **Status:** Started **Created:** Sat Dec 14, 2019 04:51 AM UTC by Dan Eble **Last Updated:** Sat Dec 14, 2019 04:55 AM UTC **Owner:** Dan Eble In addition to enabling C++11, I updated various

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5639 compile with -std=c++11

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
--- ** [issues:#5639] compile with -std=c++11** **Status:** Started **Created:** Sat Dec 14, 2019 04:51 AM UTC by Dan Eble **Last Updated:** Sat Dec 14, 2019 04:51 AM UTC **Owner:** nobody In addition to enabling C++11, I updated various things that I either remembered or found by searching

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5638 Improve Lilypond Automatic Slurs

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
--- ** [issues:#5638] Improve Lilypond Automatic Slurs** **Status:** New **Created:** Sat Dec 14, 2019 02:47 AM UTC by Carl Sorensen **Last Updated:** Sat Dec 14, 2019 02:47 AM UTC **Owner:** Carl Sorensen We currently need to do a fair amount of manual shaping of slurs. LilyPonsd is not

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #4943 Manual page breaking causing assertion failure

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
Some findings by Arnold can be found at: http://lilypond.1069038.n5.nabble.com/Issue-4934-analysis-indicates-new-issue-td224851.html regrettable there is a typo: 4934 <-> 4943 in his post. I'll quote it here entirely: > Hello, > as I got this assertion failure on multiple scores on Win7 (on

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5628 fix sign-compare warnings in flower unit tests

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- **labels**: --> Fixed_2_21_0 - **summary**: fix warnings compiling flower unit tests --> fix sign-compare warnings in flower unit tests - **status**: Started --> Fixed - **Patch**: countdown --> - **Type**: Enhancement --> Other - **Comment**: ```text commit

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5637 Port lilysong to subprocess module

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
Is lilysong actually documented somewhere other than its rather cryptic manual page? It seems like something that nobody uses or knows of and that may have stopped working decades ago. There does not seem to be any regtest associated with it. There is an `elisp/lilypond-song.el` but it's

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5637 Port lilysong to subprocess module

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- Description has changed: Diff: - **Needs**: --> - **Patch**: new --> review - **Comment**: Passes make, make check and a full make doc --- ** [issues:#5637] Port lilysong to subprocess module** **Status:** Started **Created:** Fri Dec 13, 2019 09:32 AM UTC by Jonas

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5310 find_top_context () instead of get_global_context ()

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- **Patch**: new --> review - **Comment**: Passes make, make check and a full make doc. --- ** [issues:#5310] find_top_context () instead of get_global_context ()** **Status:** Started **Created:** Sat Apr 21, 2018 08:39 PM UTC by Dan Eble **Last Updated:** Fri Dec 13, 2019 12:10 AM UTC

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5636 fix various warnings

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- **Patch**: new --> review - **Comment**: Passes make, make check and a full make doc. --- ** [issues:#5636] fix various warnings** **Status:** Started **Created:** Fri Dec 13, 2019 01:35 AM UTC by Dan Eble **Last Updated:** Fri Dec 13, 2019 01:41 AM UTC **Owner:** Dan Eble 1: int->vsize

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5637 Port lilysong to subprocess module

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
--- ** [issues:#5637] Port lilysong to subprocess module** **Status:** Started **Created:** Fri Dec 13, 2019 09:32 AM UTC by Jonas Hahnfeld **Last Updated:** Fri Dec 13, 2019 09:32 AM UTC **Owner:** nobody Port lilysong to subprocess module popen2 has been removed for Python 3.0.

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5628 fix warnings compiling flower unit tests

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
I'm fine with going to C++03 for now, that's definitely better than letting the compiler decide on the standard! --- ** [issues:#5628] fix warnings compiling flower unit tests** **Status:** Started **Created:** Wed Dec 04, 2019 10:38 PM UTC by Dan Eble **Last Updated:** Fri Dec 13, 2019 09:22

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5621 Improve positioning of rehearsal marks at the beginning of staff

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
Leaving on review for now as there seems to be some discussion going on, --- ** [issues:#5621] Improve positioning of rehearsal marks at the beginning of staff** **Status:** Started **Created:** Tue Nov 26, 2019 11:44 AM UTC by Werner LEMBERG **Last Updated:** Tue Dec 10, 2019 09:00 PM UTC

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5628 fix warnings compiling flower unit tests

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- **Patch**: review --> countdown - **Comment**: Patch on countdown for Dec 15th (if you think this needs to still be on review, based on the C++ discussions on Rietveld, then re-assign appropriately) --- ** [issues:#5628] fix warnings compiling flower unit tests** **Status:** Started

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5631 Introduce breakingRehearsalMarks for line-breaking RehearsalMarks

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
Still leaving on review for now as there seems to be some discussion going on, --- ** [issues:#5631] Introduce breakingRehearsalMarks for line-breaking RehearsalMarks** **Status:** Started **Created:** Sat Dec 07, 2019 02:48 PM UTC by Thomas Morley **Last Updated:** Tue Dec 10, 2019 06:31 AM

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5632 Replace string exceptions by RuntimeError

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- **Patch**: review --> countdown - **Comment**: Patch on couuntdown for Dec 15th. --- ** [issues:#5632] Replace string exceptions by RuntimeError** **Status:** Started **Created:** Sun Dec 08, 2019 08:28 PM UTC by Jonas Hahnfeld **Last Updated:** Wed Dec 11, 2019 01:43 PM UTC **Owner:**

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5633 musicxml: Replace new module by type() builtin

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- **Patch**: review --> countdown - **Comment**: Patch on couuntdown for Dec 15th. --- ** [issues:#5633] musicxml: Replace new module by type() builtin** **Status:** Started **Created:** Mon Dec 09, 2019 07:35 PM UTC by Jonas Hahnfeld **Last Updated:** Tue Dec 10, 2019 08:33 PM UTC

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5634 aclocal.m4: Avoid usage of Python

2019-12-13 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- **Patch**: review --> countdown - **Comment**: Patch on couuntdown for Dec 15th. --- ** [issues:#5634] aclocal.m4: Avoid usage of Python** **Status:** Started **Created:** Tue Dec 10, 2019 06:26 PM UTC by Jonas Hahnfeld **Last Updated:** Wed Dec 11, 2019 01:12 PM UTC **Owner:** Jonas