@cindex and friends in snippet files
Folks, some stuff like `subdivideBeams' is only documented in files from `Documentation/snippets'. However, not a single file in this directory contains an index entry. What is the proper way to add index entries to those files? Are they still synchronized with LSI? I would like to add a bunch of them, for obvious reasons. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.20 release roadmap
Am 20. September 2019 02:23:58 MESZ schrieb Carl Sorensen : >We are stuck for release because GUB is not working properly. Until we >get GUB to work properly, we cannot make a release. > >As far as I know now, the answer is in fact indefinite. But is that the actual roadblock for the *2.20* release, not just *any*? I mean: once that's solved, there was discussion about another 2.19 release, but would that also mean 2.20 can be immediately released? Of course it's futile since I can't help much, but it would becreally great to have a "stable" release by January . We'll have the music engraving conference in Salzburg (that Werner announced a few days ago), where we expect other software to be presented too. It would be awkward - to put it mildly - to talk about our program that hasn't seen a stabke release in six years bx then ... Urs > >Thanks, > >Carl > > >On 9/19/19, 6:14 PM, "Andrew Bernard" >wrote: > > I do hope this is not seen as impertinent, because it is not intended >that way. It's curious that I have asked the question about 2.20 >release >more than once and each time received no reply (unless lost in my >mailers). > >Most projects will give some sort of indication about future releases. > If the indication for lilypond is simply 'indefinite' that's alright, >but I would be keen to know. > > >Andrew > > >On 18/9/19 1:44 pm, Andrew Bernard wrote: >> Hello All, >> >> I asked the same on the user list, but no response. Is there any >> roadmap as to when 2.20 may be released? Are there any plans to do >so? >> > > I KNOW we are very under-resourced. I'd very much like to help with >> the development but I regret to say I have never been able to wrap my > >> mind around the lilypond source code and how it all works, so I can't > >> contribute, although I would very much like to. For some reason, >> despite experience in software, I personally find it very opaque. But > >> that's just me. >> >> As always, sincere thanks to those who do work on this amazing >software. >> >> Andrew >> >> > >___ >lilypond-devel mailing list >lilypond-devel@gnu.org >https://lists.gnu.org/mailman/listinfo/lilypond-devel > > >___ >lilypond-devel mailing list >lilypond-devel@gnu.org >https://lists.gnu.org/mailman/listinfo/lilypond-devel -- Diese Nachricht wurde von meinem Android-Gerät mit K-9 Mail gesendet. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.20 release roadmap
Thank you Carl. Andrew On 20/9/19 10:23 am, Carl Sorensen wrote: We are stuck for release because GUB is not working properly. Until we get GUB to work properly, we cannot make a release. As far as I know now, the answer is in fact indefinite. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.20 release roadmap
We are stuck for release because GUB is not working properly. Until we get GUB to work properly, we cannot make a release. As far as I know now, the answer is in fact indefinite. Thanks, Carl On 9/19/19, 6:14 PM, "Andrew Bernard" wrote: I do hope this is not seen as impertinent, because it is not intended that way. It's curious that I have asked the question about 2.20 release more than once and each time received no reply (unless lost in my mailers). Most projects will give some sort of indication about future releases. If the indication for lilypond is simply 'indefinite' that's alright, but I would be keen to know. Andrew On 18/9/19 1:44 pm, Andrew Bernard wrote: > Hello All, > > I asked the same on the user list, but no response. Is there any > roadmap as to when 2.20 may be released? Are there any plans to do so? > > I KNOW we are very under-resourced. I'd very much like to help with > the development but I regret to say I have never been able to wrap my > mind around the lilypond source code and how it all works, so I can't > contribute, although I would very much like to. For some reason, > despite experience in software, I personally find it very opaque. But > that's just me. > > As always, sincere thanks to those who do work on this amazing software. > > Andrew > > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: 2.20 release roadmap
I do hope this is not seen as impertinent, because it is not intended that way. It's curious that I have asked the question about 2.20 release more than once and each time received no reply (unless lost in my mailers). Most projects will give some sort of indication about future releases. If the indication for lilypond is simply 'indefinite' that's alright, but I would be keen to know. Andrew On 18/9/19 1:44 pm, Andrew Bernard wrote: Hello All, I asked the same on the user list, but no response. Is there any roadmap as to when 2.20 may be released? Are there any plans to do so? I KNOW we are very under-resourced. I'd very much like to help with the development but I regret to say I have never been able to wrap my mind around the lilypond source code and how it all works, so I can't contribute, although I would very much like to. For some reason, despite experience in software, I personally find it very opaque. But that's just me. As always, sincere thanks to those who do work on this amazing software. Andrew ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: account setup and first patch
>> > in that case I'd propose to delete the script from the repository >> > and update Documentation/contributor/source-code.itexi >> > accordingly, see >> > >> http://lilypond.org/doc/v2.19/Documentation/contributor/the-patch-review-cycle >> >> Can you prepare a patch, please? > > As I don't actually know what the new procedure is, I can only > delete the paragraph in question that mentions the old script. Is > that what you have in mind for now? Yes. The new procedure is not (yet?) part of LilyPond, so it's best to remove it from the documentation. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: account setup and first patch
Am Donnerstag, den 19.09.2019, 18:24 +0200 schrieb Werner LEMBERG: > >> > > I wonder whether James can upload his script to the > > >> > > repository... > > >> > > > >> > I'm 99% certain James doesn't use this shell script. > > >> > > >> It doesn't work with Source Forge. It was used with Google's > > >> Tracker. > > > > > > in that case I'd propose to delete the script from the repository > > > and update Documentation/contributor/source-code.itexi accordingly, > > > see > > > > http://lilypond.org/doc/v2.19/Documentation/contributor/the-patch-review-cycle > > > . The current situation is a bit confusing (for a newcomer)... > > > Can you prepare a patch, please? As I don't actually know what the new procedure is, I can only delete the paragraph in question that mentions the old script. Is that what you have in mind for now? Jonas signature.asc Description: This is a digitally signed message part ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: account setup and first patch
>> > > I wonder whether James can upload his script to the >> > > repository... >> > >> > I'm 99% certain James doesn't use this shell script. >> >> It doesn't work with Source Forge. It was used with Google's >> Tracker. > > in that case I'd propose to delete the script from the repository > and update Documentation/contributor/source-code.itexi accordingly, > see > http://lilypond.org/doc/v2.19/Documentation/contributor/the-patch-review-cycle > . The current situation is a bit confusing (for a newcomer)... Can you prepare a patch, please? Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: account setup and first patch
Hello, Am Donnerstag, den 19.09.2019, 00:02 +0100 schrieb James: > Hello, > > On 18/09/2019 11:33, Phil Holmes wrote: > > - Original Message - From: "Werner LEMBERG" < > > w...@gnu.org > > > > > To: < > > hah...@hahnjo.de > > >; < > > lilypond-devel@gnu.org > > > > > Sent: Wednesday, September 18, 2019 11:00 AM > > Subject: Re: account setup and first patch > > > > > > > Hello Jonas, > > > > > > > > > welcome to the list! > > > > > > > I'm using Lilypond since a few years and would like to start > > > > contributing. > > > > > > Excellent! > > > > > > > Find attached a patch to replace outdated references to > > > > code.google.com by their SourceForge equivalent. > > > > > > Thanks, I've applied it to `staging'. Regarding your remark > > > > > > * scripts/auxiliar/make-countdown-announcement.sh: I guess there is > > > a new script somewhere that works with SourceForge. Maybe this > > > script can be deleted? > > > > > > I wonder whether James can upload his script to the repository... > > > > > > > > >Werner > > > > I'm 99% certain James doesn't use this shell script. > > It doesn't work with Source Forge. It was used with Google's Tracker. in that case I'd propose to delete the script from the repository and update Documentation/contributor/source-code.itexi accordingly, see http://lilypond.org/doc/v2.19/Documentation/contributor/the-patch-review-cycle . The current situation is a bit confusing (for a newcomer)... Regards, Jonas signature.asc Description: This is a digitally signed message part ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: account setup and first patch
Hi, Am Mittwoch, den 18.09.2019, 12:00 +0200 schrieb Werner LEMBERG: > Hello Jonas, > > > welcome to the list! > > > I'm using Lilypond since a few years and would like to start > > > contributing. > > > Excellent! > > > Find attached a patch to replace outdated references to > > > code.google.com by their SourceForge equivalent. > > > Thanks, I've applied it to `staging'. thanks for applying, I've seen the commit worked its way into the master branch :-) Regards, Jonas signature.asc Description: This is a digitally signed message part ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCHES - Countdown for September 19th
Hello, Here is the current patch countdown list. The next countdown will be on September 22nd. A quick synopsis of all patches currently in the review process can be found here: http://philholmes.net/lilypond/allura/ Push: No patches to push at this time, Countdown: No patches on countdown at this time. Review: No patches in Review at this time New: No New patches at this time. *** Regards, James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
\tweak no longer works with \tuplet
Folks, have a look at https://sourceforge.net/p/testlilyissues/issues// This is a serious regression. I've noticed the problem since I'm going to rewrite the Stockhausen Klavierstück II to fix various issues accumulated over time (and to make the input look less intimidating). In the bug report I've also provided a regression test; it seems we missed this issue completely because `\tweak' + `\tuplet' is not used in any of the regression files. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
