Back in the Pond

2017-01-19 Thread David Kastrup
Hi fellow ponders, it would appear that my excursion into a regular workplace ended up somewhat shortlived. Long story short, I was not able to convincingly make a weekly commute, part home-office, and very Windows-centric workflows (and using rather unflexible version control) and a focus on

Re: LilyDev 5.0 released

2017-01-19 Thread Federico Bruni
Il giorno mer 18 gen 2017 alle 18:54, Paul ha scritto: - have you tried installing another Linux image on the same version of Virtualbox? My LilyDev4 VM is working fine (I haven't tried re-installing it from scratch). If you have some time, can you try installing

Re: Back in the Pond

2017-01-19 Thread Urs Liska
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

Re: Make failng in translation branch

2017-01-19 Thread Federico Bruni
Il giorno gio 19 gen 2017 alle 8:56, Walter Garcia-Fontes ha scritto: I'm trying "make" in the translation branch to test some new translations of mine, and I'm getting the below error. I'm doing it in a version of lilydev I downloaded some months ago, should I reinstall

Re: Back in the Pond

2017-01-19 Thread Trevor Daniels
David, you wrote Thursday, January 19, 2017 10:18 AM > it would appear that my excursion into a regular workplace ended up somewhat shortlived. Really sorry to hear that, but it's great to have you back! > So for the short time range, I am again dependent > on support by other LilyPond

Re: Back in the Pond

2017-01-19 Thread David Kastrup
"Trevor Daniels" writes: > David, you wrote Thursday, January 19, 2017 10:18 AM > >> it would appear that my excursion into a regular workplace ended up >> somewhat shortlived. > > Really sorry to hear that, but it's great to have you back! > >> So for the short time

Re: Back in the Pond

2017-01-19 Thread Simon Albrecht
On 19.01.2017 14:01, David Kastrup wrote: it is an open question whether it makes sense to admit it into 2.20.0 (or was the first version 2.20.1) We had 2.18.0 and 2.18.2. Best, Simon ___ lilypond-devel mailing list lilypond-devel@gnu.org

Re: Back in the Pond

2017-01-19 Thread Gianmaria Lari
Trevor wrote: > I'll definitely turn on my financial contribution again. > what's the better way to give a financial contribution? g. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel

C++ question:

2017-01-19 Thread Knut Petersen
Hi everybody! Is there an equivalent of \with-dimensions #'(0 . 0) #'(0 . 0) that can be used on a stencil within the C++ part of lilypond? If not: I thought I could work around that problem by constructing and using a markup: SCM properties =

Re: Back in the Pond

2017-01-19 Thread Alexander Kobel
Hi David, On 2017-01-19 12:59, Trevor Daniels wrote: David, you wrote Thursday, January 19, 2017 10:18 AM it would appear that my excursion into a regular workplace ended up somewhat shortlived. Really sorry to hear that, but it's great to have you back! Ditto. I wish that you would have

Replace midi.c with midi.py (issue 312300043 by gra...@percival-music.ca)

2017-01-19 Thread graham
Reviewers: , Message: Please review. Running "make install" does *not* result in a usable midi2ly, but that's an existing problem not related to this (which I'll discuss separately). For testing purposes, you can use: PYTHONPATH=$HOME/.local/share/lilypond/2.19.55/python/ midi2ly

python include path oddity with "make install"

2017-01-19 Thread Graham Percival
At the moment, doing: mkdir build cd build ../configure --prefix=$HOME/.local/ make make install results in python files which can't find lilylib. This is installed to: $(PREFIX)/share/lilypond/$(VERSION)/python/ The relocation is supposed to be handled by:

Re: LilyDev 5.0 released

2017-01-19 Thread Paul
Hi Federico, On 01/19/2017 06:35 AM, Federico Bruni wrote: If you have some time, can you try installing another Debian testing iso? Choose the netinst ISO for your architecture here: https://www.debian.org/devel/debian-installer/ This would help to understand if the problem is in LilyDev or

Re: Back in the Pond

2017-01-19 Thread Graham Percival
On Thu, Jan 19, 2017 at 02:01:40PM +0100, David Kastrup wrote: > "Trevor Daniels" writes: > > > David, you wrote Thursday, January 19, 2017 10:18 AM > > > >> it would appear that my excursion into a regular workplace ended up > >> somewhat shortlived. Ouch, that sucks.

Re: LilyDev 5.0 released

2017-01-19 Thread Paul
On 01/19/2017 08:16 PM, Paul wrote: Well, this is probably good and bad news, but I tried the netinst Debian testing iso (i386 with LXDE) and it's working fine. (Oddly enough it works both with and without PAE/NX enabled.) I spoke too soon. Although it worked at first, I'm now having the

Re: LilyDev 5.0 released

2017-01-19 Thread Federico Bruni
Il giorno ven 20 gen 2017 alle 2:16, Paul ha scritto: Hi Federico, On 01/19/2017 06:35 AM, Federico Bruni wrote: If you have some time, can you try installing another Debian testing iso? Choose the netinst ISO for your architecture here:

Re: Back in the Pond

2017-01-19 Thread David Kastrup
Alexander Kobel writes: > +1. A personal wish: I think that \lyricsto ChoirStaff = "ctx" { > ... } has the potential to be a killer feature w.r.t. usability for > choir literature (especially combined with the upcoming automatic > extenders). Unfortunately, assignment of