Re: GUB again
>> I've seen a proposed patch from Masamichi, but as David says, this may >> fix the issue but doesn't shed any light on what is the root cause. >> Is it worth trying to go back to an earlier version of gcc? If so, >> how would I go about that? > > I lean towards just using Masamichi's patch. I'll pull request following branch if it's necessary. https://github.com/trueroad/gub/tree/fix-librestrict ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB and mpfr/mpc
> I agree that changing the algorithms is preferred; I didn’t mean to suggest > otherwise. But if that’s not going to happen overnight, and there is a way > to mitigate the problem in the meantime without touching the code, the people > affected would value it. I tried "-mfpmath=sse -msse2". It worked fine. bad_alloc didn't occur. Correct PDF was generated. It can be a workaround until changing the algorithms. ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB and mpfr/mpc
Masamichi HOSODA writes: >> I agree that changing the algorithms is preferred; I didn’t mean to > suggest otherwise. But if that’s not going to happen overnight, and > there is a way to mitigate the problem in the meantime without > touching the code, the people affected would value it. > > I tried "-mfpmath=sse -msse2". > It worked fine. bad_alloc didn't occur. > Correct PDF was generated. > > It can be a workaround until changing the algorithms. It's not architecture independent. And may blow up for other reasons. -- David Kastrup ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
PATCHES: Countdown for December 11th 2014
Hello, Here is the current patch countdown list. The next countdown will be on December 11th. You can always view the most current countdown list here: http://code.google.com/p/lilypond/issues/list?q=Patch%3Apush%2Ccountdown%2Creview%2Cnew%2Cwaiting&colspec=Patch%20Owner%20ID%20Summary&sort=patch PUSH: Dan Eble: Patch: Add an alternative quarter rest shaped like a mirrored Z. http://code.google.com/p/lilypond/issues/detail?id=4211 Dan Eble: Patch: Convert ly::time-signature::print from C++ to Scheme. http://code.google.com/p/lilypond/issues/detail?id=4204 David Kastrup: Chord repeats should not repeat forced/cautionary accidentals http://code.google.com/p/lilypond/issues/detail?id=4010 COUNTDOWN: James Lowe: Web: Google Summer of Code (GSoC) Webpage needs updating/removing/hiding http://code.google.com/p/lilypond/issues/detail?id=4215 James Lowe: Web: Add Elaine Gould's Behind Bars to the literature list http://code.google.com/p/lilypond/issues/detail?id=4206 James Lowe: Website: add lilybin.com to Easier editing http://code.google.com/p/lilypond/issues/detail?id=4199 Keith OHara: Give compressed multi-measure rests more space http://code.google.com/p/lilypond/issues/detail?id=4197 James Lowe: MusicXML test suite: test description in 41f-StaffGroups-Overlapping.xml is incorrect http://code.google.com/p/lilypond/issues/detail?id=4177 Keith OHara: allow bn for B-natural in English http://code.google.com/p/lilypond/issues/detail?id=4076 WAITING: Urs Liska: Patch: Add original-breaks.ly commands http://code.google.com/p/lilypond/issues/detail?id=4155 Urs Liska: Patch: Issue 3916: Add \alternatingTimeSignatures http://code.google.com/p/lilypond/issues/detail?id=3918 Mike Solomon: Patch: Prevents vertical axis groups with empty skylines http://code.google.com/p/lilypond/issues/detail?id=3156 Mike Solomon: Patch: Removes the translate_axis call from axis-group-interface outside-staff positioning. http://code.google.com/p/lilypond/issues/detail?id=3134 David Kastrup: Patch: Implement music functions in Scheme rather than C++ http://code.google.com/p/lilypond/issues/detail?id=2716 Thank you, James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Web: Essay - Add Elaine Gould's book Behind Bars (issue 187860043 by pkx1...@gmail.com)
LGTM https://codereview.appspot.com/187860043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
mentorship
Dear Lilypond developers, I read in the contributor's guide that there is a system of mentorship for people who would like to help the project. Is that still the case? And if so how do I get involved in it. Kevin ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web: Update GSoc entry (issue 180650043 by pkx1...@gmail.com)
One more thing. https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi File Documentation/web/community.itexi (right): https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi#newcode965 Documentation/web/community.itexi:965: enharmonic notes @code{@{ cis'~ des' @}} and ties @q{broken} by clef or I think ties on enharmonic notes are recently fixed thanks to dak (issue 461). https://codereview.appspot.com/180650043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web: Update GSoc entry (issue 180650043 by pkx1...@gmail.com)
Am 08.12.2014 21:24, schrieb paulwmor...@gmail.com: One more thing. https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi File Documentation/web/community.itexi (right): https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi#newcode965 Documentation/web/community.itexi:965: enharmonic notes @code{@{ cis'~ des' @}} and ties @q{broken} by clef or I think ties on enharmonic notes are recently fixed thanks to dak (issue 461). Not completely. LilyPond now accepts enharmonic ties and engraves them, but they are not rendered correctly. They are still ties, i.e. horizontal, symmetric curves by default. So if one has any demands on output one has to \shape it. But nevertheless it's a great improvement allowing one to enter semantically correct input. Urs https://codereview.appspot.com/180650043/ ___ 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: Web: Update GSoc entry (issue 180650043 by pkx1...@gmail.com)
LGTM, just caught a few minor things. -Paul https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi File Documentation/web/community.itexi (right): https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi#newcode897 Documentation/web/community.itexi:897: looking for other to participate in future programs. other -> others https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi#newcode908 Documentation/web/community.itexi:908: There are many more things that can be done to improve in LilyPond and to improve LilyPond https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi#newcode919 Documentation/web/community.itexi:919: multiple staffs are used were some have grace notes and others don't. were -> where https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi#newcode964 Documentation/web/community.itexi:964: The default curves of slur and ties are often unsatisfactory. Ties on slur -> slurs https://codereview.appspot.com/180650043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: GUB and mpfr/mpc
> On Dec 8, 2014, at 08:21 , David Kastrup wrote: > > Masamichi HOSODA writes: > >>> I agree that changing the algorithms is preferred; I didn’t mean to >> suggest otherwise. But if that’s not going to happen overnight, and >> there is a way to mitigate the problem in the meantime without >> touching the code, the people affected would value it. >> >> I tried "-mfpmath=sse -msse2". >> It worked fine. bad_alloc didn't occur. >> Correct PDF was generated. >> >> It can be a workaround until changing the algorithms. > > It's not architecture independent. And may blow up for other reasons. But it’s good to know that the problem was floating point and not memory corruption, so thanks for testing it. — Dan ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: mentorship
Hello Kevin, On 08/12/14 20:08, Kevin Barry wrote: > Dear Lilypond developers, > > I read in the contributor's guide that there is a system of mentorship for > people who would like to help the project. Is that still the case? And if > so how do I get involved in it. > > Kevin Thank you for taking the time to ask. It depends on which part of LilyPond you want to help with as to the availability of people to help you. Is there a particular skill-set, set of issues or area of LilyPond you are particularly interested in? Regards James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Web: Update GSoc entry (issue 180650043 by pkx1...@gmail.com)
On 08/12/14 20:37, Urs Liska wrote: > > Am 08.12.2014 21:24, schrieb paulwmor...@gmail.com: >> One more thing. >> >> >> https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi >> >> File Documentation/web/community.itexi (right): >> >> https://codereview.appspot.com/180650043/diff/20001/Documentation/web/community.itexi#newcode965 >> >> Documentation/web/community.itexi:965: enharmonic notes @code{@{ cis'~ >> des' @}} and ties @q{broken} by clef or >> I think ties on enharmonic notes are recently fixed thanks to dak (issue >> 461). > > Not completely. > LilyPond now accepts enharmonic ties and engraves them, but they are not > rendered correctly. > They are still ties, i.e. horizontal, symmetric curves by default. > So if one has any demands on output one has to \shape it. > > But nevertheless it's a great improvement allowing one to enter > semantically correct input. > As this patch was more about generalities than specifics, I have taken out the few words anyway. James ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: mentorship
> It depends on which part of LilyPond you want to help with as to the > availability of people to help you. Is there a particular skill-set, set > of issues or area of LilyPond you are particularly interested in? Thank you for responding. I would like to be able to contribute code to the project but I'm not really a programmer (I'm a music academic). I worked through some chapters of SICP in the past, so I have a rudimentary understanding of ... the first few chapters of SICP. I would like to learn more, if that's something that would help. Otherwise I will help any way that might be needed. I don't have any specific goals other than contributing somehow and maybe learning more about programming along the way. Kevin ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: Docs: state that LilyPond input is in terms of pitches (issue 185140043 by k-ohara5...@oco.net)
Fails make. https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/common-notation.itely File Documentation/learning/common-notation.itely (right): https://codereview.appspot.com/185140043/diff/20001/Documentation/learning/common-notation.itely#newcode119 Documentation/learning/common-notation.itely:119: @node Pitches Problem with calling this node 'Pitches' is that it throws an error as it has been previously defined in another @node in this doc. You'll need to change it. https://codereview.appspot.com/185140043/ ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel