> Let's go for that, I will prepare a patch.
Patch available here: http://code.google.com/p/lilypond/issues/detail?id=1029
Frédéric
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Comment #5 on issue 1029 by frederic...@m4x.org: \thumb should behave like
other fingerings
http://code.google.com/p/lilypond/issues/detail?id=1029
Here is a patch to fix this issue.
Attachments:
0001-fixed-issue-1029-thumb-now-behaves-more-like-fingeri.patch 829
bytes
__
Comment #8 on issue 684 by jordi.na...@gmail.com: Enhancement:
MetronomeMark should support break-align-symbols
http://code.google.com/p/lilypond/issues/detail?id=684
Hi, I am willing to contribute €60 for this feature.
___
bug-lilypond mailing lis
Comment #23 on issue 1060 by Carl.D.Sorensen: Add Funk-style shape note
heads
http://code.google.com/p/lilypond/issues/detail?id=1060
New walker heads, with the correct orientation of do and with stems forced
down except for low flagged/beamed
notes.
Comments always appreciated!
Attachme
Comment #22 on issue 1060 by Carl.D.Sorensen: Add Funk-style shape note
heads
http://code.google.com/p/lilypond/issues/detail?id=1060
D'oh! I looked at that *so* many times, and somehow I overlooked that.
The way LilyPond works right now, I don't see an easy way to automatically
duplicate
Comment #14 on issue 1031 by pnorcks: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
After checking the regtests, my suggested change from comment 13 creates
other
unwanted regressions.
I'm very close to figuring th
Comment #13 on issue 1031 by pnorcks: constantly-changing
input/regression/rest-collision-beam-note.ly
http://code.google.com/p/lilypond/issues/detail?id=1031
New info:
If I remove these two lines from rest-collision.cc, the bug seems to go
away.
67 if (scm_is_number (offset))
68
Is it not the same issue as this one?
http://article.gmane.org/gmane.comp.gnu.lilypond.bugs/18619
This bug has been poisoning my life since January -- I have had
different fixes in my repo, but hopefully that last patch is the Real
Fix. We have to wait for Joe to approve it.
Nicolas, can you
Comment #21 on issue 1060 by tolaythisbodydown: Add Funk-style shape note
heads
http://code.google.com/p/lilypond/issues/detail?id=1060
You're right, the 'do' head does invert. But you've got them upside down.
The stem
should be attached to the base of the figure, to the wider line.
Confu
Comment #12 on issue 989 by kie...@alumni.rice.edu: ensure that no
information is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Can I help with this issue?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lis
Comment #11 on issue 989 by kie...@alumni.rice.edu: ensure that no
information is only in the regtests
http://code.google.com/p/lilypond/issues/detail?id=989
Can I do this one?
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.or
Comment #7 on issue 684 by x.scheuer: Enhancement: MetronomeMark should
support break-align-symbols
http://code.google.com/p/lilypond/issues/detail?id=684
You can add 50€ from me if \tempo correctly align on time signature
and handles multi-measure rests correctly.
This is actually my person
Comment #4 on issue 1026 by percival.music.ca: Documentation: adapting
Lyrics when using \repeatTie
http://code.google.com/p/lilypond/issues/detail?id=1026
I don't think it has anything to do with \partials, but yes, this just
needs a
@knownissue somewhere.
Dump it in Vocals. I don't car
On Sat, Jun 05, 2010 at 06:32:55PM +0200, James Bailey wrote:
>
> On 05.06.2010, at 11:48, Graham Percival wrote:
>
>> I've updated CG 7 Issues:
>> http://kainhofer.com/~lilypond/Documentation/contributor/issues.html
>
> Maybe it's simply how I process information, but I think of the list at
> 7.1
Comment #6 on issue 684 by kie...@alumni.rice.edu: Enhancement:
MetronomeMark should support break-align-symbols
http://code.google.com/p/lilypond/issues/detail?id=684
I personally offer CDN$150 for a full and correct implementation of
break-align-symbols on MetronomeMark. I will double that
Comment #5 on issue 684 by percival.music.ca: Enhancement: MetronomeMark
should support break-align-symbols
http://code.google.com/p/lilypond/issues/detail?id=684
argh, I forgot to mention -- I have a vague recollection of telling
somebody that if
people just said "I'd pay for this" without
On 6/5/10 10:32 AM, "James Bailey" wrote:
>
> Maybe it's simply how I process information, but I think of the list
> at 7.1 as:
> Is #1 true? Yes, proceed. No? Go to #2
> Is #2 true? Yes, proceed. No? Go to #3S
>
> Given that order of operations, I think it would make more sense for
> the order
Updates:
Status: Verified
Comment #8 on issue 1103 by jameseli...@googlemail.com: Typo in engraver
name while defining new contexts causes lilypond to segfault
http://code.google.com/p/lilypond/issues/detail?id=1103
(No comment was entered for this change.)
_
Comment #4 on issue 684 by percival.music.ca: Enhancement: MetronomeMark
should support break-align-symbols
http://code.google.com/p/lilypond/issues/detail?id=684
How much, in total, are you three willing to sponsor? (at least a ballpark
figure
would be helpful)
Updates:
Labels: Bounty
Comment #3 on issue 684 by kie...@alumni.rice.edu: Enhancement:
MetronomeMark should support break-align-symbols
http://code.google.com/p/lilypond/issues/detail?id=684
This is a high priority item for me and at least two other people.
On 05.06.2010, at 11:48, Graham Percival wrote:
Hi Bug Squad and others,
I've updated CG 7 Issues:
http://kainhofer.com/~lilypond/Documentation/contributor/issues.html
Note that this URL goes to kainhofer; the official online docs
won't be updated until 2.13.24, and it's too early for that.
Hi Joe!
We have had a discussion on the LilyPond French Users mailing lists
about the new vertical spacing system.[1]
Thanks again for this powerful system.
Jean-François was using
\override VerticalAxisGroup #'next-staff-spacing
in the last Staff of a "group" to define a bigger space between,
Le 5 juin 2010 à 15:42, Xavier Scheuer a écrit :
> 2010/6/5 Nicolas Sceaux :
>
>> Hi,
>>
>> Page spacing algorithm seems to over estimate the height of markup
>> lines.
>
> With "ly:minimal-breaking" only?
No. Height estimation is orthogonal of the chosen page breaking algorithm.
But with ly
On 6/5/10 7:17 AM, "Graham Percival" wrote:
>
> The Enhancement bit says "if in doubt, make it an enhancement".
> Beyond that, I'm not certain how to clarify these points, either in
> our "understood" policy or written policy.
OK. I'm happy with that.
Thanks,
Carl
_
2010/6/5 Nicolas Sceaux :
> Hi,
>
> Page spacing algorithm seems to over estimate the height of markup
> lines.
>
> Example:
>
> ===
> \version "2.13.23"
> \header { tagline = ##f }
> \paper {
> annotate-spacing = ##t
> #(define page-breaking ly:minimal-breaking)
> }
> #(set-default-pape
Hi,
Page spacing algorithm seems to over estimate the height of markup lines.
Example:
===
\version "2.13.23"
\header { tagline = ##f }
\paper {
annotate-spacing = ##t
#(define page-breaking ly:minimal-breaking)
}
#(set-default-paper-size "a6" 'portrait)
#(define-markup-list-command
On Sat, Jun 5, 2010 at 1:24 PM, Carl Sorensen wrote:
>
> Section 7.1: "behaviour" --> "behavior"; U.S. spelling
Oops, yeah. Ok, I've "fixed" this. (I've been trying to get in
practice writing British, since my thesis has to be written in
British, instead of the customary Canadian wherein we c
Section 7.1: "behaviour" --> "behavior"; U.S. spelling
Section 7.2: Type -- IMO, Defect is when LilyPond doesn't do what it says it
does. Enhancement is when you want LilyPond to do something new. But if you
don't want to change the statements in the docs, that's fine with me.
Looks great!
T
Status: Accepted
Owner:
Labels: Type-Defect Priority-Medium
New issue 1110 by nicolas.sceaux: Wrong octave of repetition chord with
\relative and #{ #} syntax
http://code.google.com/p/lilypond/issues/detail?id=1110
When calling a music function, which uses #{ #} syntax, on a relative mus
Hi Bug Squad and others,
I've updated CG 7 Issues:
http://kainhofer.com/~lilypond/Documentation/contributor/issues.html
Note that this URL goes to kainhofer; the official online docs
won't be updated until 2.13.24, and it's too early for that.
I generally discourage links to kainhofer, since it'
30 matches
Mail list logo
