On 2 February 2011 15:36, Reinhold Kainhofer wrote:
> That's indeed a bug, and a nasty one in particular. I don't know of any
> straightforward way to fix it.
> Currently, I change the staff's middle C position (like \clef does) to get the
> cue notes show up in their correct position. Unfortunat
2011/1/19 Janek WarchoĊ :
> % the following scheme-made custom extender line from snippet 643
> % prints the additional character not only at the ent of the extender line,
> % but also when the extender line is interrupted by line break.
> % i suppose it should be printed only once.
Fixed in LSR.
> It wasn't the wrong conclusion; there is definitely a problem with
> version 2.12.3. But unfortunately we are not maintaining that
> one; please wait for 2.14 to be ready (hopefully in 3-4 weeks).
I see.
I wait to 2.14 come out in hope.
Good luck in 2.14!
Regards,
Funaji
On Wed, Feb 02, 2011 at 08:00:43PM +, Shotaro Funaji wrote:
> > That's also Graham's opinion since he states this report on the tracker as
> invalid:
> > http://code.google.com/p/lilypond/issues/detail?id=1498
>
> I was overlooking notice of guidelines.
> And I have just understood the meanin
> That's also Graham's opinion since he states this report on the tracker as
invalid:
> http://code.google.com/p/lilypond/issues/detail?id=1498
I have added the tracker by mistake.
I was overlooking notice of guidelines.
And I have just understood the meaning of comment from Mr.Graham.
I am so so
On 2 February 2011 16:19, James Lowe wrote:
>
> Im using 2.13.45.
>
> Looks ok to me unless I am missing something.
>
> See attached.
That's also Graham's opinion since he states this report on the tracker
as invalid:
http://code.google.com/p/lilypond/issues/detail?id=1498
Cheers,
Xavier
--
Xa
Am Mittwoch, 2. Februar 2011, um 18:13:31 schrieb Trevor Daniels:
> David Kastrup wrote Wednesday, February 02, 2011 9:47 AM
>
> > test-baseline does not run through completion, so I can't actually
> > do a
> > regression test. Apparently fails somewhere in
> > out-test/71e-TabStaves.ly.
>
> I s
I confirm that those accidentals are laid properly on version 2.13.47.
Sorry for the trouble.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
-Original Message-
From: bug-lilypond-bounces+james.lowe=datacore@gnu.org
[mailto:bug-lilypond-bounces+james.lowe=datacore@gnu.org] On Behalf Of
Shotaro Funaji
Sent: 02 February 2011 13:17
To: bug-lilypond@gnu.org
Subject: Some accidentals are not printed properly.
% Accidentals
Reinhold Kainhofer wrote Wednesday, February 02, 2011 5:44 PM
Nope, the problem is that this file now spits out a warning,
which causes the regtests to fail. In particular, with the
given tuning the frets of
\key c \major b8 \3 8 \5 \6 \6 \5 \5
in PartPFourVoiceOne on string 5 seem to be ne
% Accidentals crash into notes.
% These spaces are the same as when without accidentals.
% They are too narrow.
\version "2.12.3"
{
\set Staff.extraNatural = ##f
<<
{ r8 r16 geses''
r8 r16 ges''
r8 r16 gisis''
r8 r16
Updates:
Labels: -Patch-review Patch-needs_work
Comment #14 on issue 37 by percival.music.ca: collision notehead and beams
http://code.google.com/p/lilypond/issues/detail?id=37
Han-Wen has some concerns about this patch, and is working on an alternate
approach.
_
Comment #2 on issue 1495 by d...@gnu.org: mac line endings and line comment
disaster
http://code.google.com/p/lilypond/issues/detail?id=1495
I'll fix this.
Since it involves meddling with the parser, it'll take a few hours for a
complete regtest.
David Kastrup wrote Wednesday, February 02, 2011 9:47 AM
test-baseline does not run through completion, so I can't actually
do a
regression test. Apparently fails somewhere in
out-test/71e-TabStaves.ly.
I saw this myself recently. It arises because the
conversion from the xml files to ly h
lilyp...@googlecode.com writes:
> Updates:
> Labels: Type-Defect Priority-High
>
> Comment #1 on issue 1495 by percival.music.ca: mac line endings and
> line comment disaster
> http://code.google.com/p/lilypond/issues/detail?id=1495
>
> (No comment was entered for this change.)
test-baselin
Comment #3 on issue 1495 by d...@gnu.org: mac line endings and line comment
disaster
http://code.google.com/p/lilypond/issues/detail?id=1495
Since test-baseline fails on the current Lilypond source, I can't make a
regression test.
I attach the git patch to this report. Anybody can apply
Am Dienstag, 1. Februar 2011, um 23:38:10 schrieb Steven Weber:
> Found this while playing with the new functionality. If you start a piece
> with cued notes or have cues that run across a line break, the key
> signature is printed as if it was in the cued clef instead of the non-cued
> clef.
Tha
lilyp...@googlecode.com writes:
> Updates:
> Labels: Type-Defect Priority-High
>
> Comment #1 on issue 1495 by percival.music.ca: mac line endings and
> line comment disaster
> http://code.google.com/p/lilypond/issues/detail?id=1495
>
> (No comment was entered for this change.)
I'll fix tha
Am Mittwoch, 2. Februar 2011, um 05:31:23 schrieb Jay Anderson:
> On Tue, Feb 1, 2011 at 1:46 PM, Keith OHara wrote:
> > ... on both WinXP and Linux and could not find a segfault.
>
> It happens consistently for me (linux 2.6.35, x86_64).
Ah, I'm on 32-bit linux...
> Since it's such
> a diffic
19 matches
Mail list logo
