lilyp...@googlecode.com writes:
> Comment #11 on issue 1043 by k-ohara5...@oco.net: Cross-staff beams
> confuse skyline calculations
> http://code.google.com/p/lilypond/issues/detail?id=1043
>
> Now I see that placement of outside-staff grobs uses a series of
> skyline calculations. Knowing that,
Comment #8 on issue 1173 by Carl.D.Sorensen: LilyPond crash when using
showFirstLength/showLastLength with \compressFullBarRests
http://code.google.com/p/lilypond/issues/detail?id=1173
So what is the status of this fix? At least part of the latest patch
appears to have been applied to orig
% Something like issue 506 can still be observed.
%
% Relative to the original report for issue 506,
% remove the slur, and add an accent with a
% forced direction. The beam is badly placed.
%
% I did *not* find this during normal use, but
% while testing a workaround for a different bug.
% Small
Comment #11 on issue 1043 by k-ohara5...@oco.net: Cross-staff beams confuse
skyline calculations
http://code.google.com/p/lilypond/issues/detail?id=1043
Now I see that placement of outside-staff grobs uses a series of skyline
calculations. Knowing that, the 'Summary:' makes sense. Sorry fo
Updates:
Labels: -Priority-Critical -Regression Priority-Medium
Comment #5 on issue 1263 by percival.music.ca: MetronomeMark can not be
aligned on note if MMR in another voice
http://code.google.com/p/lilypond/issues/detail?id=1263
Good reasoning, Carl. If it didn't work deliberately
Comment #4 on issue 1263 by Carl.D.Sorensen: MetronomeMark can not be
aligned on note if MMR in another voice
http://code.google.com/p/lilypond/issues/detail?id=1263
I think this should not be a critical regression.
Critical regressions are things that used to *deliberately* work. We used
this doesn't work
c4\3
It does! This avoids a string number indication in standard notation and
leads to a correct fret number in tablature. See Default tablatures in
the Notation Reference.
and this does:
4
This basically has the same effect but a string number indication
http://wasuyim.t35.com/
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
On Tue, 21 Sep 2010 19:49:45 +0200, Graham Percival
wrote:
IIRC there's properties like V-offset and H-offset, which *are*
taken into account by the spacing engine. Vicente: could you look
into this?
I can't find V-offset nor H-offset, you probably mean Y-offset and
X-offset.
indeed it s
Status: New
Owner:
Labels: Type-Enhancement Patch
New issue 1268 by neziap: [PATCH] span-bar problem
http://code.google.com/p/lilypond/issues/detail?id=1268
http://lists.gnu.org/archive/html/lilypond-devel/2010-09/msg00019.html
___
bug-lilypond
Updates:
Labels: Patch
Comment #4 on issue 1240 by neziap: Music overflows page: #'((space . N)
(stretchability . 0)) and nothing more with spacings
http://code.google.com/p/lilypond/issues/detail?id=1240
(No comment was entered for this change.)
Comment #4 on issue 1265 by ianhuli...@gmail.com: Avoid compilation and
run-time deprecation warnings from Guile V2
http://code.google.com/p/lilypond/issues/detail?id=1265
I've uploaded a new patch set uploaded with flower/include/compatibility.hh
gutted of its conditional compilation block
On Mon, Sep 20, 2010 at 04:03:26PM -0400, James Lowe wrote:
> Vicente,
>
> On 20/09/2010 19:30, Vicente Solsona wrote:
> > if you are getting an extra page just because the \f in the example (and
> > this happens often), using extra-offset won't decrease the vertical spacing
> > and you will keep
13 matches
Mail list logo
