Re: guile-2.0 and debian
Hi everyone,
On Mon, 14 Nov 2016 01:15:52 +0100
David Kastrup wrote:
> Thomas Morley writes:
>
> > Short update:
> > I managed to get guile 2.0.13 and guile-2.0-dev for 2.0.13 (grabed it
> > from Zesty Zapus which will be Ubuntu 17.04)
> > Successful make with all of Antonios patches (didn't try make doc so far).
> >
In the latest version of my notes I forgot to mention that I am using
2.0.13 from Debian unstable. It was in the first draft.
> > Though, _every_ compilation of a .ly will cause a gs-error.
> >
> > Even for { c1 } I get:
> >
> > lilypond-git atest-40.ly
> > GNU LilyPond 2.19.51
> > Processing `atest-40.ly'
> > Parsing...
> > Interpreting music...
> > Preprocessing graphical objects...
> > Finding the ideal number of pages...
> > Fitting music on 1 page...
> > Drawing systems...
> > Layout output to `/tmp/lilypond-6s1XBB'...
> > Converting to `atest-40.pdf'...
> > warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595,28
> > -dDEVICEHEIGHTPOINTS=841,89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH
> > -r1200 -sDEVICE=pdfwrite -sOutputFile=atest-40.pdf -c.setpdfwrite
> > -f/tmp/lilypond-6s1XBB)' failed (256)
> >
> > fatal error: failed files: "atest-40.ly"
> >
> > Will try to continue tomorrow, too late today.
>
> That one is going to be another (re)encoding error, this time when
> writing PostScript. It may or may not be a different problem than the
> ones I experienced: Masamichi-san fairly recently made some changes to
> font handling that also were concerned with byte transparency.
>
Thomas what is your locale?
If run lilypond with my default locale (LANG=it_IT.utf8) I get this
error too; as I wrote somewhere, running the "gs" command on its own
showed that in my case this was due to the EPS file containing commas
as decimal separator instead of periods.
Running lilypond like this worked around the issue for me:
$ LANG=C lilypond-git atest-40.ly
Does this work for you too?
BTW setting only LC_NUMERIC instead of LANG could be enough.
As happened often in my naive attempt to move things forward I could
spot where the problem was but due to my lack of knowledge about
lilypond and guile I am not always able to figure out what the correct
fix is.
For instance if David, or someone else, could confirm that patch 0005
[1] actually makes sense I would propose it for inclusion in lilypond.
Thanks,
Antonio
[1]
https://ao2.it/tmp/lilypond-guile2/0005-Fix-ending-the-dynamic-extent-in-Text_interface-inte.patch
--
Antonio Ospite
https://ao2.it
https://twitter.com/ao2it
A: Because it messes up the order in which people normally read text.
See http://en.wikipedia.org/wiki/Posting_style
Q: Why is top-posting such a bad thing?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
Antonio Ospite writes: > For instance if David, or someone else, could confirm that patch 0005 > [1] actually makes sense I would propose it for inclusion in lilypond. > > Thanks, >Antonio > > [1] > https://ao2.it/tmp/lilypond-guile2/0005-Fix-ending-the-dynamic-extent-in-Text_interface-inte.patch [Forehead-slap] Looks like the right thing to do but it seems like moving it the scm_dynwind_end call before anything else is done might be better since non_fatal_error might cause a fatal error (depending on command line options) and I am not completely sure that a non-local C++ exit will properly count as a non-local Scheme exit according to scm_dynwind_end's documentation. It's a non-brainer so I might just push a fix without further notice if it's ok with you that I'm stealing your credit in that manner. If it's not ok, I'll get your patch and commit message and do that change with you as author. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
On Mon, 14 Nov 2016 14:07:08 +0100 David Kastrup wrote: > Antonio Ospite writes: > > > For instance if David, or someone else, could confirm that patch 0005 > > [1] actually makes sense I would propose it for inclusion in lilypond. > > > > Thanks, > >Antonio > > > > [1] > > https://ao2.it/tmp/lilypond-guile2/0005-Fix-ending-the-dynamic-extent-in-Text_interface-inte.patch > > [Forehead-slap] Looks like the right thing to do but it seems like > moving it the scm_dynwind_end call before anything else is done might be > better since non_fatal_error might cause a fatal error (depending on > command line options) and I am not completely sure that a non-local C++ > exit will properly count as a non-local Scheme exit according to > scm_dynwind_end's documentation. > > It's a non-brainer so I might just push a fix without further notice if > it's ok with you that I'm stealing your credit in that manner. If it's > not ok, I'll get your patch and commit message and do that change with > you as author. > Sure, if your change is different and better than mine, go a head and take credit, maybe mention my name in the commit message, with something like a Thanks-to or a Reported-by tag, but it's not a big deal. After this was fixed I noticed that I was getting the warnings in a different order compared to what markup-cyclic-reference.ly was expecting, see patch 0006[1]. I am not sure if this happens with guile-1.8 too, so if you got the chance take a look at that too, please. Thanks again, Antonio [1] https://ao2.it/tmp/lilypond-guile2/0006-Fix-the-expected-warning-with-guile-2-in-markup-cycl.patch -- Antonio Ospite https://ao2.it https://twitter.com/ao2it A: Because it messes up the order in which people normally read text. See http://en.wikipedia.org/wiki/Posting_style Q: Why is top-posting such a bad thing? ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
Antonio Ospite writes: > On Mon, 14 Nov 2016 14:07:08 +0100 > David Kastrup wrote: > >> Antonio Ospite writes: >> >> > For instance if David, or someone else, could confirm that patch 0005 >> > [1] actually makes sense I would propose it for inclusion in lilypond. >> > >> > Thanks, >> >Antonio >> > >> > [1] >> > https://ao2.it/tmp/lilypond-guile2/0005-Fix-ending-the-dynamic-extent-in-Text_interface-inte.patch >> >> [Forehead-slap] Looks like the right thing to do but it seems like >> moving it the scm_dynwind_end call before anything else is done might be >> better since non_fatal_error might cause a fatal error (depending on >> command line options) and I am not completely sure that a non-local C++ >> exit will properly count as a non-local Scheme exit according to >> scm_dynwind_end's documentation. >> >> It's a non-brainer so I might just push a fix without further notice if >> it's ok with you that I'm stealing your credit in that manner. If it's >> not ok, I'll get your patch and commit message and do that change with >> you as author. >> > > Sure, if your change is different and better than mine, go a head and > take credit, maybe mention my name in the commit message, with something > like a Thanks-to or a Reported-by tag, but it's not a big deal. Turns out that the commit message is a lot more work than the patch so I'll just keep yours around. > After this was fixed I noticed that I was getting the warnings in a > different order compared to what markup-cyclic-reference.ly was > expecting, see patch 0006[1]. I am not sure if this happens with > guile-1.8 too, so if you got the chance take a look at that too, > please. > https://ao2.it/tmp/lilypond-guile2/0006-Fix-the-expected-warning-with-guile-2-in-markup-cycl.patch I get the same warning here. It's due to the previous warning's lack of proper cleanup: if you remove the first expect-warning and its trigger, this will also occur with current LilyPond. So I better change this in the same patch. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
David Kastrup writes: > Antonio Ospite writes: > >> On Mon, 14 Nov 2016 14:07:08 +0100 >> David Kastrup wrote: >> >>> Antonio Ospite writes: >>> >>> > For instance if David, or someone else, could confirm that patch 0005 >>> > [1] actually makes sense I would propose it for inclusion in lilypond. >>> > >>> > Thanks, >>> >Antonio >>> > >>> > [1] >>> > https://ao2.it/tmp/lilypond-guile2/0005-Fix-ending-the-dynamic-extent-in-Text_interface-inte.patch >>> >>> [Forehead-slap] Looks like the right thing to do but it seems like >>> moving it the scm_dynwind_end call before anything else is done might be >>> better since non_fatal_error might cause a fatal error (depending on >>> command line options) and I am not completely sure that a non-local C++ >>> exit will properly count as a non-local Scheme exit according to >>> scm_dynwind_end's documentation. >>> >>> It's a non-brainer so I might just push a fix without further notice if >>> it's ok with you that I'm stealing your credit in that manner. If it's >>> not ok, I'll get your patch and commit message and do that change with >>> you as author. >>> >> >> Sure, if your change is different and better than mine, go a head and >> take credit, maybe mention my name in the commit message, with something >> like a Thanks-to or a Reported-by tag, but it's not a big deal. > > Turns out that the commit message is a lot more work than the patch so > I'll just keep yours around. > >> After this was fixed I noticed that I was getting the warnings in a >> different order compared to what markup-cyclic-reference.ly was >> expecting, see patch 0006[1]. I am not sure if this happens with >> guile-1.8 too, so if you got the chance take a look at that too, >> please. >> https://ao2.it/tmp/lilypond-guile2/0006-Fix-the-expected-warning-with-guile-2-in-markup-cycl.patch > > I get the same warning here. It's due to the previous warning's lack of > proper cleanup: if you remove the first expect-warning and its trigger, > this will also occur with current LilyPond. > > So I better change this in the same patch. Pushed this to staging. I have to apologize to the bug team for bypassing procedures a lot these days, but this one is simple and I can't really wait a lot for a drain of the pipeline if I want to get a few things in shape before leaving. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Stepping down and moving on
Hi David I can only echo the good wishes and thanks that others have already expressed. Lilypond is a great program - the more I use it the more I can see the potential if I can ever get my head around the finer points. Meanwhile the list provides great support, and you have been a major contributor to the on-list help as well as to the project itself. So - thanks again, and good luck in your new post. David On Wed, 2016-11-09 at 18:09 +0100, David Kastrup wrote: > Hi folks and team, > > while I haven't really occupied an official function in LilyPond > development, it's hard to deny that I have effectively functioned as > acting chief architect and vetter (with a rather mottled > performance). > > Partly in connection with a drop of my productivity particularly this > year, the amount of financial support for my work from members of the > LilyPond community went down from overall survivable to > disastrous. Of > course this is bitter for those of you that did contribute in > significant amounts to my subsistence but I have to be moving on. > > I have accepted a full-time development (and team management) > position > with another company. Due to their project and team expansion plans, > I will be starting already in December. > > This employment is in another city. I'll be travelling back and > forth > weekly for the foreseeable future. While I might be working on some > LilyPond side projects interesting to me occasionally, I will not be > able to do any serious amound of coordination or other activity > involving me with LilyPond's community. > > As my communication style has proven to be a somewhat mixed blessing > for > the purpose of attracting long-term developers, I expect that this > may > help in the long run for finding a different balance of areas > LilyPond > is getting worked on. > > During his tenure as LilyPond leader, Graham has demonstrated that > even > without a central technical lead there is a lot of potential to focus > the resources of people willing to work on and expand LilyPond and we > have been continuing to reap the results of his talent for organizing > people into useful teams even though I have not really figured out > how > to fill gaps in the various teams and tools managing LilyPond's > infrastructure to offset the "natural" amounts of fluctuation. > > I'll try seeing through the release of 2.20 in the little time > remaining > to me both before and after starting my job. My main worry is the > current comparative amount of instability with regard to font > handling, > and my main bad taste is that 2.20.1 will not be able to support > Guile 2: there is no way that anything deserving the label of > "stable" > and including Guile 2 will come about in the rest of my tenure. > > There are also several half-completed features that are a nuisance. > I do not expect to be able to to a significant amount of work on them > in > the foreseeable future. > > Once consequence, of course, is that my requirement for funding is > over. > I am greatly thankful to the people who have enabled me to keep > working > on LilyPond as long as I did, but what remains in my bank account, in > spite of being quite less than what I started with when working on > LilyPond, is sufficient to tide me over the time to my first > paycheck. > > So I would ask you to cancel any regular bank payments you might > still > have in place as of December: I don't see that I will have a > reasonable > chance at returning a tangible value for them. > > Thanks for making me stay in the pond as long as I did! > ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Back to work on Issue 4752: Add ly:one-page-breaking
Hi all, I have some time to work again on ly:one-page-breaking. Ideally I'd like to land it before 2.20 is released. I've just updated the patches so they apply to current master. James (or anyone), one possible complication was different gcc versions on different machines giving different results. If you have a chance, would you mind testing the patches to see if this is the case? Assuming there are still problems can you save and post the full log? For me make still succeeds on current LilyDev (gcc 4.9.2, g++ 4.9.2, Debian 4.9.2-10). https://sourceforge.net/p/testlilyissues/issues/4752/ https://codereview.appspot.com/288910043 http://lists.gnu.org/archive/html/lilypond-devel/2016-02/msg5.html Thanks, -Paul ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
Hi Antonio,
first of all, thanks a lot for working on this!
Regrettable during a working week I have very little time to work on a
serious issue like this one.
That said:
2016-11-14 13:13 GMT+01:00 Antonio Ospite :
> Hi everyone,
>
> On Mon, 14 Nov 2016 01:15:52 +0100
> David Kastrup wrote:
>
>> Thomas Morley writes:
>>
>> > Short update:
>> > I managed to get guile 2.0.13 and guile-2.0-dev for 2.0.13 (grabed it
>> > from Zesty Zapus which will be Ubuntu 17.04)
>> > Successful make with all of Antonios patches (didn't try make doc so far).
>> >
>
> In the latest version of my notes I forgot to mention that I am using
> 2.0.13 from Debian unstable. It was in the first draft.
>
>> > Though, _every_ compilation of a .ly will cause a gs-error.
>> >
>> > Even for { c1 } I get:
>> >
>> > lilypond-git atest-40.ly
>> > GNU LilyPond 2.19.51
>> > Processing `atest-40.ly'
>> > Parsing...
>> > Interpreting music...
>> > Preprocessing graphical objects...
>> > Finding the ideal number of pages...
>> > Fitting music on 1 page...
>> > Drawing systems...
>> > Layout output to `/tmp/lilypond-6s1XBB'...
>> > Converting to `atest-40.pdf'...
>> > warning: `(gs -q -dSAFER -dDEVICEWIDTHPOINTS=595,28
>> > -dDEVICEHEIGHTPOINTS=841,89 -dCompatibilityLevel=1.4 -dNOPAUSE -dBATCH
>> > -r1200 -sDEVICE=pdfwrite -sOutputFile=atest-40.pdf -c.setpdfwrite
>> > -f/tmp/lilypond-6s1XBB)' failed (256)
>> >
>> > fatal error: failed files: "atest-40.ly"
>> >
>> > Will try to continue tomorrow, too late today.
>>
>> That one is going to be another (re)encoding error, this time when
>> writing PostScript. It may or may not be a different problem than the
>> ones I experienced: Masamichi-san fairly recently made some changes to
>> font handling that also were concerned with byte transparency.
To exclude recent changes by Masamichi-san I checked out
commit ff3e029f198c72d88c1c2fd2db3ce12cce86e725
Author: Phil Holmes
Date: Mon Nov 7 14:11:25 2016 +
Release: bump VERSION.
and started freshly from there
>
> Thomas what is your locale?
~$ env|grep LANG
LANG=en_US.UTF-8
GDM_LANG=en
LANGUAGE=en
~$ env|grep LC_NUMERIC
LC_NUMERIC=de_DE.UTF-8
>
> If run lilypond with my default locale (LANG=it_IT.utf8) I get this
> error too; as I wrote somewhere, running the "gs" command on its own
> showed that in my case this was due to the EPS file containing commas
> as decimal separator instead of periods.
>
> Running lilypond like this worked around the issue for me:
>
> $ LANG=C lilypond-git atest-40.ly
>
> Does this work for you too?
> BTW setting only LC_NUMERIC instead of LANG could be enough.
I need to do both to make it work:
~/lilypondH/Test/forum$ LANG=C LC_NUMERIC=C lilypond-git atest-40.ly
GNU LilyPond 2.19.51
Processing `atest-40.ly'
Parsing...
Interpreting music...
Preprocessing graphical objects...
Interpreting music...
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 1 page...
Drawing systems...
Layout output to `/tmp/lilypond-cw8exx'...`scm_take_str' is
deprecated. Use scm_take_locale_stringn instead.
Converting to `atest-40.pdf'...
Deleting `/tmp/lilypond-cw8exx'...
Success: compilation successfully completed
(I remember you wrote about scm_take_str already)
Though, more serious:
You already wrote about stuff like
bääh = { c1 }
\new Staff \bääh
not working and suggested "A workaround is to only use ASCII
characters in macro names"
I know several users who would need to fix/rewrite most of their code
if we would go for this. But it would be considerable if really,
really nothing else is possible, imho
But this one is the current showstopper:
{ c1^\markup "büüh" }
See attached png.
Making LilyPond unusable for everyone.
Can you confirm the image?
Cheers,
Harm
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: guile-2.0 and debian
> I have to apologize to the bug team for bypassing procedures a lot > these days, but this one is simple and I can't really wait a lot for > a drain of the pipeline if I want to get a few things in shape > before leaving. As usual: Please proceed! I think we all have full confidence in your commits. Werner ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
