Updates:
Status: Duplicate
Labels: -Patch-needs_work
Mergedinto: 2240
Blockedon: -2239
Comment #37 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Merging thi
Comment #36 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
lilyp...@googlecode.com writes:
Hm. I deleted many comments now. If it is a total number problem, this
might help. If it is a
Updates:
Labels: -Patch-new Patch-needs_work
Blockedon: 2239
Comment #35 on issue 2070 by gra...@percival-music.ca: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
oh, it's probably that problem where goog
Comment #34 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
I don't think NR should be affected. The extending/programming reference
will likely need a few touchups, but not all that much
Comment #33 on issue 2070 by pkx1...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
David,
Do we need any ew @warnings added anywhere in the NR that you can think of
off the top of your head - in case this
Updates:
Blockedon: -2229
Comment #32 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
If you are not working with song/festival or the XML output, this is pretty
much the final can
Updates:
Labels: Patch-new
Comment #31 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c31
Don't wrap EventChord around rhythmic events by default.
This changes quite a number of th
Comment #30 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Not when tested on the current brand-new master (unless I made a mistake
when uploading). It _would_ lose it without
commit e
Updates:
Labels: Patch-needs_work
Comment #29 on issue 2070 by lilypond...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c29
Patchy the autobot says: this loses the second word FAT in
text-spanner-a
Updates:
Labels: Patch-new
Comment #28 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c28
Don't wrap EventChord around rhythmic events by default.
This changes quite a number of th
lilyp...@googlecode.com writes:
> Updates:
> Labels: Patch-needs_work
>
> Comment #25 on issue 2070 by lilypond...@gmail.com: Patch: Don't wrap
> EventChord around rhythmic events by default.
> http://code.google.com/p/lilypond/issues/detail?id=2070#c25
>
> Patchy the autobot says: based on
Comment #27 on issue 2070 by gra...@percival-music.ca: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
staging is vaguely in limbo: I've disabled the crontab on my desktop since
I want to control when it gets bogged dow
Comment #26 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
The last upload is based on current master, the current work is based on
staging. Since staging has not been bounced to master
Updates:
Labels: Patch-needs_work
Comment #25 on issue 2070 by lilypond...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c25
Patchy the autobot says: based on current master, this removes the pitched
Updates:
Labels: Patch-new
Comment #24 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c24
Don't wrap EventChord around rhythmic events by default.
This changes quite a number of th
Updates:
Blockedon: 2229
Comment #23 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
I think I have got the articulation business tackled in issue 2229.
___
Comment #22 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
@mike: of course I'll get the terminology wrong: my amount of knowledge is
just sufficient for buzzword juggling. Second option
Comment #21 on issue 2070 by m...@apollinemike.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Just a pedantic terminological thing: there isn't an EventChord engraver,
just an EventChord iterator. Iterators do di
Comment #20 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
The last patch marks everything that can be an "articulation", namely an
event attached to a single note inside of a chord, in a
Comment #19 on issue 2070 by carl.d.s...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
OK, I'm trying to understand the implications of things and respond to
comments 16 and 17. I'm not sure I'm clear abou
Updates:
Labels: -Patch-review Patch-needs_work
Comment #18 on issue 2070 by colinpkc...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Marking as "needs work" to re3flect David's comment @17.
__
Comment #17 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Copying comment from the patch issue:
Ok, I need some pointers here. In order to make this work compatibly at the
lowest level, a
Comment #16 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Again, concerning comment #14 and compatibility. I have tried looking in
the engravers concerning how to make things behave as
Comment #15 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Well, for things like fingerings, I don't think the difference can easily
go away: inside of a chord, fingerings will need to ge
Comment #14 on issue 2070 by carl.d.s...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
A patch for issue 2085 has been posted. It now looks to see if the
StringNumber stencil is #f, and if it is, it avoids
Comment #13 on issue 2070 by carl.d.s...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
I will take a look at the tablature stuff when I get done grading finals
(probably about a week out). I think the prop
Comment #12 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
That's ok. I will likely edge a few changes into master at the meantime
that make the transition smoother: while the default of
Comment #11 on issue 2070 by colinpkc...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
@David: responding to your comment above, I'll keep this off the countdown
schedule until I hear from you that you've h
Comment #10 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
The appearance in tablature-harmonic-functions.ly is simply wrong (all of
them are too high even before the change) because ther
Updates:
Labels: Patch-review
Comment #9 on issue 2070 by lilypond...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c9
Patchy the autobot says: LGTM. I can accept this, but the 8va in
tablature-har
Updates:
Labels: Patch-new
Comment #8 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c8
Don't wrap EventChord around rhythmic events by default.
This changes quite a number of thin
Updates:
Labels: Patch-needs_work
Comment #7 on issue 2070 by lilypond...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c7
Patchy the autobot says: balloon.log: not an articulation 8
___
Updates:
Labels: Patch-new
Comment #6 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c6
Don't wrap EventChord around rhythmic events by default.
This changes quite a number of thin
Comment #5 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Issue 2037 has been merged into this issue.
___
bug-lilypond mailing list
bug-lilypon
Comment #4 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Actually, as I move the patch to behave more like Lilypond works by default
(only keeping articulations in "articulations" inside
Updates:
Labels: Patch-needs_work
Comment #3 on issue 2070 by lilypond...@gmail.com: Patch: Don't wrap
EventChord around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c3
Patchy the autobot says: I'm sure that David already knows this, but the
pa
Updates:
Labels: Patch-new
Comment #2 on issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord
around rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070#c2
Don't wrap EventChord around rhythmic events by default.
This changes quite a number of thin
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord around
rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Don't wrap EventChord around rhythmic events by default.
This changes quite a num
38 matches
Mail list logo
