Re: Back in the Pond

[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 lyrics to *container*
> contexts does not work (at least, not reliably), and extender
> generation is completely defunct.

Uh, I thought that people replaced extenders right now?

> I reported that in a thread from 2016-12-26 on bug-lilypond, but could
> not motivate any supporters yet.

The container context issue would want to be tackled by a melisma
translator (working both in Midi and PDF since we want the same results
there).  That work is unfinished and somewhat pervasive.  So it's a bit
unlikely for 2.20.

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LilyDev 5.0 released

[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:

https://www.debian.org/devel/debian-installer/

This would help to understand if the problem is in LilyDev or in 
Debian. I guess it's the latter.
Probably some hardware/kernel problem. I'm just guessing, I never 
experienced these problems.


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.)


Maybe I'll use this as an opportunity to try setting up all the dev 
dependencies from scratch?


This is what I'd recommend. If you managed to get the VM working...



I tried installing LilyDev5 on my old mac laptop.  It installs 
fine, and I can boot into LXQT, entering my password, but then 
there seems to be some problem with the mouse/keyboard 
integration as I can't get it to respond to clicks or key presses 
after I have logged in.


This is a problem of Virtual Box. I'm afraid that you should ask for 
help on Virtual Box forums.


I installed it on this old laptop just to see if it would work, but 
it is too old and slow to be of any real use.


Ok




virt-manager logs:

A. When installing virt-manager and dependencies via synaptic 
package manager:


W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user 
'_apt'. - pkgAcquire::Run (13: Permission denied)


https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1543280


Ah, thanks.


Unable to connect to libvirt.

Verify that:
 - The 'libvirt-bin' package is installed


$ aptitude show libvirt-bin


Synaptic package manager shows that it's installed.  (I tried that 
command but I don't have aptitude installed.)


Ok




 - The 'libvirtd' daemon has been started


$ systemctl status libvirtd


Looks like I did manage to get this started, as confirmed by this 
command.



- You are member of the 'libvirtd' group


$ groups


Looks like there is no libvirtd group.  So that's probably it.


I see that 16.04 is Yakkety, so according to the guide below you should 
add your user to libvirt. You can do it with this command:


$ sudo adduser $USER libvirt

Then exit the session, log in again and check that it is now present:

$ groups





Have you verified these points?
IIRC you are quite new to Linux and use Ubuntu in your host machine, 
right? Which version?

Yes, still pretty new at it.  Ubuntu 16.04 is my host machine.


Read this guide:
https://help.ubuntu.com/lts/serverguide/libvirt.html

In later versions of libvirt the correct group is libvirt (instead 
of libvirtd). That's the case for Fedora25, libvirt version 2.2.0.


Thanks for the tips and all your work on LilyDev!  At this point I 
may just stick with VirtualBox rather than try to get up to speed 
with libvirt (assuming things go well with this new debian vm).


I realize now that I may have suggested a simpler command to check if 
Virtual Box is the problem or not. Please try running this in a 
terminal:


kvm -cdrom lilydev-bla-bla.iso -boot d -m 2048






___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LilyDev 5.0 released

[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 same 
problem with the vanilla debian VM that I have with LilyDev5...  sigh...


-Paul

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Back in the Pond

[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.  :(

> Well, the 2.20 release stoppers of course should be tackled.  Step 1
> IIRC was to contact the persons last having worked on three issues you
> identified.  Uhm, I'd be glad to leave that in Graham's hand, at least
> until it's clear that addressing those issues will have to be done by
> somebody else.

Right, I haven't forgotten, but I likely won't get to this until
Feb.  I've had a poor (and rare) reaction to some recent
vaccinations [1], and lost most of 5 days in the past two weeks.
I'm not certain how much energy I'll have after catching up on
work, and getting some work done for a Feb 4 board meeting for an
(offline) amateur music organization.

[1] I don't regret getting the vaccinations, since it's an
important public health issue and most people with whom I go
ballroom dancing are seniors.  For me personally, I'd be willing
to take my chances with the flu or even MMR, but for the elderly
those illnesses could well be fatal.  I just wish that I'd had a
better idea that I'd be one of the unusual people who have bad
side effects.  :(

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

python include path oddity with "make install"

[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:
python/relocate-preamble.py.in
but it seems to assume that "current" is a valid $(VERSION).
I know that GUB does add a symlink for "current", but that doesn't
appear to happen for "make install".


I can see a few different ways forward:
- figure out why the @lilypond_datadir@ replacement is going to
  /usr/...  instead of $(PREFIX)
- add a "current" symlink
- add some more directories to the system path in
  relocate-preamble.py.in

Unfortunately, I've lost a lot of steam on this and am not likely
to return to it until Feb.  I'd rather not hold back the
pure-python midi2ly change, so it would be awesome if somebody
else could clarify matters and/or fix it.

Cheers,
- Graham

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

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

[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

(assuming that you installed to $HOME/.local/ )

Description:
Remove midi.c


midi2ly: replace unprintables with ~


midi2ly: fix non-printable in MIDI text


Add rewrite of midi.c in python

Work was done in 2012, and came from here:
https://codereview.appspot.com/7016046/

Please review this at https://codereview.appspot.com/312300043/

Affected files (+211, -474 lines):
  M python/GNUmakefile
  D python/midi.c
  A python/midi.py
  M scripts/midi2ly.py



___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LilyDev 5.0 released

[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 in 
Debian. I guess it's the latter.
Probably some hardware/kernel problem. I'm just guessing, I never 
experienced these problems.


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.)


Maybe I'll use this as an opportunity to try setting up all the dev 
dependencies from scratch?


I tried installing LilyDev5 on my old mac laptop.  It installs fine, 
and I can boot into LXQT, entering my password, but then there seems 
to be some problem with the mouse/keyboard integration as I can't get 
it to respond to clicks or key presses after I have logged in.


This is a problem of Virtual Box. I'm afraid that you should ask for 
help on Virtual Box forums.


I installed it on this old laptop just to see if it would work, but it 
is too old and slow to be of any real use.



virt-manager logs:

A. When installing virt-manager and dependencies via synaptic package 
manager:


W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)


https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1543280


Ah, thanks.


Unable to connect to libvirt.

Verify that:
 - The 'libvirt-bin' package is installed


$ aptitude show libvirt-bin


Synaptic package manager shows that it's installed.  (I tried that 
command but I don't have aptitude installed.)



 - The 'libvirtd' daemon has been started


$ systemctl status libvirtd


Looks like I did manage to get this started, as confirmed by this command.


- You are member of the 'libvirtd' group


$ groups


Looks like there is no libvirtd group.  So that's probably it.


Have you verified these points?
IIRC you are quite new to Linux and use Ubuntu in your host machine, 
right? Which version? 


Yes, still pretty new at it.  Ubuntu 16.04 is my host machine.


Read this guide:
https://help.ubuntu.com/lts/serverguide/libvirt.html

In later versions of libvirt the correct group is libvirt (instead of 
libvirtd). That's the case for Fedora25, libvirt version 2.2.0.


Thanks for the tips and all your work on LilyDev!  At this point I may 
just stick with VirtualBox rather than try to get up to speed with 
libvirt (assuming things go well with this new debian vm).


Thanks again,
-Paul


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Back in the Pond

[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 had better luck with that endeavor...


So for the short time range, I am again dependent
on support by other LilyPond lovers.


I'll definitely turn on my financial contribution again.


Ditto, although it's just a drop in a mostly empty bucket...


So what's next on my agenda?
[...]
And, of course, this is an opportunity to try putting out the 2.20
release finally.


Definitely the top priority, IMO.


+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 lyrics to *container* contexts does not 
work (at least, not reliably), and extender generation is completely 
defunct. I reported that in a thread from 2016-12-26 on bug-lilypond, 
but could not motivate any supporters yet.


I saw a comment by you that you are aware of the issue; can't remember 
where, it was at some point during my (unsuccessful) debugging streak 
for the problem - might well be a very old comment in the issue tracker 
or a commit message or the like.  May I kindly ask you to have a look 
and think about whether this might be tackleable before 2.20?  I have no 
good intuition for the complexity of this issue; the *specification* 
part should be reasonably simple (which syllable corresponds to which 
note(s)), but I don't know what kind of difficulties the current design 
presents for actually coding it.



Cheers,
Alexander

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

C++ question:

[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 = Font_interface::text_font_alist_chain (me);
  SCM ws_mol = Text_interface::interpret_markup (me->layout ()->self_scm (), 
properties, ly_string2scm ("\\markup {\\bold foo}"));
  Stencil ws = *unsmob (ws_mol);

That emits "\markup {\bold foo}" instead of the result of the interpreted 
markup. If I define a property test-markup,
replace 'ly_string2scm ("\\markup {\\bold foo}")' with something like  'me->get_property 
("test-markup")' the code works
as expected. So ly_string2scm is not enough ... I need a string2markup(). Any 
idea?


 Knut

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Back in the Pond

[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

Re: Back in the Pond

[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
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Back in the Pond

[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 range, I am again dependent 
>> on support by other LilyPond lovers.
>
> I'll definitely turn on my financial contribution again.

Very much appreciated.

>> So what's next on my agenda?  
>>
>> One somewhat long-standing goal was to remove LilyPond's own
>> implementation of a Rational data type and replace it by one based on
>> Guile's arbitrary-precision arithmetic.
>
> Worthwhile, but best left for 2.21 I think.

Well, the 2.20 release stoppers of course should be tackled.  Step 1
IIRC was to contact the persons last having worked on three issues you
identified.  Uhm, I'd be glad to leave that in Graham's hand, at least
until it's clear that addressing those issues will have to be done by
somebody else.

And the Moment/Rational/Midi-gc stuff is already in reasonable state of
progress in private branches so I don't want to let it get cold.

But of course it is an open question whether it makes sense to admit it
into 2.20.0 (or was the first version 2.20.1).  More likely than not,
not.  So that already gives an incentive for branching off the 2.20
release branch very soon.

>> I am glad that I'll be able to provide technical support and
>> expertise at least for a while and thus hopefully help Graham pick up
>> the reins of the overall project governance a bit better.
>
> Excellent!
>
>> And, of course, this is an opportunity to try putting out the 2.20
>> release finally.
>
> Definitely the top priority, IMO.
>
>> But at any rate, I hope to be on board at least for making LilyPond 2.20
>> a thing.
>
> :)
>
> Trevor

-- 
David Kastrup

___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Back in the Pond

[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 lovers.

I'll definitely turn on my financial contribution again.

> So what's next on my agenda?  
>
> One somewhat long-standing goal was to remove LilyPond's own
> implementation of a Rational data type and replace it by one based on
> Guile's arbitrary-precision arithmetic.

Worthwhile, but best left for 2.21 I think.
 
> I am glad that I'll be able to provide technical support and expertise
> at least for a while and thus hopefully help Graham pick up the reins of
> the overall project governance a bit better.

Excellent!

> And, of course, this is an opportunity to try putting out the 2.20
> release finally.  

Definitely the top priority, IMO.

> But at any rate, I hope to be on board at least for making LilyPond 2.20
> a thing.

:)

Trevor
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: LilyDev 5.0 released

[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 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 in 
Debian. I guess it's the latter.
Probably some hardware/kernel problem. I'm just guessing, I never 
experienced these problems.




- please try also installing LilyDev with virt-manager: 
https://virt-manager.org/


I gave that a try but did not get far.  Seems to be a dependency or 
permissions issue I couldn't figure out.  Error messages below.


I hope to make a new release of LilyDev this week. I'd be interested 
to know if making LilyDev work for you requires some change to 
LilyDev itself (I don't think so, but let's see..).


I tried installing LilyDev5 on my old mac laptop.  It installs fine, 
and I can boot into LXQT, entering my password, but then there seems 
to be some problem with the mouse/keyboard integration as I can't get 
it to respond to clicks or key presses after I have logged in.


This is a problem of Virtual Box. I'm afraid that you should ask for 
help on Virtual Box forums.




-Paul


virt-manager logs:

A. When installing virt-manager and dependencies via synaptic package 
manager:


W: Can't drop privileges for downloading as file 
'/root/.synaptic/tmp//tmp_sh' couldn't be accessed by user '_apt'. - 
pkgAcquire::Run (13: Permission denied)


https://bugs.launchpad.net/ubuntu/+source/aptitude/+bug/1543280



B. When using virt-manager:


Unable to connect to libvirt.

Verify that:
 - The 'libvirt-bin' package is installed
 - The 'libvirtd' daemon has been started

Libvirt URI is: lxc:///

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 903, 
in _do_open

self._backend.open(self._do_creds_password)
  File "/usr/share/virt-manager/virtinst/connection.py", line 148, in 
open

open_flags)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 105, in 
openAuth

if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: Failed to connect socket to 
'/var/run/libvirt/libvirt-sock': Permission denied



Unable to connect to libvirt.

Verify that:
 - The 'libvirt-bin' package is installed


$ aptitude show libvirt-bin



 - The 'libvirtd' daemon has been started


$ systemctl status libvirtd



 - You are member of the 'libvirtd' group


$ groups

Have you verified these points?
IIRC you are quite new to Linux and use Ubuntu in your host machine, 
right? Which version? Read this guide:

https://help.ubuntu.com/lts/serverguide/libvirt.html

In later versions of libvirt the correct group is libvirt (instead of 
libvirtd). That's the case for Fedora25, libvirt version 2.2.0.





Libvirt URI is: qemu:///system

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/connection.py", line 903, 
in _do_open

self._backend.open(self._do_creds_password)
  File "/usr/share/virt-manager/virtinst/connection.py", line 148, in 
open

open_flags)
  File "/usr/lib/python2.7/dist-packages/libvirt.py", line 105, in 
openAuth

if ret is None:raise libvirtError('virConnectOpenAuth() failed')
libvirtError: Failed to connect socket to 
'/var/run/libvirt/libvirt-sock': Permission denied






___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Back in the Pond

[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


___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Re: Make failng in translation branch

[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
the new version of lilydev?


No, you shouldn't. Because LilyDev 5 is based on Debian testing and 
it's using guile-2.0 by default (guile-1.8 was removed from testing 
repositories in the meanwhile, so installing it requires using pinning).

So keep using LilyDev 4.


Curious thing is it was compiling fine
only two weeks ago on my previous round of translation (already
merged). I presume this has nothing to do with my translations as it
happens already with "make" and not "make doc". These are the last
lines when it shows the error:

make[1]: Entering directory
'/home/wgarcia/lilypond-git/build/Documentation'
/home/wgarcia/lilypond-git/./Documentation/GNUmakefile:2: config.make:
No such file or directory
make/stepmake.make:1: config.make: No such file or directory
/home/wgarcia/lilypond-git/./Documentation/make/stepmake.make:1:
config.make: No such file or directory
/home/wgarcia/lilypond-git/./make/stepmake.make:69: config.make: No
such file or directory
make/toplevel-version.make:1: config.make: No such file or directory
/home/wgarcia/lilypond-git/./Documentation/make/toplevel-version.make:1:
config.make: No such file or directory
local.make:1: config.make: No such file or directory
make/generic-vars.make:1: config.make: No such file or directory
/home/wgarcia/lilypond-git/./Documentation/make/generic-vars.make:1:
config.make: No such file or directory
make/lilypond-vars.make:1: config.make: No such file or directory
/home/wgarcia/lilypond-git/./Documentation/make/lilypond-vars.make:1:
config.make: No such file or directory
make/generic-rules.make:1: config.make: No such file or directory
/home/wgarcia/lilypond-git/./Documentation/make/generic-rules.make:1:
config.make: No such file or directory
make/substitute.make:1: config.make: No such file or directory
/home/wgarcia/lilypond-git/./Documentation/make/substitute.make:1:
config.make: No such file or directory
make/lilypond-rules.make:1: config.make: No such file or directory
/home/wgarcia/lilypond-git/./Documentation/make/lilypond-rules.make:1:
config.make: No such file or directory
make/generic-targets.make:1: config.make: No such file or directory
/home/wgarcia/lilypond-git/./Documentation/make/generic-targets.make:1:
config.make: No such file or directory
make/lilypond-targets.make:1: config.make: No such file or directory
/home/wgarcia/lilypond-git/./Documentation/make/lilypond-targets.make:1:
config.make: No such file or directory
mkdir -p ./out
touch ./out/dummy.dep
echo '*' > ./out/.gitignore

configure changed! You should probably reconfigure manually.

(cd /home/wgarcia/lilypond-git/build/Documentation; ./config.status)
/bin/sh: 1: ./config.status: not found
/home/wgarcia/lilypond-git/stepmake/stepmake/generic-targets.make:147:
recipe for target 'config.make' failed
make[1]: *** [config.make] Error 127
make[1]: Leaving directory
'/home/wgarcia/lilypond-git/build/Documentation'
/home/wgarcia/lilypond-git/stepmake/stepmake/generic-targets.make:6:
recipe for target 'all' failed
make: *** [all] Error 2



Have you tried cleaning and reconfigure?

make clean
./autogen.sh
make








___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel

Back in the Pond

[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
shortlived code (rather than the multiple-decade timespan projects that
LilyPond, TeX, and Emacs sport) combine with a competitive amount of
immediately visible productivity.

This was actually not as much an opportunity I had myself actively
sought out but rather an interview a friend of mine had arranged because
my finances were not really working out with LilyPond.

I don't quite know where to go from here, so I'm pretty sure to be
around at least for February back in the Pond, and I'll probably take a
look at what options we have to divert donations through the FSF.  They
take a 10 percent cut, but they also handle credit card processing and
other stuff, and of course there would be no need to notify people in
case I left again: the project obviously could somewhat comfortably
revert to making use of money independently in order to pay for some
long-standing coding projects.

Of course, going via the FSF and a project-specific fund would mean that
we would need some sort of mechanism to actually decide what to use the
money for.

I have been not overly successful in providing regular accountability to
my personal supporters, so it remains to be seen how I would fare with
more visible requirements to reports.

While my short excursion into more regular work places has provided a
short breath of relief financially, those were also offset by a number
of acquisitions made both for immediate needs connected with having to
maintain two households as well as making some long-required or desired
acquisitions not previously deemed affordable.

The long and the short of it is that I'll not be able to, say, hold out
half a year until other financial arrangements catch hold.  And I don't
really have a view on how much of a positive difference routing part of
LilyPond financing through the FSF could have.

So for the short time range, I am again dependent on support by other
LilyPond lovers.

Sorry for turning on dime again here.

So what's next on my agenda?  Finishing some started work that was more
or less stepped in mid-stride by my excursion into the regular
workplace.  One somewhat long-standing goal was to remove LilyPond's own
implementation of a Rational data type and replace it by one based on
Guile's arbitrary-precision arithmetic.

This is a multistep endeavor.

Step 1 is putting the data structures of the Midi backend under Guile
garbage collection control (so far, they are just allocated in C++ and
never released.  It doesn't make much of an impact because the Midi data
is so much less than what is used for visual typesetting, but it's
disconcerting a bit).

This is necessary because various timing data is stored in the Midi data
structures, and using Guile rationals for that requires tieing the data
structures into Guile's garbage collection.

Next step is making all musical Moment data structures (optionally tied
into Guile/SCM already as Simple_smob) and the occurences of the
Rational data type (so far not tied to Guile at all) properly
garbage-collected.  Then the Rational data type needs to be replaced by
a C++ wrapper for Guile's SCM data type (in order not to have to rewrite
a lot of code, the Rational data type itself and its conversion
functions would likely remain but be reimplemented in terms of Guile
arithmetic).

That would likely cater for most problems of becoming
arbitrary-precision (with "arbitrary" actually meaning a few million
digits).  For the overwhelming number of scores, this should not make
much of a difference.  I expect a bit of performance impact.

But nothing comparable to the Guile 2 transition (if and when we go that
route eventually).  With regard to Guile 2, we'll need to figure out a
viable programming and communication strategy and also decide whether we
rather make Guile 1.8 work privately for us.

That will also have an influence on deciding how to progress technically
with our MusicXML support.

I am glad that I'll be able to provide technical support and expertise
at least for a while and thus hopefully help Graham pick up the reins of
the overall project governance a bit better.

At the very least, I'll be able to get a bit on my ongoing work queue
flushed out which was left in a dissatisfactorily unfinished state by my
departure and which would likely have taken half to a year to clear in
most parts while having a regular main job.

And, of course, this is an opportunity to try putting out the 2.20
release finally.  I'll take stock of how to deal with our showstoppers
in that area soonish if Graham does not beat me to it: it's one of those
tasks which have so many open ends that I easily lose focus, and much of
it is trying to figure out the status of previous