[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5162 Some hooks useful for video production

2017-07-29 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto
- **Patch**: review --> needs_work - **Comment**: Setting this back to 'needs_work' --- ** [issues:#5162] Some hooks useful for video production** **Status:** Started **Created:** Tue Jul 25, 2017 05:48 PM UTC by Knut Petersen **Last Updated:** Wed Jul 26, 2017 11:51 AM UTC **Owner:** Knut

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5162 Some hooks useful for video production

2017-07-26 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto
Well, not every simple solution is > far too ad-hoc. I believe that KISS is still one of the most important priciples. It is evident that the proposed change to color? and setcolor cannot harm any existing code as lilyponds behaviour does not change unless overloaded-rgb? is set to #t. It

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5162 Some hooks useful for video production

2017-07-25 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto
You are missing a Rietveld review allowing for commenting on the patch details. At any rate, I think this approach is far too ad-hoc. You'd not get it accepted in the Linux kernel (which you claim to be your metric). I rather propose that you instead allow color to be a list starting with a

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5162 Some hooks useful for video production

2017-07-25 Thread Auto mailings of changes to Lily Issues via Testlilyissues-auto
--- ** [issues:#5162] Some hooks useful for video production** **Status:** New **Created:** Tue Jul 25, 2017 05:48 PM UTC by Knut Petersen **Last Updated:** Tue Jul 25, 2017 05:48 PM UTC **Owner:** Knut Petersen **Attachments:** -