David Kastrup wrote Thursday, January 26, 2012 5:12 AM
Basically the situations where the behavior will be _noticeably_
different are when you have a \relative with a q in it before any other
chord. Or when you use music variables with a q in them before any
other chord, and employ those in
Comment #5 on issue 2044 by gra...@percival-music.ca: convert-ly fails on
input with invalid version string
http://code.google.com/p/lilypond/issues/detail?id=2044
Yes, you should always give a .0 if that's what you intended: 2.15.0.
If you want a warning in lilypond.exe, open a new issue
Comment #12 on issue 39 by elu...@gmail.com: collision flag notehead with
polyphony
http://code.google.com/p/lilypond/issues/detail?id=39
here is another quite frequent flag notehead collision:
\relative c' { g' a8 }
Attachments:
test2.png 10.9 KB
Updates:
Status: Verified
Comment #6 on issue 2044 by elu...@gmail.com: convert-ly fails on input
with invalid version string
http://code.google.com/p/lilypond/issues/detail?id=2044
no, I can live with that - verified!
___
bug-lilypond
Updates:
Status: Verified
Comment #11 on issue 2224 by elu...@gmail.com: LM: clickable examples in
the docs have stopped working.
http://code.google.com/p/lilypond/issues/detail?id=2224
(No comment was entered for this change.)
___
Updates:
Status: Verified
Comment #6 on issue 2220 by elu...@gmail.com: Undefined references to node
in translated manuals
http://code.google.com/p/lilypond/issues/detail?id=2220
LGTM
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Updates:
Status: Verified
Comment #11 on issue 2200 by elu...@gmail.com: Dots shouldn't always be
placed in one column
http://code.google.com/p/lilypond/issues/detail?id=2200
(No comment was entered for this change.)
___
bug-lilypond
Comment #19 on issue 2180 by n.putt...@gmail.com: beams are detached from
stems
http://code.google.com/p/lilypond/issues/detail?id=2180
It's from the fix for issue 2193, which I argued is misguided. Beams
shouldn't encompass rests from other voices.
On 22/01/2012 20:58, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
The problem here is that lilypond builds up memory from 400MB
Updates:
Status: Verified
Comment #20 on issue 2180 by elu...@gmail.com: beams are detached from stems
http://code.google.com/p/lilypond/issues/detail?id=2180
ok - verified
___
bug-lilypond mailing list
bug-lilypond@gnu.org
- Original Message -
From: Reinhold Kainhofer reinh...@kainhofer.com
To: Julien Rioux jri...@physics.utoronto.ca
Cc: lilypond-de...@gnu.org; bug-lilypond@gnu.org
Sent: Thursday, January 26, 2012 4:13 PM
Subject: Re: make doc problem
On 22/01/2012 20:58, Julien Rioux wrote:
Thanks,
Graham Percival gra...@percival-music.ca wrote in message
news:20120124232213.GA8188@futoi...
On Tue, Jan 24, 2012 at 03:10:46PM -0800, -Eluze wrote:
when a bug is fixed its status changes to fixed and one would think
it's
just peanuts to verify that once the new version is out
Yep. :(
Updates:
Status: Accepted
Comment #9 on issue 2249 by philehol...@gmail.com: ledger lines of pitched
rests are verticaly misplaced
http://code.google.com/p/lilypond/issues/detail?id=2249
It seems to me this is a valid bug report - the rests should have ledger
lines if they're
Comment #3 on issue 2248 by philehol...@gmail.com: Patch: change bugreports
expected response time
http://code.google.com/p/lilypond/issues/detail?id=2248
With Graham's change to 4 days: don't believe a count-down is needed - push
directly to staging (assuming make doc is good!).
Updates:
Status: Fixed
Labels: -Patch-push
Comment #5 on issue 2238 by pkx1...@gmail.com: Patch: Spelling fixes in
comments and documentation
http://code.google.com/p/lilypond/issues/detail?id=2238
author Stefan Weil s...@weilnetz.de
Thu, 19 Jan 2012 21:23:33 +
Updates:
Status: Fixed
Labels: -Patch-push
Comment #5 on issue 2227 by pkx1...@gmail.com: Patch: changes.tely: mention
Flag changes, remove duplicate does
http://code.google.com/p/lilypond/issues/detail?id=2227
Pavel, I pushed for you.
author Pavel Roskin pro...@gnu.org
Updates:
Status: Fixed
Labels: -Type-Enhancement -Patch-push Type-Documentation
Comment #5 on issue 2225 by pkx1...@gmail.com: Patch: Docs: Explain the
difference between ritardando and rallentando
http://code.google.com/p/lilypond/issues/detail?id=2225
Pavel, I pushed this
Updates:
Owner: janek.li...@gmail.com
Comment #5 on issue 1985 by pkx1...@gmail.com: musicxml2ly: group-symbol
none leads to bus error
http://code.google.com/p/lilypond/issues/detail?id=1985
(No comment was entered for this change.)
___
Comment #10 on issue 2249 by elu...@gmail.com: ledger lines of pitched
rests are verticaly misplaced
http://code.google.com/p/lilypond/issues/detail?id=2249
yes, but in my first post I was thinking that the ledger line of the rests
outside of a staff should be aligned with the notes'
Hi,
i think the output of beam-shortened-lengths.ly doesn't look good, see
in current regtests
http://www.lilypond.org/doc/v2.15/input/regression/collated-files.html
. Am i missing something?
cheers,
Janek
___
bug-lilypond mailing list
On 22/01/2012 2:58 PM, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the build.
Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
Could we redistribute the regression test input files into
On 26/01/2012 11:13 AM, Reinhold Kainhofer wrote:
On 22/01/2012 20:58, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the
build. Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
The problem
On Thu, Jan 26, 2012 at 05:57:43PM -0500, Julien Rioux wrote:
On 22/01/2012 2:58 PM, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the build.
Disk access and usage of swap when compiling
input/regression/collated-files slows down the build to a crawl for me.
On 26/01/2012 6:14 PM, Graham Percival wrote:
On Thu, Jan 26, 2012 at 05:57:43PM -0500, Julien Rioux wrote:
On 22/01/2012 2:58 PM, Julien Rioux wrote:
Thanks, you're quite right CPU is not the limiting factor for the build.
Disk access and usage of swap when compiling
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 2255 by ralphbug...@gmail.com: Margin adjustment documentation
http://code.google.com/p/lilypond/issues/detail?id=2255
Xavier Scheuer writes :
after having defined top-margin = 5\cm you override
this with #(set-paper-size letter
On Mon, Jan 23, 2012 at 6:38 PM, Xavier Scheuer x.sche...@gmail.com wrote:
On 24 January 2012 00:25, -Eluze elu...@gmail.com wrote:
it's not ignored - but after having defined top-margin = 5\cm you
override
this with #(set-paper-size letter)
changing this order will do what you
Status: Accepted
Owner:
Labels: Type-Defect
New issue 2256 by ralphbug...@gmail.com: empty strings: tabStaff insists on
stringnumbers and looses notes
http://code.google.com/p/lilypond/issues/detail?id=2256
S. Runkel writes :
\version 2.14.2
\makeStringTuning #'custom-tuning c g d' a'
On Tue, Jan 24, 2012 at 1:21 AM, S. Runkel s.run...@runkel-it.de wrote:
%{
Phil,
Please find a revised example for *2.14.2*
It will not work on 2.12 but shows the bug at 2.14 on its own.
%}
\version 2.14.2
\makeStringTuning #'custom-tuning c g d' a'
\score {
\new TabStaff {
\set
Updates:
Labels: -Patch-countdown Patch-push
Comment #6 on issue 803 by colinpkc...@gmail.com: correction needed for the
German translation of convert-ly
http://code.google.com/p/lilypond/issues/detail?id=803
Counted down to 20120126, please push
Updates:
Labels: -Patch-countdown Patch-push
Comment #13 on issue 2189 by colinpkc...@gmail.com: Doc: NR add to
\partial for clearer understanding
http://code.google.com/p/lilypond/issues/detail?id=2189
Counted down to 20120126, please push
Updates:
Labels: -Patch-countdown Patch-push
Comment #12 on issue 2223 by colinpkc...@gmail.com: Regtest for
lilypond-book are not running
http://code.google.com/p/lilypond/issues/detail?id=2223
Counted down to 20120126, please push
Updates:
Labels: -Patch-countdown Patch-push
Comment #4 on issue 2248 by colinpkc...@gmail.com: Patch: change bugreports
expected response time
http://code.google.com/p/lilypond/issues/detail?id=2248
Counted down to 20120126, please push after the change
Status: Accepted
Owner:
Labels: Type-Critical Regression
New issue 2257 by k-ohara5...@oco.net: reg-test beam-shortened-lengths.ly
fails
http://code.google.com/p/lilypond/issues/detail?id=2257
\header{
texidoc=Beams in unnatural direction, have shortened stems, but do not
look too
Updates:
Status: Invalid
Labels: -Type-Ugly Type-Enhancement
Comment #11 on issue 2249 by k-ohara5...@oco.net: ledger lines of pitched
rests are verticaly misplaced
http://code.google.com/p/lilypond/issues/detail?id=2249
Ross (p174) says that when you need to put a whole rest
Updates:
Labels: Patch-new
Comment #1 on issue 2256 by carl.d.s...@gmail.com: empty strings: tabStaff
insists on stringnumbers and looses notes
http://code.google.com/p/lilypond/issues/detail?id=2256#c1
Allow open strings in chords regardless of finger positions (issue 2256)
Comment #2 on issue 2257 by m...@apollinemike.com: reg-test
beam-shortened-lengths.ly fails
http://code.google.com/p/lilypond/issues/detail?id=2257
Hmm...I'll have a look - pester me if I forget!
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Comment #2 on issue 2258 by k-ohara5...@oco.net: Bad regression
test 'beam-shortened-lengths.ly'
http://code.google.com/p/lilypond/issues/detail?id=2258
The regression test went bad between 2.14.2 and 2.15.14
No no. I was again confused by the change to the test itself.
This regression
37 matches
Mail list logo
