On Sun Apr 25, 17:31 You wrote:
> g4 g8. g16 a4 g8. g16 g4 f8. e16 d2 (chorus from "Waltzing Matilda")
[...]
> That means the above music sequence can be written in "quick" style as:
> g4 3 g a g3 g g f3 e d2
:-)
This remembered me (i dont know why, sorry, no offence) Euro-Eng
On Sat Apr 24, 18:59 You wrote:
> Hi lilypond team!
>
> While typesetting a piece, I found this bug:
> An connected Arpeggio may collide with the previous note when having
> chords in multiple voices.
Hi!
Sorry, isn't it the same as
http://code.google.com/p/lilypond/issues/detail?id=931 ?
> I tr
On Sun, 25 Apr 2010 17:31:42 (UTC), Trevor Skeggs wrote:
Why should 3 not be a valid duration, mid-way between 2 and 4?
> (It would have the same value as a dotted 4).
>
> After all, if the program is going to the trouble of weeding-out
> these values and printing an
Updates:
Status: Accepted
Labels: Type-Enhancement Priority-Medium
Comment #1 on issue 1064 by percival.music.ca: Feature request:
binding-gutter
http://code.google.com/p/lilypond/issues/detail?id=1064
Please don't ignore the "don't add material directly to the tracker"
noti
Comment #23 on issue 943 by pnorcks: input/regression/slur-broken-trend.ly
broken
http://code.google.com/p/lilypond/issues/detail?id=943
And... the function call order for the "correct.png" case from comment 9
above:
Call order:
- calc_control_points (Slur1)
- set_next_direction (Slur1) -
Comment #22 on issue 943 by pnorcks: input/regression/slur-broken-trend.ly
broken
http://code.google.com/p/lilypond/issues/detail?id=943
Further information:
The function call order is different (as I suspected) with current git
compared to
that after applying Neil's patch (or reverting Jo
Status: New
Owner:
New issue 1064 by rbstoddard: Feature request: binding-gutter
http://code.google.com/p/lilypond/issues/detail?id=1064
Multi-page scores would benefit by having a "binding gutter" that adds an
additional amount of space on the left for odd-numbered pages and on the
right f
On 25 April 2010 18:31, Trevor Skeggs wrote:
> 1). If a note duration such as c3 is detected, an error message is issued:
>
> error: not a duration: 3
>
> Why should 3 not be a valid duration, mid-way between 2 and 4?
> (It would have the same value as a dotted 4).
I think you misunders
Trevor Skeggs wrote:
> Is it OK to post suggestions on this site? (I could not
> find any link for such in the Lilypond site, other than
> for documentation changes).
Questions like these are better suited for the developer
mailing list:
http://lilypond.org/doc/v2.13/Documentation/web/contact
An
Is it OK to post suggestions on this site?
(I could not find any link for such in the Lilypond site,
other than for documentation changes).
1). If a note duration such as c3 is detected, an error message is issued:
error: not a duration: 3
Why should 3 not be a valid duration, mid-wa
Is this a report of a problem in the docs, or a problem in
something you wrote yourself?
Any language includes must go after other builtin lilypond
includes. I can't find the string "Fretboard" in any of our
snippets, so I suspect the code below was written by you. If you
fix the order, it shoul
The Snippet List extract for a simple lead-sheet template
( melody, lyrics, chords and fret diagrams ) is not practical
because it produces only trivial 3-note fretboard diagrams
(the three lowest guitar strings are always marked as unused).
- - - - - - - - - - -
The Snippet included in Notat
Comment #32 on issue 602 by n.puttock: Feature request: better support for
Sacred Harp notation
http://code.google.com/p/lilypond/issues/detail?id=602
Hehe, it's perferctly innocent: I was looking at note-collision.cc a few
days ago for
Issue 39, and couldn't help noticing the comment befor
Comment #31 on issue 602 by Carl.D.Sorensen: Feature request: better
support for Sacred Harp notation
http://code.google.com/p/lilypond/issues/detail?id=602
Neil,
I've fixed and pushed that now, along with a change to the regression test
that demonstrates that it works
properly.
BTW, how
Comment #9 on issue 1027 by percival.music.ca: LSR: minimum-Y-extent
snippets need to be updated
http://code.google.com/p/lilypond/issues/detail?id=1027
Excellent; this is exactly what the "verified" step is supposed to
catch. :)
--
You received this message because you are listed in the
Updates:
Status: Fixed
Owner: Carl.D.Sorensen
Labels: fixed_2_13_20
Comment #8 on issue 1027 by n.puttock: LSR: minimum-Y-extent snippets need
to be updated
http://code.google.com/p/lilypond/issues/detail?id=1027
From a docs perspective this isn't fixed since the new s
Comment #9 on issue 1044 by Carl.D.Sorensen: Update lilybuntu and lily-git
(whitespace correction etc.)
http://code.google.com/p/lilypond/issues/detail?id=1044
The title of this issue is incorrect. No changes need to be made in
lily-git. It would be best to close this issue
and open a ne
Comment #7 on issue 1027 by percival.music.ca: LSR: minimum-Y-extent
snippets need to be updated
http://code.google.com/p/lilypond/issues/detail?id=1027
Eh? I see adjusted-lyrics-vertical-spacing.ly in
Documnetation/snippets/new/. That
means this issue is fixed, closed, and should be ver
Comment #25 on issue 838 by percival.music.ca: Inconsistency in tests
output size
http://code.google.com/p/lilypond/issues/detail?id=838
No. Patrick was just suggesting that I stop being so lazy and type
make LILYPOND_BRANCH=dev/gperciva lilypond
when I'm testing stuff, instead of copying
Comment #5 on issue 946 by percival.music.ca: build tarballs of docs
http://code.google.com/p/lilypond/issues/detail?id=946
Later suggestions:
we could also try making the html docs without the regtests. Snippets are
a main
manual, so I'm reluctant to omit them. Although I suppose we could
Updates:
Status: Verified
Comment #2 on issue 1049 by v.villenave: GUB should push git tags
http://code.google.com/p/lilypond/issues/detail?id=1049
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of this issue, or b
Updates:
Status: Verified
Comment #10 on issue 844 by v.villenave: clean up website maintenance
http://code.google.com/p/lilypond/issues/detail?id=844
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields of this issue, o
Updates:
Summary: LSR: minimum-Y-extent snippets need to be updated
Status: Accepted
Labels: -Priority-Critical -Spacing -fixed2_13_19 Priority-Low LSR
Comment #6 on issue 1027 by v.villenave: LSR: minimum-Y-extent snippets
need to be updated
http://code.google.com/p/li
Updates:
Status: Fixed
Comment #1 on issue 1049 by percival.music.ca: GUB should push git tags
http://code.google.com/p/lilypond/issues/detail?id=1049
This was fixed a while ago by me getting a github account. You can see the
tags in
the GUB git repo now.
--
You received this messag
Updates:
Status: Verified
Comment #3 on issue 1032 by v.villenave: Documentation:
automatically-generated list of articulations
http://code.google.com/p/lilypond/issues/detail?id=1032
Wow, impressive. And the Feta index too. Thanks Mark!
--
You received this message because you are l
Updates:
Status: Verified
Comment #3 on issue 1024 by v.villenave: measure width should adapt to
MetronomeMarks
http://code.google.com/p/lilypond/issues/detail?id=1024
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fie
Updates:
Status: Verified
Comment #8 on issue 1017 by v.villenave: migrate old essay
http://code.google.com/p/lilypond/issues/detail?id=1017
Andrew's sampler is very interesting. Nice work!
--
You received this message because you are listed in the owner
or CC fields of this issue, or b
Updates:
Summary: Update lilybuntu and lily-git (whitespace correction etc.)
Status: Accepted
Labels: -Type-Scripts -Priority-High Type-Other Priority-Postponed
Comment #8 on issue 1044 by v.villenave: Update lilybuntu and lily-git
(whitespace correction etc.)
http://co
Updates:
Status: Verified
Comment #7 on issue 993 by v.villenave: translation infrastructure for new
website
http://code.google.com/p/lilypond/issues/detail?id=993
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or CC fields
Updates:
Status: Verified
Comment #6 on issue 1021 by v.villenave: Remove dependence on the
feta-alphabet Type 1 fonts
http://code.google.com/p/lilypond/issues/detail?id=1021
(No comment was entered for this change.)
--
You received this message because you are listed in the owner
or
Updates:
Status: Verified
Comment #12 on issue 974 by v.villenave: music overflows page
http://code.google.com/p/lilypond/issues/detail?id=974
This issue is verified (but issue 1025 doesn't seem to be fully addressed
right now).
--
You received this message because you are listed in
Updates:
Status: Verified
Comment #24 on issue 838 by v.villenave: Inconsistency in tests output size
http://code.google.com/p/lilypond/issues/detail?id=838
Patrick, your idea of having a "testing" branch is nice; do you want me to
open a
tracker page for dealing with git branches str
Updates:
Status: Verified
Comment #9 on issue 669 by v.villenave: \override 'bar-size + \remove
Staff_symbol_engraver = mess with ties and slurs
http://code.google.com/p/lilypond/issues/detail?id=669
... and Verified.
--
You received this message because you are listed in the owner
o
Updates:
Status: Verified
Comment #10 on issue 68 by v.villenave: certain \paper variables put music
at the bottom of the page (easy workaround)
http://code.google.com/p/lilypond/issues/detail?id=68
OK, Verified.
Wow: is it just me, or do you guys feel dizzy too when comparing
bet
Updates:
Status: Verified
Labels: Spacing
Comment #9 on issue 1053 by v.villenave: Severe overestimation of line
height for significantly non-rectangular systems
http://code.google.com/p/lilypond/issues/detail?id=1053
The spacing looks good to me with 2.13.19. Closing.
--
You
Updates:
Status: Started
Owner: joeneeman
Labels: -fixed_2_13_19
Comment #2 on issue 1025 by v.villenave: Lyrics with alignAboveContext are
not taken into account in Vertical spacing
http://code.google.com/p/lilypond/issues/detail?id=1025
Joe, I'm still getting a colli
Updates:
Status: Verified
Comment #8 on issue 917 by v.villenave: Regression: Full-bar rests take
more space at the beginning of a line
http://code.google.com/p/lilypond/issues/detail?id=917
... And Verified.
--
You received this message because you are listed in the owner
or CC fiel
Updates:
Status: Verified
Comment #4 on issue 899 by v.villenave: full-measure-extra-space should be
more flexible
http://code.google.com/p/lilypond/issues/detail?id=899
It does look a bit better now.
--
You received this message because you are listed in the owner
or CC fields of th
Updates:
Status: Verified
Comment #17 on issue 786 by v.villenave: Extenders in lyrics stop
prematurely if a single underscore is found
http://code.google.com/p/lilypond/issues/detail?id=786
... Aand Verified. Thanks Neil!
--
You received this message because you are listed in the ow
39 matches
Mail list logo
