Updates:
Labels: -Fixed_2_15_34 Fixed_2_15_35
Comment #27 on issue 984 by k-ohara5...@oco.net: Noteheads don't merge when
one of the voices contains a second
http://code.google.com/p/lilypond/issues/detail?id=984
Probably this fix will not appear until version .35 (the commit was stil
> I'm not top posting.
Hi,
if a note in voiceTwo is above the one in voiceOne, a slur starting in voiceTwo
will collide with the note head of voiceOne. The following example will
reproduce the problem (and does so with version 2.12.3, I didn't test 2.14.2).
%%%
\version "
Updates:
Labels: Patch-review
Comment #7 on issue 2418 by d...@gnu.org: Patch: Don't copy GNUmakefile and
*.make from within builddir to builddir
http://code.google.com/p/lilypond/issues/detail?id=2418#c7
Patchy the autobot says: LGTM.
___
Updates:
Labels: Patch-new
Comment #8 on issue 2418 by d...@gnu.org: Patch: Don't copy GNUmakefile and
*.make from within builddir to builddir
http://code.google.com/p/lilypond/issues/detail?id=2418#c8
Don't copy GNUmakefile and *.make from within builddir to builddir
http://coderevi
Comment #26 on issue 984 by colingh...@gmail.com: Noteheads don't merge
when one of the voices contains a second
http://code.google.com/p/lilypond/issues/detail?id=984
I just started verifying this one but ran out of time. A couple of test
files are attached, extracted from above. I'll fini
Updates:
Status: Verified
Comment #14 on issue 2387 by colingh...@gmail.com: Patch: Allow music in
contextmods
http://code.google.com/p/lilypond/issues/detail?id=2387
Verified that all seven of the commit IDs above are part of release 2.15.34.
___
Updates:
Status: Verified
Comment #14 on issue 2378 by colingh...@gmail.com: Patch: Various updates
to reduce make doc output
http://code.google.com/p/lilypond/issues/detail?id=2378
Verified that the committish for this patch was part of the 2.15.34 release.
Updates:
Status: Verified
Comment #29 on issue 2348 by colingh...@gmail.com: Patch: Handling of open
strings in tablature
http://code.google.com/p/lilypond/issues/detail?id=2348
Verified that the commitish for this patch was part of release 2.15.34.
_
Comment #10 on issue 2169 by colingh...@gmail.com: Patch: Doc: Introduce
Voices in the correct order. Mention that hideNotes hides beams
http://code.google.com/p/lilypond/issues/detail?id=2169
Trevor, could you supply a committish for this patch, please?
On Tue, Mar 20, 2012 at 12:28 AM, Graham Percival
wrote:
> On Tue, Mar 20, 2012 at 12:11:46AM +0100, David Kastrup wrote:
>> So instead of surprising volunteers by giving them more information than
>> expected we give them less information than expected?
>
> Bug squad members shouldn't be reading
On Mon, Mar 19, 2012 at 12:13:05PM -0700, Eluze wrote:
>
>
> Jean-Charles Malahieude-2 wrote:
> >
> > Please find enclosed a draft. It is much less complicated than what
> > Keith O'Hara provided in
> > http://lists.gnu.org/archive/html/lilypond-user/2010-12/msg00674.html
> > which might help y
On Tue, Mar 20, 2012 at 12:11:46AM +0100, David Kastrup wrote:
> So instead of surprising volunteers by giving them more information than
> expected we give them less information than expected?
Bug squad members shouldn't be reading tracker messages anyway.
http://lilypond.org/doc/v2.15/Documenta
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 2420 by colingh...@gmail.com: Combining lyrics lines
http://code.google.com/p/lilypond/issues/detail?id=2420
Reported by Jean-Charles Malahieude here:
http://lists.gnu.org/archive/html/bug-lilypond/2012-03/msg00753.html
http://ar
"Carey, Norman" writes:
> Thanks so much for your help.
>
> I was reluctant to download the unstable version 2.15 with all of the
> warnings attached
Well, "may not run" beats "will not run". We _are_ finding regressions
holding up a release of 2.16 with annoying regularity, but most
regression
We have a new mailing list for automatic messages. No human
emails are allowed; only whitelisted email addresses can send to
the list.
https://lists.gnu.org/mailman/listinfo/lilypond-auto
Scripts whose output should be sent to this list include:
- patchy staging-merge (both success and failure
Comment #2 on issue 2419 by carl.d.s...@gmail.com: Subdivide beam bug
2.15.33
http://code.google.com/p/lilypond/issues/detail?id=2419
Thanks for doing this, Ralph. This was a duplicate report that somehow got
kicked out today (the original date was March 9.
The original issue, Issue 2386
Comment #12 on issue 2386 by carl.d.s...@gmail.com: Inconsistent Beam
Subdivision
http://code.google.com/p/lilypond/issues/detail?id=2386
Issue 2419 has been merged into this issue.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.
Updates:
Status: Duplicate
Mergedinto: 2386
Comment #1 on issue 2419 by carl.d.s...@gmail.com: Subdivide beam bug
2.15.33
http://code.google.com/p/lilypond/issues/detail?id=2419
Thanks for doing this, Ralph. This was a duplicate report that somehow got
kicked out today (the
On Mon, Mar 19, 2012 at 05:36:03PM -0400, Carey, Norman wrote:
> Thanks so much for your help.
I did very little. There's a dedicated and talented team of developers who
really deserve your thanks. I've copied this reply to the developer mailing
list.
> I was reluctant to download the unstable
Hi All,
You may have seen the announcement that version 2.15.34 of Lilypond has been
released. It would be great to hear if it works for you on your respective
platforms so that I can update the table below.
|-+-++-+-+-|
| MacOS X | x
Thanks so much for your help.
I was reluctant to download the unstable version 2.15 with all of the warnings
attached but have just done so and I've at least gotten the program up and
running.
Thank you!
Deputy Executive Officer
DMA Performance
CUNY Graduate Center
Tel: (212) 817-8594
Office:
On Fri, Mar 9, 2012 at 10:29 PM, Nick Payne wrote:
> I would expect that all four beams should be subdivided, but only the
> second beam in the bar is being subdivided:
>
> \version "2.15.33"
>
> \relative c' {
>\set tupletSpannerDuration = #(ly:make-moment 1 4)
>\set baseMoment = #(ly:mak
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 2419 by ralphbug...@gmail.com: Subdivide beam bug 2.15.33
http://code.google.com/p/lilypond/issues/detail?id=2419
Nick Payne writes :
I would expect that all four beams should be subdivided, but only the
second beam in the bar is being s
Comment #6 on issue 2418 by d...@gnu.org: Patch: Don't copy GNUmakefile and
*.make from within builddir to builddir
http://code.google.com/p/lilypond/issues/detail?id=2418
As I said: lilypond uses _wildcards_ for finding things in its source
directory. Which is what caused this issue in th
Comment #5 on issue 2418 by gra...@percival-music.ca: Patch: Don't copy
GNUmakefile and *.make from within builddir to builddir
http://code.google.com/p/lilypond/issues/detail?id=2418
I don't want a ~/lilypond. I have a ~/src/, which has about 20
repositories (mostly git, but a few svn).
Comment #4 on issue 2418 by d...@gnu.org: Patch: Don't copy GNUmakefile and
*.make from within builddir to builddir
http://code.google.com/p/lilypond/issues/detail?id=2418
What keeps you from putting the source into ~/lilypond/src and the build
into ~/lilypond/build? The point of a separat
Comment #3 on issue 2418 by gra...@percival-music.ca: Patch: Don't copy
GNUmakefile and *.make from within builddir to builddir
http://code.google.com/p/lilypond/issues/detail?id=2418
Right. I'm stupid because I like to have
~/src/lilypond/
with everything belonging to lilypond in that direc
Comment #2 on issue 2418 by d...@gnu.org: Patch: Don't copy GNUmakefile and
*.make from within builddir to builddir
http://code.google.com/p/lilypond/issues/detail?id=2418
Well, I have to add that creating a build dir _within_ the source dir seems
like a rather stupid thing to do. It rathe
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2418 by d...@gnu.org: Patch: Don't copy GNUmakefile and *.make
from within builddir to builddir
http://code.google.com/p/lilypond/issues/detail?id=2418
Don't copy GNUmakefile and *.make from within builddir to builddir
http
Jean-Charles Malahieude-2 wrote:
>
> Please find enclosed a draft. It is much less complicated than what
> Keith O'Hara provided in
> http://lists.gnu.org/archive/html/lilypond-user/2010-12/msg00674.html
> which might help you understand what singers might read.
>
> You'll see what I mean by c
Updates:
Status: Fixed
Labels: -Patch-push Fixed_2_15_35
Comment #5 on issue 2395 by julien.r...@gmail.com: Patch: Update roadmap,
make and make doc info.
http://code.google.com/p/lilypond/issues/detail?id=2395
e3a319a4c3fd7fb0327160fe26b67df37d3f5410
5f2e79bd78f7c350167e61e38
Updates:
Status: Fixed
Labels: -Patch-push Fixed_2_15_35
Comment #5 on issue 2396 by julien.r...@gmail.com: Patch: Build: Better
error handling from build scripts.
http://code.google.com/p/lilypond/issues/detail?id=2396
2f84bbe9a6dc6ca2d9a49eae0bf094744e47f11d
__
Hi Phil,
On 19/03/12 11:31, lilyp...@googlecode.com wrote:
>
> Comment #4 on issue 2216 by pkx1...@gmail.com: AU: Document all
> options for lilypond -dhelp
> http://code.google.com/p/lilypond/issues/detail?id=2216
>
> I noticed Graham has some commments. I'd also like to make sure
> that my ter
Comment #7 on issue 2216 by d...@gnu.org: AU: Document all options for
lilypond -dhelp
http://code.google.com/p/lilypond/issues/detail?id=2216
Well, that's what happens if you say (set! some-symbol value): the variable
addressed by the interned symbol some-symbol is assigned a value.
The
Comment #6 on issue 2216 by pkx1...@gmail.com: AU: Document all options for
lilypond -dhelp
http://code.google.com/p/lilypond/issues/detail?id=2216
No I am not sure it is correct, however 'variable' isn't that helpful
either. Hence my request from the devs to point me in the right direction
Comment #5 on issue 2216 by elu...@gmail.com: AU: Document all options for
lilypond -dhelp
http://code.google.com/p/lilypond/issues/detail?id=2216
are you sure "symbol" is correct? imo it should be "variable" or "var":
this variable is assigned a value.
__
Comment #4 on issue 2216 by pkx1...@gmail.com: AU: Document all options for
lilypond -dhelp
http://code.google.com/p/lilypond/issues/detail?id=2216
I noticed Graham has some commments. I'd also like to make sure that my
terminology is correct.
I.e. the command
-d[symbol]=[value] or --def
Comment #8 on issue 2391 by pkx1...@gmail.com: Add Appendix entry for
Predefined Paper Sizes
http://code.google.com/p/lilypond/issues/detail?id=2391
I already do a make doc before I submit to patch-new, but as things change
during the review, I always do a make doc for something this signif
Updates:
Labels: Patch-review
Comment #3 on issue 2216 by d...@gnu.org: AU: Document all options for
lilypond -dhelp
http://code.google.com/p/lilypond/issues/detail?id=2216#c3
Patchy the autobot says: LGTM. But test-patches does not do a doc build.
Given sufficient horsepower, it
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 t
Updates:
Labels: Patch-review
Comment #7 on issue 2391 by d...@gnu.org: Add Appendix entry for Predefined
Paper Sizes
http://code.google.com/p/lilypond/issues/detail?id=2391#c7
Patchy the autobot says: LGTM. But test-patches does not do a doc build.
Given sufficient horsepower, it
Updates:
Labels: Patch-review
Comment #9 on issue 2397 by d...@gnu.org: Tuplet number incorrectly placed
when using additonal arriculations and/or abreak
http://code.google.com/p/lilypond/issues/detail?id=2397#c9
Patchy the autobot says: LGTM. No visible regtest changes. Of course,
Updates:
Labels: Patch-review
Comment #1 on issue 2417 by d...@gnu.org: Patch: Sets lilypond-id message
to type progress
http://code.google.com/p/lilypond/issues/detail?id=2417#c1
Patchy the autobot says: LGTM.
___
bug-lilypond mailing lis
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
___
44 matches
Mail list logo
