Re: Release issues?

te" problem described here: >>> http://lists.gnu.org/archive/html/bug-lilypond/2017-03/msg00034.html >>> >>> >>> >>> Il giorno lun 20 mar 2017 alle 10:19, Urs Liska <u...@openlilylib.org> ha >>> scritto: >>>> Hi

Release issues?

Hi, are there any issues with the releases? The version bump commit to 2.19.57 is over a week old, but the website still claime 2.19.56. Urs -- u...@openlilylib.org https://openlilylib.org http://lilypondblog.org ___ lilypond-devel mailing list

Re: [guile-2.2] patches

Am 19.03.2017 um 15:43 schrieb David Kastrup: > The problem is more that Guile-2.0 will not work at all any more, and it > will take some time until Guile-2.2 becomes generally available. Now > it's not like compilation with Guile-2.0 is doing us a lot of favors > anyway. I think that's what

Re: [Guile 2.2]

Am 12. März 2017 15:52:27 MEZ schrieb Thomas Morley : >Hi all, > >guile 2.1.8 is released, which will be the next step towards the new >stable guile 2.2. > >Hence I'd think I should share my test-results >I've successfully build guile-2.1.8 from the guile-repo and had a

Font loading (was: GSoC 2017)

Am 11. März 2017 12:48:55 MEZ schrieb Werner LEMBERG : >> Here's a caveat (but I'm not sure if that relates to the GSoC >> project). Some time ago I worked on a modified system to load the >> notation font from system installed fonts too, which would >> substantially reduce the

Re: Static URLs pointing to releases

thought I couldn't "glob" a URL like http://download.linuxaudio.org/lilypond/binaries/freebsd-64/* to get all available files but the index page *does* include all links. Best Urs Am 10.03.2017 um 10:16 schrieb Phil Holmes: > - Original Message ----- From: "Urs Liska"

Re: Guile 1.8 in Ubuntu 17.04

Am 10.03.2017 um 09:51 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Just wanted to add to the list that I see that the upcoming Ubuntu >> 17.04 will not have Guile 1.8 anymore. > Then it either will not have LilyPond anymore, have LilyPond w

Static URLs pointing to releases

This had come up at some point, but I don't think we came to a conclusion, so ... Is it possible to have static URLs somewhere at lilypond.org that point to the binaries of the latest stable and latest development releases? The idea is for a script or program to be able to automatically retrieve

Guile 1.8 in Ubuntu 17.04

Just wanted to add to the list that I see that the upcoming Ubuntu 17.04 will not have Guile 1.8 anymore. -- u...@openlilylib.org https://openlilylib.org http://lilypondblog.org ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: Website upload

Am 07.03.2017 um 15:57 schrieb Urs Liska: > So ideally someone (as said I can't build currently) could grep through > the whole built website, taking the attached file (produced by a > combination of grep and sed) as the basis and this line: > > for f in $(cat to-be-deleted.txt);

Re: Website upload

Am 07.03.2017 um 15:34 schrieb Phil Holmes: > - Original Message - From: "David Kastrup" <d...@gnu.org> > To: "Phil Holmes" <m...@philholmes.net> > Cc: "Urs Liska" <u...@openlilylib.org>; <lilypond-devel@gnu.org> > S

Re: Website upload

//lilypond.org/gsoc.* URLs pointing to the English version of google-summer-of-code.html until April 3. Urs > > -- > Phil Holmes > > > - Original Message - From: "David Kastrup" <d...@gnu.org> > To: "Phil Holmes" <m...@philholmes.net> &

Re: Website upload

Am 07.03.2017 um 12:05 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Am 07.03.2017 um 11:45 schrieb David Kastrup: >>> Urs Liska <u...@openlilylib.org> writes: >>> >>>> Am 07.03.2017 um 11:24 schrieb Phil Holmes: >

Re: Website upload

Am 07.03.2017 um 11:58 schrieb Phil Holmes: > - Original Message - From: "Urs Liska" <u...@openlilylib.org> > To: "Phil Holmes" <m...@philholmes.net>; <lilypond-devel@gnu.org> > Cc: "Graham Percival" <gra...@percival-musi

Re: Website upload

Am 07.03.2017 um 11:45 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Am 07.03.2017 um 11:24 schrieb Phil Holmes: >> >>> Again - this needs answering with a bit of care, because the website >>> and the docs are closely

Re: Website upload

Am 07.03.2017 um 11:24 schrieb Phil Holmes: > Am 06.03.2017 um 23:43 schrieb Phil Holmes: >> > Simple answer - I run the GUB uploader. >> > >> > Slightly more useful one: there are two aspects to the "website": the >> > one that is created with "make website". This is a fairly simple >> > step,

Re: Fix dashed line errors (issue 320320043 by david.nales...@gmail.com)

I currently can't compile so I can't test the patch, and I can only assess (1) from reading the code. But it's good to fix this. It's a glitch but nevertheless "feels" awkward when tweaking a score. Urs Am 07.03.2017 um 05:46 schrieb david.nales...@gmail.com: > Reviewers: , > > Message: >

Re: GSoC 2017

Am 06.03.2017 um 23:46 schrieb tisimst: > On Mon, Mar 6, 2017 at 3:34 PM, Urs Liska [via Lilypond] < > ml-node+s1069038n200802...@n5.nabble.com> wrote: > >> Of course it is good to have optical sizes - even if the vast majority >> of LilyPond users may not ev

Re: Website upload

d note simply be deleted but redirected to http://lilypond.org/google-summer-of-code.html. Urs > > -- > Phil Holmes > > > - Original Message - From: "Urs Liska" <u...@openlilylib.org> > To: <lilypond-devel@gnu.org> > Sent: Monday, March 06, 2017 9:

Re: [requesting guidance] GSoC LilyPond

Hello Adeel, I hope you are by now subscribed to this list. [forwarding from summer-of-c...@gnu.org] Am 06.03.2017 um 15:47 schrieb Urs Liska: > > Hello Adeel, > > > thanks for your interest in LilyPond and GSoC. > > > This message is for you as well as for the other

Re: GSoC 2017

Am 06.03.2017 um 17:32 schrieb tisimst: > On Mon, Mar 6, 2017 at 1:42 AM, ul [via Lilypond] < > ml-node+s1069038n200762...@n5.nabble.com> wrote: > >> >> Am 06.03.2017 um 07:44 schrieb Werner LEMBERG: > Not yet :-) I can only second what Urs said. I think we (i.e. Abraham and you)

Re: GSoC 2017

Am 06.03.2017 um 23:16 schrieb tisimst: > On Mon, Mar 6, 2017 at 2:34 PM, Noeck [via Lilypond] < > ml-node+s1069038n200797...@n5.nabble.com> wrote: > >> 3. IIUC, this was just a set of overrides and callback functions picking >> up the correct symbols from a smufl font, doing the mapping by

Website upload (was: Obsolete GSoC page)

Phil, could you tell us how you (you do that, isn't it?) how you upload the website? Urs Am 06.03.2017 um 11:59 schrieb Urs Liska: > > Am 6. März 2017 11:41:54 MEZ schrieb Federico Bruni <f...@inventati.org>: >> Il giorno lun 6 mar 2017 alle 11:27, Federico Bruni >>

Re: Obsolete GSoC page

Am 6. März 2017 11:41:54 MEZ schrieb Federico Bruni : >Il giorno lun 6 mar 2017 alle 11:27, Federico Bruni > ha scritto: >> gsoc-2012.html is generated by an existing node: "@node GSoC 2012", >> as shown by the grep above. > >Sorry, you are right: the

Re: Obsolete GSoC page

Am 06.03.2017 um 10:16 schrieb Federico Bruni: > > > Il giorno lun 6 mar 2017 alle 7:20, Urs Liska <u...@openlilylib.org> ha > scritto: >> Am 06.03.2017 um 05:02 schrieb Werner LEMBERG: >> >> PS: If I do a google search for `lilypond gsoc', the first hit i

Re: GSoC 2017

Am 06.03.2017 um 07:44 schrieb Werner LEMBERG: >>> Not yet :-) I can only second what Urs said. >> I think we (i.e. Abraham and you) should give Matthew some more >> concrete pointers on where to start investigating. > Can you send him our e-mail conversation regarding this topic? > Currently,

Re: GSoC 2017

Hi Matthew, Am 06.03.2017 um 05:02 schrieb Werner LEMBERG: > >> The first thing will be to get an idea about what happens when >> LilyPond uses glyphs from the notation font. How does it locate the >> font, how does it identify the glyph to choose? And on the other >> side, how is the notation

Obsolete GSoC page (was: GSoC 2017)

Am 06.03.2017 um 05:02 schrieb Werner LEMBERG: > PS: If I do a google search for `lilypond gsoc', the first hit is the > old > > http://lilypond.org/gsoc.html > > and only the second hit is the current > > http://lilypond.org/google-summer-of-code.html > > Any chance to

Re: Next devel release

Am 02.03.2017 um 18:04 schrieb Phil Holmes: > - Original Message - From: > To: > Sent: Thursday, March 02, 2017 1:21 PM > Subject: Next devel release > > >> Hi all (Phil?), >> >> when is the next release (2.19.57) to be expected? >> I'm

GSoC 2017

Dear LilyPond community, I'm happy to inform you that both LilyPond (as part of GNU) and Frescobaldi have been accepted as mentoring organizations for Google Summer of Code 2017 :-) This means we have the chance to get up to four (realistically) students to work on improving LilyPond and

Re: Web: Move older news to the attic page (issue 318630043 by paulwmor...@gmail.com)

Am 27.02.2017 um 12:46 schrieb Federico Bruni: > Il giorno lun 27 feb 2017 alle 11:49, Urs Liska <u...@openlilylib.org> > ha scritto: >> With the "old news" page the screenshot doesn't really tell me what >> you did. Would you mind explaining "in plain word

Re: Web: Move older news to the attic page (issue 318630043 by paulwmor...@gmail.com)

Am 27.02.2017 um 05:27 schrieb paulwmor...@gmail.com: > Reviewers: , > > Message: > Please review. I realized after changing the file names that it might > not have been the best approach. I'm not sure how it will affect > translations of the site. Not hard to change them back in a revised >

Re: Web: nest GSOC project ideas under subsection/h3 (issue 314530043 by paulwmor...@gmail.com)

Am 22.02.2017 um 20:04 schrieb gra...@percival-music.ca: > Sorry, I disagree. I think the boxes make it easier to skim the page; > there horizontal gap makes it absolutely clear that each proposal is > distinct. I think the point in Paul's suggestion is to make a clear separation between the

Re: NR: Document \remove "Keep_alive_together_engraver" (issue 318580043 by g...@ursliska.de)

Am 17.02.2017 um 09:21 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> Am 17.02.2017 um 08:34 schrieb d...@gnu.org: >>> Ok, I'll bite. What kind of piano music is written like >>> >>> \score { >>> \new PianoStaf

Re: NR: Document \remove "Keep_alive_together_engraver" (issue 318580043 by g...@ursliska.de)

Am 17.02.2017 um 08:34 schrieb d...@gnu.org: > On 2017/02/17 07:27:27, git wrote: >> On 2017/02/17 07:24:42, dak wrote: > >> > Documentation should not focus about how to use the wrong tool for > the job. >> > If you want to document it, do it the other way round: explain how > you can keep >> >

Re: Lily version operators documentation

Am 15. Februar 2017 13:03:55 MEZ schrieb Trevor Daniels <tr...@treda.co.uk>: > >Urs Liska wrote Wednesday, February 15, 2017 8:04 AM > >> Am 14.02.2017 um 18:27 schrieb Trevor Daniels: >> >>> As these functions are not intended for the usual LilyPond user

Re: Lily version operators documentation

Am 14.02.2017 um 18:27 schrieb Trevor Daniels: > Urs Liska wrote Tuesday, February 14, 2017 9:23 AM > >> my patch https://sourceforge.net/p/testlilyissues/issues/5067/ >> http://codereview.appspot.com/317270043 is currently on countdown. It >> introduces the pro

Re: Add lilypond version predicates/operators (issue 317270043 by g...@ursliska.de)

Hi Harm, Am 14.02.2017 um 22:03 schrieb thomasmorle...@gmail.com: > To throw in my own 2cts. > > Why not compare strings, looks more straight forward to me. > > Indeed your code looks simpler, and your measurement indicates that the computational cost is very similar. However, David's last

Lily version operators documentation

Hi, my patch https://sourceforge.net/p/testlilyissues/issues/5067/ http://codereview.appspot.com/317270043 is currently on countdown. It introduces the procedures - lilypond>? - lilypond>=? - lilypondhttps://openlilylib.org http://lilypondblog.org

Re: GSoC projects list

Am 10. Februar 2017 06:43:55 MEZ schrieb Werner LEMBERG : > >> Some ideas, without being able to mentor them. [...] > >Here's another one: > > . Make lilypond support automatic line breaks for piano four hands >scores. Nice one. > >However, this must be tagged as

Re: Braille

Am 8. Februar 2017 07:26:16 MEZ schrieb Werner LEMBERG : > >> I have resurrected my Braille music output project, which was >> originated around 12 years ago [...] I've been beavering away it it >> for the past few months and I have a rough prototype, probably sort >> of a proof

Re: Contemporary notation (Re: GSoC projects list)

lyphs from specialized fonts. Indeed this should be discussed thoroughly before actually investing substantial energy in implementation. But for now I'd defer this to a moment if there should be a student interested in the project. This discussion would be a very interesting topic for getting familiar with

Re: Cleaning up GSoC project ideas

Am 06.02.2017 um 15:40 schrieb Paul: > On 02/02/2017 04:10 PM, Urs Liska wrote: > >> However, I suggest that we either remove such orphaned projects or at >> least compress and move them down to the bottom of the page. A concise >> page with actual and current pro

Contemporary notation (Re: GSoC projects list)

Am 06.02.2017 um 00:24 schrieb Urs Liska: > > Hi all, > > I'm somewhat worried about LilyPond's GSoC project proposals list. > Right now I'm purging the web page > (http://lilypond.org/google-summer-of-code.html) from projects without > mentors, and I have the feeling when this

Re: GSoC projects list

Am 06.02.2017 um 08:48 schrieb Werner LEMBERG: >> So essentially per now we will have only 4/5 projects left: >> >> * Improving internal chord structure >> * Adopting SMuFL >> * Adding glyph variants >> * openLilyLib testing and documentation >> >> I find this list quite disappointing,

Re: GSoC projects list

Am 6. Februar 2017 07:56:34 MEZ schrieb Jan-Peter Voigt <jp.vo...@gmx.de>: >Hi Urs, > > >Am 06.02.2017 um 00:24 schrieb Urs Liska: >> Hi all, >> >> I'm somewhat worried about LilyPond's GSoC project proposals list. >Right >> now I'm purging the w

GSoC projects list

Hi all, I'm somewhat worried about LilyPond's GSoC project proposals list. Right now I'm purging the web page (http://lilypond.org/google-summer-of-code.html) from projects without mentors, and I have the feeling when this process is completed we're left with an unsatisfactory state. >From the 9

Re: Web-GSoC: Remove Grace note project (issue 317210043 by g...@ursliska.de)

Am 5. Februar 2017 15:21:54 MEZ schrieb d...@gnu.org: >The problem with "mentoring" this is that the expertise for >successfully >mentoring this project is the same as for doing it yourself. This is >not a question of making a plan and then implementing its parts over >the >course of several

Cleaning up GSoC project ideas

work to commit to. We really need more activity here, and it can't be true that I have to be permanently pushing to get things forward. So please someone or many get involved ... Best Urs -- Urs Liska https://openlilylib.org http://lilypondblog.org ___ lil

Re: Question about '\new Staff =' command

Am 02.02.2017 um 21:25 schrieb SoundsFromSound: > Urs Liska wrote >> You can use the explicit staff name to access the context (or compare to >> some arbitrary value), and it's for example used in the \change Staff = >> "upper" command. > > Can you give a

Re: Question about '\new Staff =' command

Am 02.02.2017 um 15:05 schrieb James: > Hello, > > Would someone tell me (as a person who doesn't really use explicit > 'Staff' commands what the purpose of the \new Staff = 'some string' is? > > That is looking at many of the examples in our Docs and Snippets, the > '=' doesn't appear to do

Re: ly2musicxml / possible sponsoring

;>> >>> Is there any chance for completion? If it helps, I'm willing to put >>> an >>> resonable amount of money into this and fund the completion of this >>> feature. >> I'd probably be interested in working on this, especially if you are >> willing and

Re: GSoC project ideas

Am 23.01.2017 um 23:11 schrieb Simon Albrecht: > On 23.01.2017 22:47, Urs Liska wrote: >> So while it's perfectly possible to put OLL projects on the list and to >> apply for them (or others not listed there) in case of doubt projects >> working on LilyPond itself mi

Re: GSoC project ideas

er, "new-style", packages. This would actually bring openLilyLib a huge step forward to be usable on a broader base. Urs > > On Mon, Jan 23, 2017 at 8:06 PM, Urs Liska <u...@openlilylib.org> wrote: > >> Hi all, >> >> GSoC has started and the timeline is

Re: GSoC project ideas

> >PS: >I've also provided a patch containing a section with recommendations to >potential students. They draw from my own experience as a mentor last >year and suggestions discussed both on the mentors' mailing list and >the >mentors' summit last year. Please consider these paragraphs too, as

GSoC project ideas

Hi all, GSoC has started and the timeline is proceeding quickly (https://summerofcode.withgoogle.com/). GNU is going to apply until February 9, and by February 27 I expect them to be accepted to the program, which will make LilyPond applicable as well. Students will apply between March 20 and

Structuring website page

Hi, I'm drafting a new section on our GSoC page goving more information for achieving a mutually satisfying project. I'd add that to the bottom of the page, after the project ideas. However, the page isn't properly structured, and while it's acceptable in the current incarnation it becomes

Re: Back in the Pond

Hi David, Am 19.01.2017 um 11:18 schrieb David Kastrup: > But at any rate, I hope to be on board at least for making LilyPond 2.20 > a thing. to cut your long story even shorter: sad but glad to read that. Urs -- u...@openlilylib.org https://openlilylib.org http://lilypondblog.org

OLL features (was: LilyPond 2.20 release process)

fort to have in a 2.20, considering that a 2.22 is presumably quite some time away. What do you think? Best Urs -- Urs Liska https://openlilylib.org http://lilypondblog.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Free alternatives to Rietveld?

Am 27. Dezember 2016 13:33:11 MEZ, schrieb Simon Albrecht : >Hello everybody, > >just now I tried to login with Google in order to close my two recent >Rietveld reviews. However, Google decided that despite entering a >verification code from e-mail it couldn’t confirm

Re: Offer to help development: Convert MIDI to Lilypond

Hi Joseph, welcome to the LilyPond community. It is great to see someone volunteering for such a task. It is a good idea to ask for a mentor, although that person would probably be mostly a mediator between you and the developers. Personally I don't think I could be that mentor but I wanted

Re: PATCHES - Countdown for December 24th

list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel -- Urs Liska https://openlilylib.org http://lilypondblog.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: [PATCH] Automatic lyric extenders

onable request. Urs > > Cheers, > Knut > > > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.org/mailman/listinfo/lilypond-devel -- Urs Liska www.openlilylib.org ___

Re: music function to be included somewhere in scm/*

Am 16. Dezember 2016 15:11:59 MEZ, schrieb David Nalesnik <david.nales...@gmail.com>: >On Fri, Dec 16, 2016 at 8:07 AM, Knut Petersen ><knut_peter...@t-online.de> wrote: >> Am 16.12.2016 um 14:38 schrieb Urs Liska: >>> >>> >>>> As your kno

Re: music function to be included somewhere in scm/*

Am 16. Dezember 2016 14:31:43 MEZ, schrieb Knut Petersen : >Hi Alexander et. al.! > >For me scheme still is the most counterintuitive way to program a >computer. I believe that I discovered a >thousand ways to trigger the message "[...] warning: Ignoring >non-music

Re: music function to be included somewhere in scm/*

Am 15. Dezember 2016 18:58:13 MEZ, schrieb Knut Petersen : >Am 15.12.2016 um 17:17 schrieb Francisco Vila: >> >> Excuse my brevity for now, but I think lyrics extenders are meant >only for the last syllable of a word. What does Gould say, for example? >I can check

Re: music function to be included somewhere in scm/*

Am 14. Dezember 2016 18:03:09 MEZ, schrieb Simon Albrecht : >On 14.12.2016 14:54, Knut Petersen wrote: >> With a music function \autoextenders that adds extender events to >> every syllable you >> - can be sure never to forget extenders, >> - can be sure never to

Re: music function to be included somewhere in scm/*

Am 14.12.2016 um 10:43 schrieb Alexander Kobel: >> To allow automated creation of lyric extenders a helper function is >> needed > > ... that does exactly this, adding extenders everywhere. > > IMHO, the actual question to decide upon is: Do we want this to be > enabled by default? IIUC, the

Re: music function to be included somewhere in scm/*

Am 14.12.2016 um 10:43 schrieb Alexander Kobel: >> Q2: Obviously the definition of \autoextenders does not match the coding >> style used in scm/*. It does not even >> work if it is added to music-functions.scm. Some advice is needed ... >> the extending-manual is not a real help in >> this

Re: Lilypond python upgrade

Am 8. Dezember 2016 08:17:17 MEZ, schrieb Werner LEMBERG : > >> Moving a thread across from the user list, I just wanted to let >> people know that I will be starting on the work of upgrading >> lilypond to use Python 3 - yes, with all the complexity that >> entails. I am happy to

Re: bypassing the patch countdown

Am 7. Dezember 2016 23:34:39 MEZ, schrieb Graham Percival : >I was going to wait a month or two before suggesting this, just to >make sure I was fully "up to date", but I'll jump in now. > >We instituted the policy of patch countdowns and Patchy after the >lengthy wait

Re: referencing hash key with music symbol

Am 7. Dezember 2016 19:20:26 MEZ, schrieb David Kastrup : >Jeffery Shivers writes: > >> Hi LP team, >> >> I am working on automating editorial commands with ScholarLY, and I >am >> having some trouble pulling a music function that is stored in a hash >>

Re: guile-2.0 and debian

Am 07.12.2016 um 11:34 schrieb Federico Bruni: > Il giorno mer 7 dic 2016 alle 10:28, Urs Liska <u...@openlilylib.org> ha > scritto: >> OK, thank you. >> After installing these building LilyPond fails with the following error: >> >> WARNING: Please consider i

Re: guile-2.0 and debian

Am 07.12.2016 um 10:31 schrieb Antonio Ospite: > On Wed, 7 Dec 2016 08:42:29 +0100 > Urs Liska <u...@openlilylib.org> wrote: > >> Am 07.11.2016 um 17:08 schrieb Federico Bruni: >>> In case you don't know already, last news about guile2 and debian: >&

Re: guile-2.0 and debian

Am 07.12.2016 um 09:53 schrieb Federico Bruni: > Il giorno mer 7 dic 2016 alle 8:42, Urs Liska <u...@openlilylib.org> ha > scritto: >>> In case you don't know already, last news about guile2 and debian: >>> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005

Re: guile-2.0 and debian

Am 07.12.2016 um 09:53 schrieb Federico Bruni: > Yesterday I was updating LilyDev to stretch (now testing) and I found > that ttf- packages are no more in Debian. B I wanted to install ttf-inconsolata and was directed to install fonts-inconsolata instead. Does that help?

Re: guile-2.0 and debian

Am 07.11.2016 um 17:08 schrieb Federico Bruni: > In case you don't know already, last news about guile2 and debian: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=746005#216 Just for the record (although it's probably evident): This doesn't only mean one can't install "lilypond" from

Re: Doc CG 6.1: Add caveat on website work (issue 315130043 by gra...@percival-music.ca)

Am 05.12.2016 um 09:05 schrieb gra...@percival-music.ca: > Looks good to me, especially with Trevor's suggestion. > > > https://codereview.appspot.com/315130043/diff/1/Documentation/contributor/website-work.itexi > > File Documentation/contributor/website-work.itexi (right): > >

Re: Unit testing

Am 29. Oktober 2016 12:06:20 GMT-07:00, schrieb Carl Sorensen <c_soren...@byu.edu>: > > >On 10/29/16 11:34 AM, "lilypond-devel on behalf of Urs Liska" ><lilypond-devel-bounces+c_sorensen=byu@gnu.org on behalf of >u...@openlilylib.org> wrote: >

Unit testing

Is there any notion (or the potential for a notion) of unit testing in LilyPond's development process? Urs -- Diese Nachricht wurde von meinem Android-Mobiltelefon mit K-9 Mail gesendet. ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: Changing voice order...

Am 27. Oktober 2016 04:40:14 GMT-07:00, schrieb David Kastrup : > >This concerns << ... \\ ... \\ ... ... >> > >If we have more than one voice, voices are assigned in order: > >1/2, 1/2/3, 1/2/3/4, 1/2/3/4/5, 1/2/3/4/5/6 ... > >while the documentation is quite explicit that,

Re: Akkordzither-tab in lilypond proper?

Am 22. Oktober 2016 16:29:10 MESZ, schrieb Simon Albrecht : >On 22.10.2016 10:00, Thomas Morley wrote: >> Hi, >> >> I recently mentioned my work to create the very special notation for >> Akkordzither. >>

Re: issue tracker access

Am 18.10.2016 um 22:43 schrieb Simon Albrecht: > Hi Janek, > > great to see you back in the Pond :-) ;-) ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Add output-attributes grob property to replace id (issue 308430043 by paulwmor...@gmail.com)

Am 27.09.2016 um 20:46 schrieb paulwmor...@gmail.com: > I considered this, but it's simpler for both code and user if all these > svg output attributes are in the same alist property rather than split > across two. Currently the id property is not used for anything else, so > no need to keep it

Re: Add annotation of \shape-d curves (WIP) (issue 303650043 by g...@ursliska.de)

-init.ly:30: (ice-9 optargs)) > These are artifacts from Frescobaldi auto-formatting, I suppose. > > https://codereview.appspot.com/303650043/ > > ___ > lilypond-devel mailing list > lilypond-devel@gnu.org > https://lists.gnu.

Re: Proposal: change Grob.id to Grob.output-properties

Am 16. September 2016 02:37:53 MESZ, schrieb Paul : >Hi all, I'd like to improve on the "id" grob property but I wanted to >ask about the best way to migrate users if/when we made the change I'm >thinking of. > First of all, I think this is a good idea, and it comes at

Re: Web: home page: add examples/images, reduce news to headlines (issue 306350043 by paulwmor...@gmail.com)

Am 15.09.2016 um 02:51 schrieb paulwmor...@gmail.com: > Now using the Bach BWV861 example from the essay. Screenshot: > https://drive.google.com/open?id=0ByNTIEA63_a_ZGZrZzlkSUhJeU0 > > I like the cleaner look since this image doesn't have any title, text, > etc. like the previous one. If you

Re: Web: home page: add examples/images, reduce news to headlines (issue 306350043 by paulwmor...@gmail.com)

Am 06.09.2016 um 17:49 schrieb paulwmor...@gmail.com: > Patch set 3 uploaded, with just one example image on the home page and a > list of links to the other examples on the examples page. I like how > this gets an image of sheet music onto the home page and helps > communicate the wide range

Re: Web: home page: add examples/images, reduce news to headlines (issue 306350043 by paulwmor...@gmail.com)

Am 31. August 2016 16:11:14 MESZ, schrieb Paul : >On 08/30/2016 06:05 PM, carl.d.soren...@gmail.com wrote: > >> I'm not comfortable with the really long, scrolling, home page. > >Ok, given these concerns that Carl and David raised, let me think some >more and see what I

GUB, first usage question

Hi all, I just thought giving GUB a try, despite all the numerous issues people seem to have with it. So I went to my server, cloned GUB and ran bin/gub lilypond-installer. This ran for quite some time and finished with a simple "done", so obviously successfully (for this limited single target).

Re: Downcase of a symbol

>Case insensitivity is almost never a good idea. It leads to stuff that >sometimes works and sometimes fails under mysterious circumstances. > >For example, you are aware that in a Turkish locale, I downcases to ı >instead of i , and i uppercases to İ instead of I ? > >And if you do

Re: Downcase of a symbol

Am 13.08.2016 um 08:10 schrieb David Kastrup: > Urs Liska <u...@openlilylib.org> writes: > >> I have written a function to return the lowercase version of a symbol >> for use in my library as >> >> % Return the lowercase version of a symbol >> #(de

Downcase of a symbol

Hi, I have written a function to return the lowercase version of a symbol for use in my library as % Return the lowercase version of a symbol #(define (symbol->lowercase sym) (string->symbol (string-downcase (symbol->string sym Just a small question: this seems so general that I

Re: Branch management

Am 12.08.2016 um 07:21 schrieb littlesincanada: > Hi, > > On 11/08/16 21:18, David Kastrup wrote: >> littlesincanada writes: >> >>> On the face of it, a rebase is the obvious solution, but I'm told that >>> it's a cardinal sin to rebase commits that have already

Re: Programming Language

Am 10.08.2016 um 19:09 schrieb David Kastrup: > C++ is a good career move, but the C++ in LilyPond's code base is of > rather mixed quality and of rather mixed age: the early parts had to > rely on the features available in early language standards. So C++ > skills acquired while working with

Re: additional entry in lilypond.org/productions.html?

Am 12.07.2016 um 10:00 schrieb Marc Hohl: >> The Productions page has now a long column of concerts on the left and a >> short column of published sheet music on the right. I think that >> "published" in this case means just publicly available? I mean, Mutopia >> is not a publishing company. > >

Re: Leave of absence

Have fun. I just read they have 29 degrees Celsius during summer: 14 in the morning and 15 in the afternoon ;-) Am 11.07.2016 um 10:05 schrieb Thomas Morley: > Hi all, > > I'll be on vacations for the next two weeks, doing camping in Normandie. > Thus completely without net-access. > > Cheers,

Re: referencing hash key with music symbol

frastructure where it would look something like \registerOption scholarly.editorial-functions.additions #'() \setOption scholarly.editorial-functions.addition.slur #some-function Don't know if that helps with your problem but please consider using the existing infrastructure. Urs -

Re: NR: Mention standalone accidentals in figuremode (issue 299510043 by g...@ursliska.de)

Am 03.07.2016 um 23:05 schrieb d...@gnu.org: > I think this chapter would deserve a lot more love I agree, but I can't provide that currently. Maybe things look differently when I'm more into (or through) the current project, which is my first encounter (engraving-wise) with figured bass.

Re: NR: Mention standalone accidentals in figuremode (issue 299510043 by g...@ursliska.de)

Am 03.07.2016 um 14:49 schrieb benko@gmail.com: > LGTM > > https://codereview.appspot.com/299510043/ Discussion on lilypond-user (http://lists.gnu.org/archive/html/lilypond-user/2016-07/msg00058.html) show that it isn't that good. I think there *is* something to be done about the current

<    1   2   3   4   5   6   7   8   >