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

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
Issue 5621: Improve rehearsal mark position at beginning of staff This is a work in progress. RehearsalMark uses a callback for self-alignment-X that yields the opposite of the direction specified by the anchor grob. I don't know if there should be some unpure-pure stuff involved. It looks

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5641 Drop undocumented lilymidi and lilysong

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
lilymidi works, its man page is sufficient as its documentation (as opposed to that of lilysong) and I frequently use it for dumping midi files. One could mention it in the usage guide but it's functional as well as in active use. --- ** [issues:#5641] Drop undocumented lilymidi and

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5641 Drop undocumented lilymidi and lilysong

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
--- ** [issues:#5641] Drop undocumented lilymidi and lilysong** **Status:** Started **Created:** Sat Dec 14, 2019 02:19 PM UTC by Jonas Hahnfeld **Last Updated:** Sat Dec 14, 2019 02:19 PM UTC **Owner:** nobody Drop undocumented lilymidi and lilysong Both have been introduced by commit

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

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
In case we want to do this, I've submitted #5641 to remove both lilysong and lilymidi. Neither of them is mentioned in the documentation and I don't see any tests to make sure they actually work. I found `elisp/lilypond-song.el` to be related in that it call lilysong, so I'm proposing to remove

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: Ticket 1245 discussion

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
That animation link is dead. All we have is the two PDF files. The first of those is not related to LilyPond and just contains a basic sketch of an input file for festival. --- ** [issues:#1245] festival song output is completely undocumented** **Status:** Accepted **Labels:** Frog

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5640 Fix regtests about Footnote

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- **Patch**: needs_work --> new - **Comment**: Let me check that again - I just spotted I didn't have a clean tree. --- ** [issues:#5640] Fix regtests about Footnote** **Status:** Started **Created:** Sat Dec 14, 2019 11:43 AM UTC by Thomas Morley **Last Updated:** Sat Dec 14, 2019 03:53 PM

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5640 Fix regtests about Footnote

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- Description has changed: Diff: - **Needs**: --> - **Patch**: new --> needs_work - **Comment**: Fails make check --snip-- ~~~ command failed: /home/james/lilypond-git/build/out/bin/lilypond \ -I /home/james/lilypond-git/input/regression -dbackend=eps

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5640 Fix regtests about Footnote

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- **Patch**: new --> needs_work - **Comment**: It fails as above. --- ** [issues:#5640] Fix regtests about Footnote** **Status:** Started **Created:** Sat Dec 14, 2019 11:43 AM UTC by Thomas Morley **Last Updated:** Sat Dec 14, 2019 04:04 PM UTC **Owner:** Thomas Morley Fix regtests about

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5641 Drop undocumented lilymidi and lilysong

2019-12-14 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 test-baseline and a full make doc, --- ** [issues:#5641] Drop undocumented lilymidi and lilysong** **Status:** Started **Created:** Sat Dec 14, 2019 02:19 PM UTC

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5640 Fix regtests about Footnote

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
--- ** [issues:#5640] Fix regtests about Footnote** **Status:** Started **Created:** Sat Dec 14, 2019 11:43 AM UTC by Thomas Morley **Last Updated:** Sat Dec 14, 2019 11:43 AM UTC **Owner:** nobody Fix regtests about Footnote Several regtest about FootnoteItem/Spanner contained overrides

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

2019-12-14 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 - **Type**: --> Enhancement - **Comment**: Passes make, make check and a full make doc. --- ** [issues:#5639] compile with -std=c++11** **Status:** Started **Created:** Sat Dec 14, 2019 04:51 AM

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

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
I haven't come across any and I'm absolutely fine with dropping it. Right now it's executed with `--help` during the build to generate the man page, so I wanted to fix it for Python 3. --- ** [issues:#5637] Port lilysong to subprocess module** **Status:** Started **Created:** Fri Dec 13,

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

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
And here’s the main example from that introduction—compiled with v2.19.83: :::TeX \include "oll-core/package.ily" \loadModules snippets #'((notation-snippets shaping-bezier-curves shapeII)) \paper { ragged-right = ##t indent = 0 } SUp = \change Staff = "up" SDn = \change Staff =

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

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
Though I would argue that in this case the left endpoint should be slightly further up. --- ** [issues:#5638] Improve Lilypond Automatic Slurs** **Status:** Accepted **Created:** Sat Dec 14, 2019 02:47 AM UTC by Carl Sorensen **Last Updated:** Sat Dec 14, 2019 08:30 AM UTC **Owner:** Carl

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

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
There are some examples in the documentation for shapeII in openlilylib: Attachments: - [Screenshot from 2019-12-14 09-29-33.png](https://sourceforge.net/p/testlilyissues/issues/_discuss/thread/af69f38bf3/c9d7/attachment/Screenshot%20from%202019-12-14%2009-29-33.png) (51.7 kB; image/png)

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

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
A very valiant undertaking—it would certainly be great to see improvement there! I don’t think many people have taken notice yet—you should certainly post to the user and/or devel list to ask for input. I haven’t done many projects myself that required extensive slur tweaking. --- **

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

2019-12-14 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto via Automated messages for lilypond development
- **status**: New --> Accepted --- ** [issues:#5638] Improve Lilypond Automatic Slurs** **Status:** Accepted **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