On Fri 28 May 2010, 23:20 Xavier Scheuer wrote:
Hi!
Hi!
I'm experiencing a very annoying (IMO) output with multiline
\header fields.
Thank you, added as 1136:
http://code.google.com/p/lilypond/issues/detail?id=1136
I don't know if it's a bug or if I'm doing something wrong (actually I
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1136 by brownian.box: Multiline \header fields: wrong
baselineskip between and/or inside header fields
http://code.google.com/p/lilypond/issues/detail?id=1136
Reported by Xavier Scheuer:
Updates:
Status: Verified
Comment #23 on issue 617 by brownian.box: X-offset works in a specific way
for RehearsalMarks
http://code.google.com/p/lilypond/issues/detail?id=617
(No comment was entered for this change.)
___
bug-lilypond
Updates:
Status: Verified
Comment #4 on issue 801 by brownian.box: Accidentals in a chord may collide
with augmentation dots
http://code.google.com/p/lilypond/issues/detail?id=801
(No comment was entered for this change.)
___
bug-lilypond
Updates:
Status: Verified
Comment #7 on issue 819 by brownian.box: TabVoice confused with ChordNames
spacing when using an override.
http://code.google.com/p/lilypond/issues/detail?id=819
(No comment was entered for this change.)
___
Updates:
Status: Verified
Comment #18 on issue 884 by brownian.box: pageBreak resets page-count
property
http://code.google.com/p/lilypond/issues/detail?id=884
(No comment was entered for this change.)
___
bug-lilypond mailing list
Updates:
Status: Verified
Comment #4 on issue 886 by brownian.box: ChordNames horizontal extent may
affect note spacing
http://code.google.com/p/lilypond/issues/detail?id=886
(No comment was entered for this change.)
___
bug-lilypond
Updates:
Status: Verified
Comment #4 on issue 1088 by brownian.box: Accidentals for single notes may
collide with augmentation dots
http://code.google.com/p/lilypond/issues/detail?id=1088
(No comment was entered for this change.)
___
Updates:
Status: Verified
Comment #3 on issue 1120 by brownian.box: Melismata disturb note head
distances
http://code.google.com/p/lilypond/issues/detail?id=1120
(No comment was entered for this change.)
___
bug-lilypond mailing list
Updates:
Status: Verified
Comment #4 on issue 1130 by brownian.box: Stave spacing not consistent
http://code.google.com/p/lilypond/issues/detail?id=1130
(No comment was entered for this change.)
___
bug-lilypond mailing list
Status: Accepted
Owner:
Labels: Type-Defect Priority-High
New issue 1137 by brownian.box: \bassFigureExtendersOn regression
http://code.google.com/p/lilypond/issues/detail?id=1137
http://lilypond.org/test/v2.13.25-1/compare-v2.13.24-1/v2.13.25-1/figured-bass-extenders-markup.ly
I'm not
Status: Accepted
Owner:
Labels: Type-Defect Priority-High
New issue 1138 by brownian.box: (minor) regression: Adding a Bar_engraver
to the Lyrics context DOES NOT make sure that lyrics do not collide with
barlines
http://code.google.com/p/lilypond/issues/detail?id=1138
Updates:
Labels: Patch
Comment #3 on issue 1116 by neziap: Title not centered
http://code.google.com/p/lilypond/issues/detail?id=1116
http://lists.gnu.org/archive/html/lilypond-devel/2010-06/msg00235.html
___
bug-lilypond mailing list
sorry being a Bug Squad member i can not decide is this a bug .)
Hi!
Excuse me, snippet is rather long --- whie i strip it to three notes and three
syllables, everyting is ok, i dont know for which reason. So, i've taken a
piece of real score and stripped/simplyfied it.
So, there are three
Status: Accepted
Owner:
Labels: Type-Collision Priority-Medium
New issue 1139 by brownian.box: 'inter-loose-line-spacing #'stretchability
leads to collision under some conditions
http://code.google.com/p/lilypond/issues/detail?id=1139
Sorry, snippet rather long; there is no collision if
On Mon 21 Jun 2010, 13:52 I wrote:
sorry being a Bug Squad member i can not decide is this a bug .)
Sorry, rather strange question.
Can't believe this can be intended behavior, so added this as 1139:
http://code.google.com/p/lilypond/issues/detail?id=1139
--
Dmytro O. Redchuk
Bug Squad
Reinhold Kainhofer reinh...@kainhofer.com wrote in message
news:201006202256.43475.reinh...@kainhofer.com...
Am Sonntag, 20. Juni 2010, um 22:53:06 schrieb Phil Holmes:
Well - the oddity that I identified was that a bug had been reported,
and
that 2.12 behaved differently from 2.13.
In what
Sorry, I'm somewhat lost with Google.
Please ignore ;-)
(I'll have time till Friday, at least ...)
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Dmytro O. Redchuk brownian@gmail.com wrote in message
news:1269355703.19166.179.ca...@dor...
У вт, 2010-03-23 у 08:25 -0600, Carl Sorensen пише:
The clue here is that there is some kind of break in the middle of the
score
that you've put in manually that confuses the layout engine.
My
Andrew Hawryluk ahawry...@gmail.com wrote in message
news:l2u11cc7c4f1004011001j1c7da228y36981a5024a1a...@mail.gmail.com...
This looks like a bug to me. My minimal example:
\version 2.13.16
{
\set Staff.pedalSustainStyle = #'text
c''1\sustainOn
}
If the pedalSustainStyle is set to #'mixed or
On Mon 21 Jun 2010, 15:29 Phil Holmes wrote:
Just remove the /pageBreak in the middle of your score and it works
perfectly.
Yes, almost .)
(I can use both system-count and page-count, replace \pageBreak with
\break, then adjust spacing to force three-systems-per-page desired
layout, with
On Mon 21 Jun 2010, 17:44 I wrote:
So I'm going to break Graham's Bug Squad rule again here, and ask a
Thank you .)
question. As far as I can see, this shows a critical bug. It may
be complex as a bit of Lilypond, but surely something that compiles
and displays perfectly under 2.12
Status: Accepted
Owner:
Labels: Type-Documentation Priority-Low
New issue 1140 by PhilEHolmes: StringNumber documentation
http://code.google.com/p/lilypond/issues/detail?id=1140
There have been requests for improved documentation of the StringNumber
element.
-Eluze elu...@gmail.com wrote in message
news:28325812.p...@talk.nabble.com...
the code
\version 2.13.18
\layout {
\context {
\Staff
\override StringNumber #'stencil = ##f
} }
{ a\6-18 }
produces the error: cannot align on self: empty element
however, the pdf is produced correctly.
adding
Comment #1 on issue 1140 by Carl.D.Sorensen: StringNumber documentation
http://code.google.com/p/lilypond/issues/detail?id=1140
The patch doesn't remove the string number engraver; it simply sets the
string numbers not to print.
___
Updates:
Status: Invalid
Comment #1 on issue 1138 by joeneeman: (minor) regression: Adding a
Bar_engraver to the Lyrics context DOES NOT make sure that lyrics do not
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=1138
Actually, the output from 2.13.25 is
Am Montag, 21. Juni 2010, um 16:09:57 schrieb Phil Holmes:
Well, it started by you saying:
Is this a bug? In my eyes, it is quite severe, because it means you can't
trust lilypond any more. If you check e.g. the individual parts (which do
not
add the RemoveEmptyStaffContext) for errors,
Updates:
Status: Invalid
Comment #2 on issue 1140 by percival.music.ca: StringNumber documentation
http://code.google.com/p/lilypond/issues/detail?id=1140
Carl: err, patch? Do you mean override ?
With regards to the initial report, I'm not clear what the problem is. If
there'a good
Hi all,
There appear to be at least two collisions in this small snippet that are
unsightly: the first flat and the preceding rest, and the second flat and the
preceding ledger line.
Regression?
Thanks,
Kieren.
\version 2.13.25
\include english.ly
thenotesI =
On 21.06.2010, at 21:55, Kieren MacMillan wrote:
Hi all,
There appear to be at least two collisions in this small snippet
that are unsightly: the first flat and the preceding rest, and the
second flat and the preceding ledger line.
Regression?
Thanks,
Kieren.
On 21.06.2010, at 21:55, Kieren MacMillan wrote:
Hi all,
There appear to be at least two collisions in this small snippet
that are unsightly: the first flat and the preceding rest, and the
second flat and the preceding ledger line.
Regression?
Thanks,
Kieren.
Updates:
Status: Verified
Comment #2 on issue 1138 by jameseli...@googlemail.com: (minor) regression:
Adding a Bar_engraver to the Lyrics context DOES NOT make sure that lyrics
do not collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=1138
(No comment was
32 matches
Mail list logo
