Graham Percival skrev:
is actually a serious error. Problem is masked by the fact that
default beam
(horizontal) does not look bad in this case.
Does this apply to all "program errors" ? I remember you telling me
that we had so many progerrors that it wasn't worth reporting them
unless the
Issue 334: setting staff size not longer safe
http://code.google.com/p/lilypond/issues/detail?id=334
Comment #2 by gpermus:
Really?! To clarify, I'm talking about lilypond raising an error with
-dsafe
It's a nitpick (err, sorry, should have been Priority-Low), but in a previous
version
it _was
Issue 302: bad shape for tied notes in different clefs
http://code.google.com/p/lilypond/issues/detail?id=302
Comment #1 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Type-Defect Type-Enhancement
--
You received this message because you are lis
Issue 336: octavation, change clef produces incorrect note positions
http://code.google.com/p/lilypond/issues/detail?id=336
Comment #2 by hanwenn:
clef and octavation operate on middleCPosition, which determines the vertical
offset
for a pitch. If you want to comibine both, set middleCPosition ex
Issue 334: setting staff size not longer safe
http://code.google.com/p/lilypond/issues/detail?id=334
Comment #1 by hanwenn:
works for me
Issue attribute updates:
Status: Invalid
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you
[EMAIL PROTECTED] wrote:
Comment #1 by hanwenn:
is actually a serious error. Problem is masked by the fact that default beam
(horizontal) does not look bad in this case.
Does this apply to all "program errors" ? I remember you telling me
that we had so many progerrors that it wasn't worth re
Issue 323: right-oriented fingering fails to be oriented with slur
http://code.google.com/p/lilypond/issues/detail?id=323
Comment #2 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_33 fixed_2_10_33
--
You received
Issue 329: lyrics messed up when assigned to voices with different rhythms
http://code.google.com/p/lilypond/issues/detail?id=329
Comment #2 by hanwenn:
hi,
the problem is that \lyricsto will try to connect the "sop" melody with the
context
created by "\new Lyrics".
Then \lyrics in \words crea
Issue 153: \once \set fails with MIDI instruments
http://code.google.com/p/lilypond/issues/detail?id=153
Comment #3 by hanwenn:
unfortunately, there is no place to store the pre-\once value, so it can be
restored
easily.
Chanign to enhancement, since this hasn't ever worked; perhaps it needs
cl
Issue 454: beamlets have different length
http://code.google.com/p/lilypond/issues/detail?id=454
Comment #2 by hanwenn:
See also #423
--
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 notifi
Issue 438: subdivideBeams sometimes fails
http://code.google.com/p/lilypond/issues/detail?id=438
Comment #1 by hanwenn:
dup: see Issue 11.
Issue attribute updates:
Status: Duplicate
--
You received this message because you are listed in the owner
or CC fields of this issue, or because
Hi
I am trying to find a tweak for this :
{
< fis''' f'''!>4
}
How can i avoid the collision between the accidentals. Is it possible,
without using the g flat ?
Thanx for any suggestions
Karim
___
bug-lilypond mailing list
bug-lilypond@gnu.org
ht
Issue 444: false progerror with beaming and rest
http://code.google.com/p/lilypond/issues/detail?id=444
Comment #1 by hanwenn:
is actually a serious error. Problem is masked by the fact that default beam
(horizontal) does not look bad in this case.
Issue attribute updates:
Labels: -Prio
Issue 458: handling ties from different voices
http://code.google.com/p/lilypond/issues/detail?id=458
Comment #1 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Type-Defect Type-Enhancement
--
You received this message because you are listed in t
Issue 454: beamlets have different length
http://code.google.com/p/lilypond/issues/detail?id=454
Comment #1 by hanwenn:
There are some limits to the beamlet lengths, to ensure that they are kept
separate,
if we have two of them pointing inwards. This capping should only happen if
there
are in
Issue 456: \laissezVibrer in chords
http://code.google.com/p/lilypond/issues/detail?id=456
Comment #1 by hanwenn:
Hi werner,
can you reserve Defect for something that the documentation and examples imply
to work?
thanks,
Issue attribute updates:
Labels: -Type-Defect Type-Enhancement
Issue 457: general problem with \override and \once \override
http://code.google.com/p/lilypond/issues/detail?id=457
Comment #4 by hanwenn:
No, werner's right. This is a defect, and is caused by an insidious
optimization.
It works already if you have an \override for a another property following
Issue 459: Misaligned TrillSpanner across a line break
http://code.google.com/p/lilypond/issues/detail?id=459
Comment #2 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -fixed_2_10 fixed_2_10_33
--
You received this message because you are listed
Issue 459: Misaligned TrillSpanner across a line break
http://code.google.com/p/lilypond/issues/detail?id=459
Comment #1 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Status: Fixed
Labels: fixed_2_11_33 fixed_2_10
--
You received this message be
Hi there,
In the following snippet, beginning a sequence of music with a grace note
produces the above error at compile time when the \midi block is included,
though the midi output seems to be fine:
\version "2.11.32"
\score {
\new Staff {
\grace c'8
c'1
}
\midi {}
}
Issue 460: bar numbers for broken bars
http://code.google.com/p/lilypond/issues/detail?id=460
Comment #1 by hanwenn:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Type-Defect Type-Enhancement
--
You received this message because you are listed in the owner
Issue 461: enharmonic ties
http://code.google.com/p/lilypond/issues/detail?id=461
Comment #1 by hanwenn:
this is on purpose. The formatting would be completely different, due to
non-horizontalness.
Use a slur to fake this.
Issue attribute updates:
Labels: -Type-Defect Type-Enhancement
Issue 462: horizontal space of invisible bar
http://code.google.com/p/lilypond/issues/detail?id=462
Comment #1 by hanwenn:
this is hard; the invisible bar inserts a time step into the problem, which
influences the spacing problem. Joe?
Issue attribute updates:
Cc: joeneeman
Label
Issue 465: Spacing collisision
http://code.google.com/p/lilypond/issues/detail?id=465
New issue report by hanwenn:
in 2.11.31
input/regression/trill-spanner-pitched.ly
will put the parenthesis on top of the note.
Issue attributes:
Status: Accepted
Owner: hanwenn
CC: j
Issue 464: \mark text pushes multi-measure rest
http://code.google.com/p/lilypond/issues/detail?id=464
New issue report by gpermus:
%{
if the R1 is replaced by notes, the "foo foo foo" is printed over the
notes; when there is a R1, the "foo foo foo" pushes the rest to the right
%}
\version "2.11
%% Whole measure rests are not centered when there is a long text mark.
%%
\version "2.11.32"
\paper{ ragged-right=##t }
\context StaffGroup
<<
\new Staff \relative g' {
\override Score.RehearsalMark #'self-alignment-X = #LEFT
\override Score.RehearsalMark #'break-align-symbols = #'(time
Issue 445: minimum-Y-extent missing for staffs
http://code.google.com/p/lilypond/issues/detail?id=445
Comment #1 by [EMAIL PROTECTED]:
The setting I had in mind was, of course,
\override VerticalAxisGroup #'minimum-Y-extent = #'(-4 . 4)
and nothing else.
--
You received this message because
27 matches
Mail list logo
