Issue 425 in lilypond: input/regression/spacing-non-adjacent-column2.ly
Issue 425: input/regression/spacing-non-adjacent-column2.ly http://code.google.com/p/lilypond/issues/detail?id=425 Comment #2 by chhitz: No, it still happens in 2.11.31. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 291 in lilypond: \glissando doesn't work properly with chords
Issue 291: \glissando doesn't work properly with chords http://code.google.com/p/lilypond/issues/detail?id=291 Comment #7 by gpermus: Added to docs, thanks. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > Joe Neeman escreveu: >> On Saturday 01 September 2007 09:00, Trevor Bača wrote: >>> On 8/31/07, Joe Neeman <[EMAIL PROTECTED]> wrote: On Friday 31 August 2007 23:17, Trevor Bača wrote: > Should I send the inputfile to either Joe or Han-Wen for testing > against .31? I'd be happy to take a look at it. >>> Thank you *so* much, Joe! Will send offlist ... >> >> I can't reproduce with git or the x86-linux binary. >> I get a segfault with the amd64 binary... in ghostscript (during the >> convert-to-pdf stage). If I take the .ps file and run it though the system's >> ghostscript, it works perfectly. So it seems to be a problem with the >> ghostscript that's included in the binary package. > > In the original report, it didn't crash in GS but in lily. > It looks as if someone needs to build a macos binary without > stripping. I have such a beast here, maybe Trevor could send me his failing file. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 425 in lilypond: input/regression/spacing-non-adjacent-column2.ly
Issue 425: input/regression/spacing-non-adjacent-column2.ly http://code.google.com/p/lilypond/issues/detail?id=425 Comment #3 by joeneeman: What platform and can you attach the output. Attached is what I get with the amd64 binary on the website. Attachments: spacing-non-adjacent-columns2.preview.png 4.1 KB Issue attribute updates: Status: Accepted Labels: -fixed_2_11_31 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 425 in lilypond: input/regression/spacing-non-adjacent-column2.ly
Issue 425: input/regression/spacing-non-adjacent-column2.ly http://code.google.com/p/lilypond/issues/detail?id=425 Comment #4 by chhitz: The public regression-test website and compiled with the official 2.11.32 binary for MacOSX (ppc) show the same output. Attachments: spacing-non-adjacent-columns2_2.11.32_macosx_ppc.png 4.4 KB -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.11.30 segmentation fault
On 9/2/07, Nicolas Sceaux <[EMAIL PROTECTED]> wrote: > Han-Wen Nienhuys <[EMAIL PROTECTED]> writes: > > > Joe Neeman escreveu: > >> On Saturday 01 September 2007 09:00, Trevor Bača wrote: > >>> On 8/31/07, Joe Neeman <[EMAIL PROTECTED]> wrote: > On Friday 31 August 2007 23:17, Trevor Bača wrote: > > Should I send the inputfile to either Joe or Han-Wen for testing > > against .31? > I'd be happy to take a look at it. > >>> Thank you *so* much, Joe! Will send offlist ... > >> > >> I can't reproduce with git or the x86-linux binary. > >> I get a segfault with the amd64 binary... in ghostscript (during the > >> convert-to-pdf stage). If I take the .ps file and run it though the > >> system's > >> ghostscript, it works perfectly. So it seems to be a problem with the > >> ghostscript that's included in the binary package. > > > > In the original report, it didn't crash in GS but in lily. > > It looks as if someone needs to build a macos binary without > > stripping. > > I have such a beast here, maybe Trevor could send me his failing file. Excellent! I'll send you the file offlist in just a second ... and you can feed it to the beast ;-) -- Trevor Bača [EMAIL PROTECTED] ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 439 in lilypond: script collides with cross-staff beam
Issue 439: script collides with cross-staff beam
http://code.google.com/p/lilypond/issues/detail?id=439
New issue report by wbsoft:
%{
the dynamic collides with the cross-staff beam and stems.
%}
\version "2.11.32"
\paper { ragged-right = ##t }
\relative c'' \new PianoStaff <<
\new Staff = rh {
\time 12/8
g16\mf a b
\change Staff = lh
d,, b g
}
\new Staff = lh {
\clef bass
s4.
}
>>
Attachments:
x-s-script-beam-collision.png 5.2 KB
Issue attributes:
Status: New
Owner:
Labels: Type-Defect Priority-Medium
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Strange cross-stave beam and slur behaviour with portato
Hi Trevor On 9/2/07, Trevor Bača <[EMAIL PROTECTED]> wrote: > > > I can't be certain, but I'd bet that this is related to Google #430: > > http://code.google.com/p/lilypond/issues/detail?id=430 > > If it's the same bug, then we're in luck because Han-Wen and Joe have > marked #430 fixed in the upcoming 2.11.32 build. That certainly looks like a similar issue. I should have mentioned however that it's only the portato script which produces this weirdness; I tested it with several other articulations, and none resulted in broken beams. Regards, Neil ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
