[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5764 flower: Drop unused functions

- **labels**: --> Fixed_2_21_0 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: ~~~ commit fd5b94378b7700f04c12f0d56095bc29450d0c5b Author: Jonas Hahnfeld AuthorDate: Sat Feb 15 16:49:26 2020 +0100 Commit: Jonas Hahnfeld CommitDate: Thu Feb 20 08:47:04 2020 +0100

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5763 flower: Delete old files

- **labels**: --> Fixed_2_21_0 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: ~~~ commit 45ebc21df25f62412f115aa4f0597c79d3aa6a52 Author: Jonas Hahnfeld AuthorDate: Sat Feb 15 16:25:11 2020 +0100 Commit: Jonas Hahnfeld CommitDate: Thu Feb 20 08:45:45 2020 +0100

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5770 Generate dependency files with Clang

- **labels**: --> Fixed_2_21_0 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: ~~~ commit 3fc41d7ac175fec152f577a1b324f7f0fdfd2a10 Author: Jonas Hahnfeld AuthorDate: Sun Feb 16 21:52:01 2020 +0100 Commit: Jonas Hahnfeld CommitDate: Thu Feb 20 08:47:59 2020 +0100

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5774 Remove LO extension from GSoC ideas list

- **labels**: --> Fixed_2_21_0 - **status**: Started --> Fixed - **Comment**: I've pushed this and set the "Fixed" label, but I'm not sure if I should have also changed the "Patch" to "Push". --- ** [issues:#5774] Remove LO extension from GSoC ideas list** **Status:** Fixed **Labels:** Fixe

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5776 Remove redundant checks with C++11

--- ** [issues:#5776] Remove redundant checks with C++11** **Status:** Started **Created:** Thu Feb 20, 2020 11:40 AM UTC by Jonas Hahnfeld **Last Updated:** Thu Feb 20, 2020 11:40 AM UTC **Owner:** nobody Remove redundant checks with C++11 Individual changes: 1) Drop check for std::vector:

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5776 Remove redundant checks with C++11

> 3) Drop check for explicit template instantiation > The define was unused and as far as I can tell, the code is valid C++ and should just always work. One thing that I have mused about at times is the separation of files flower/include/interval.tcc lily/include/smobs.tcc that makes sense for im

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5776 Remove redundant checks with C++11

One could argue that it still makes sense to kind of separate the declaration from the template implementation. I don't have a strong opinion here. [FWIW and totally unrelated to this issue (well, that's what I muse about): I tried to reduce the amount of templates in smobs.tcc at least twice. T

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

- **labels**: --> Fixed_2_21_0 - **status**: Started --> Fixed - **Patch**: push --> - **Comment**: ```text commit 6e6b834a5cd10f33d427da7253568216cc673e1f (origin/staging) Author: Dan Eble Date: Sat Feb 15 13:21:20 2020 -0500 Issue 5766/5: int->vsize to fix warning in pointer-group-int

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5777 Let flex handle the input stack

--- ** [issues:#5777] Let flex handle the input stack** **Status:** Started **Created:** Thu Feb 20, 2020 02:17 PM UTC by Jonas Hahnfeld **Last Updated:** Thu Feb 20, 2020 02:17 PM UTC **Owner:** nobody Let flex handle the input stack This requires at least flex 2.5.29 released in 2003. Pr

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5778 Implement Grob::event_cause, Grob::ultimate_event_cause

--- ** [issues:#5778] Implement Grob::event_cause, Grob::ultimate_event_cause** **Status:** Started **Created:** Thu Feb 20, 2020 03:11 PM UTC by David Kastrup **Last Updated:** Thu Feb 20, 2020 03:11 PM UTC **Owner:** nobody Implement Grob::event_cause, Grob::ultimate_event_cause Those wer

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5777 Let flex handle the input stack

As a hint: getting the input stack handling reasonably safe from tumbling into `ly/init.ly` for followup errors from parsing the main document was sort of a chore. There are comments around \maininput in that file reading like ~~~ $(if (ly:get-option 'include-settings) (ly:parser-include-stri

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] Re: #5777 Let flex handle the input stack

I tested EOFs in comments, strings, commands and contexts and all got me the same "syntax error, unexpected end of input" plus some extra ones for comments and strings. But with none of that, I was either able to escape main input nor trigger the rule `{ANY_CHAR}` as indicated in Rietveld... -

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5775 GSoC idea: Frescobaldi extension

- **labels**: --> Fixed_2_21_0 - **status**: Started --> Fixed - **Comment**: Now that GNU has been accepted for GSoC I've pushed to staging --- ** [issues:#5775] GSoC idea: Frescobaldi extension** **Status:** Fixed **Labels:** Fixed_2_21_0 **Created:** Wed Feb 19, 2020 06:09 PM UTC by Urs

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5778 Implement Grob::event_cause, Grob::ultimate_event_cause

- Description has changed: Diff: - **Needs**: --> - **Patch**: new --> review - **Comment**: Passes make. make check and a full make doc --- ** [issues:#5778] Implement Grob::event_cause, Grob::ultimate_event_cause** **Status:** Started **Created:** Thu Feb 20, 2020 03:11 P

[Lilypond-auto] [LilyIssues-auto] [testlilyissues:issues] #5778 Implement Grob::event_cause, Grob::ultimate_event_cause

- **Needs**: --> - **Patch**: new --> review - **Type**: --> --- ** [issues:#5778] Implement Grob::event_cause, Grob::ultimate_event_cause** **Status:** Started **Created:** Thu Feb 20, 2020 03:11 PM UTC by David Kastrup **Last Updated:** Fri Feb 21, 2020 12:55 AM UTC **Owner:** David Ka