Updates:
Status: Fixed
Labels: -Patch-countdown Patch-push Fixed_2_15_35
Comment #21 on issue 2272 by mts...@gmail.com: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
(No comment was entered for this change
Comment #20 on issue 2272 by mts...@gmail.com: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
Pushed as 469c53f8ce7c9e6a4e120be130bef0aaac271422.
Sorry for the early push, but I have several out-of-town gigs over the next
few days and
Comment #18 on issue 2272 by k-ohara5...@oco.net: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
a way to make the failure mode of this regtest become obvious
I'll make 'accidental-broken-tie-spacing' test set an accid
Updates:
Labels: Patch-review
Comment #17 on issue 2272 by d...@gnu.org: Long monosyllabic words collide
with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272#c17
Patchy the autobot says: LGTM.
___
bug-lilypond mailing
Comment #16 on issue 2272 by mts...@gmail.com: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
It'd be great if there were a sort of collision-assertion feature. That
is, for any two grobs, be able to:
a) Connect them somehow;
Comment #15 on issue 2272 by d...@gnu.org: Long monosyllabic words collide
with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
Regarding comment #13: well, there must be _some_ advantage in having the
regtests being run by overqualified personnel.
Can you think of a way
Updates:
Labels: Patch-new
Comment #14 on issue 2272 by mts...@gmail.com: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272#c14
Axis group interface ignores column rank for pure-from-neighbor-interface
http://codereview.appspot.com
Comment #12 on issue 2272 by k-ohara5...@oco.net: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
Interesting spacing changes in accidental-broken-tie-spacing
This was worth mentioning, because in fact the current patch defeats the
Updates:
Labels: Patch-review
Comment #10 on issue 2272 by d...@gnu.org: Long monosyllabic words collide
with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272#c10
Patchy the autobot says: LGTM. Interesting spacing changes in
accidental-broken-tie-spacing and
Updates:
Labels: Patch-new
Comment #9 on issue 2272 by mts...@gmail.com: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272#c9
Axis group interface ignores column rank for pure-from-neighbor-interface
http://codereview.appspot.com
Updates:
Labels: Patch-review
Comment #8 on issue 2272 by d...@gnu.org: Long monosyllabic words collide
with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272#c8
Patchy the autobot says: LGTM. There is a somewhat surprising increase
from 1539186 to 2500694 cells in
Comment #7 on issue 2272 by mts...@gmail.com: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272#c7
Axis group interface ignores column rank for pure-from-neighbor-interface
http://codereview.appspot.com/5843063
Comment #6 on issue 2272 by mts...@gmail.com: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
It was just a minor fix that was necessary - by definition, the pure
heights of all elements in the "neighbors" grob array facto
Updates:
Labels: Patch-new
Comment #5 on issue 2272 by mts...@gmail.com: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272#c5
Axis group interface ignores column rank for pure-from-neighbor-interface
http://codereview.appspot.com
Comment #4 on issue 2272 by k-ohara5...@oco.net: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
"Go back to the old machinery"? I recommend you look at that commit.
The span-bar.cc had only minor changes. In define-grobs.s
Comment #3 on issue 2272 by d...@gnu.org: Long monosyllabic words collide
with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
"Go back to the old machinery"? I recommend you look at that commit.
input/regression/span-bar-allow-span-bar.ly | 59 +++
li
Updates:
Labels: -Type-Ugly Type-Critical Regression
Comment #2 on issue 2272 by k-ohara5...@oco.net: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
\version "2.15.33"
\new StaffGroup <<
\new Staff { R1 e'
Updates:
Status: Accepted
Comment #1 on issue 2272 by philehol...@gmail.com: Long monosyllabic words
collide with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
(No comment was entered for this change.)
___
bug-lilypond
Hi Patrick,
On Thu, Feb 02, 2012 at 12:47:05PM +0100, pls wrote:
> I guess this is related to Issue 2061
> (http://code.google.com/p/lilypond/issues/detail?id=2061). Even though the
> status of Issue 2061 is set to fixed long monosyllabic words still collide
> with barlines in LilyPond v2.15.2
Status: New
Owner:
Labels: Type-Ugly
New issue 2272 by colingh...@gmail.com: Long monosyllabic words collide
with barlines
http://code.google.com/p/lilypond/issues/detail?id=2272
Reported by Patrick
http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/32939
This seems to be related
Hey all,
I guess this is related to Issue 2061
(http://code.google.com/p/lilypond/issues/detail?id=2061). Even though the
status of Issue 2061 is set to fixed long monosyllabic words still collide with
barlines in LilyPond v2.15.27. (Short) syllables don't collide:
\version "2.15.27"
global =
21 matches
Mail list logo
