Comment #12 on issue 1875 by pkx1...@gmail.com: tests for flower appear to
miss instantiations of classes
http://code.google.com/p/lilypond/issues/detail?id=1875
David,
Is there a specific way you want me to test this against whatever current
master is?
I'm slightly unsure if just applyi
Updates:
Status: Started
Owner: mts...@gmail.com
Labels: -Patch-new Patch-review
Comment #2 on issue 2059 by pkx1...@gmail.com: Bar numbering of alternatives
http://code.google.com/p/lilypond/issues/detail?id=2059
Passes Make and make check just gives me
--snip--
/home/
http://lilypond.org/doc/v2.14/Documentation/music-glossary/appoggiatura
isn't cross-referenced as it could be, see:
http://lilypond.org/doc/v2.14/Documentation/music-glossary/acciaccatura
suggest also adding "mordent" to all of the already associated group (grace,
notes, ornament, appoggiatura,
Comment #15 on issue 2057 by k-ohara5...@oco.net: Hairpin hits barline at
line break
http://code.google.com/p/lilypond/issues/detail?id=2057
I added issue 2060, with linked patch, to make the existing "bound-padding"
be applied to hairpins consistently.
Status: Started
Owner:
Labels: Patch-new Type-Ugly
New issue 2060 by k-ohara5...@oco.net: Patch: Hairpin missing padding at
line break
http://code.google.com/p/lilypond/issues/detail?id=2060
%% Hairpin at a line break reaches the end of the bar,
%% whereas for a normal bar (i.e. not at a
On Mon, Nov 28, 2011 at 06:05:35PM -0700, Colin Campbell wrote:
> On 11-11-28 11:39 AM, Phil Holmes wrote:
> >This presumes that the Bug squad can and do run Git, which is a
> >false presumption.
+1
> More specifically, I believe it requires a Linux build environment,
> to be truly effective.
If
Colin Campbell writes:
> On 11-11-28 11:39 AM, Phil Holmes wrote:
>> "David Kastrup" wrote in message
>> news:87r50syvzn@fencepost.gnu.org...
>>
>>> Actually, the verification for a commit id to be in master can be as
>>> simple as
>>>
>>> git fetch
>>> git log origin..cf93b1df71253b2686ceab
Comment #27 on issue 1997 by d...@gnu.org: segfault in
tablature-negative-fret.ly
http://code.google.com/p/lilypond/issues/detail?id=1997#c27
Work around compiler bug, Issue 1997: segfault in tablature-negative-fret.ly
http://codereview.appspot.com/5431088
_
On 11-11-28 11:39 AM, Phil Holmes wrote:
"David Kastrup" wrote in message
news:87r50syvzn@fencepost.gnu.org...
Graham Percival writes:
On Mon, Nov 28, 2011 at 11:16:55AM +0100, David Kastrup wrote:
Graham Percival writes:
> Too hard for people with less than 5 hours of training to
> d
Updates:
Status: Verified
Comment #9 on issue 1971 by colinpkc...@gmail.com: Slashed flags no longer
work
http://code.google.com/p/lilypond/issues/detail?id=1971
Verified per Phil's instructions.
___
bug-lilypond mailing list
bug-lilypond@
Updates:
Owner: adam.spi...@gmail.com
Comment #39 on issue 1503 by carl.d.s...@gmail.com: Feature request:
simplify jazz chord display
http://code.google.com/p/lilypond/issues/detail?id=1503
Correct owner, giving credit where it's due. Thanks, Adam.
___
Updates:
Owner: adam.spi...@gmail.com
Labels: -fixed_2_15_20 fixed_2_15_21
Comment #24 on issue 1572 by carl.d.s...@gmail.com: Change chord name
separator and inversion separator, separately
http://code.google.com/p/lilypond/issues/detail?id=1572
Change fixed version
___
Comment #26 on issue 1997 by carl.d.s...@gmail.com: segfault in
tablature-negative-fret.ly
http://code.google.com/p/lilypond/issues/detail?id=1997
Looking at Jakub's response to you, it appears that he is in favor of
moving to non-buggy compilers, with which I agree. But we don't currently
Updates:
Labels: -fixed_2_15_20 fixed_2_15_21
Comment #38 on issue 1503 by carl.d.s...@gmail.com: Feature request:
simplify jazz chord display
http://code.google.com/p/lilypond/issues/detail?id=1503
It's actually fixed_2_15_21, because .20 is already released. This will
appear in .
Comment #37 on issue 1503 by carl.d.s...@gmail.com: Feature request:
simplify jazz chord display
http://code.google.com/p/lilypond/issues/detail?id=1503
NC is already implemented. Put a rest in your ChordNames context and you
get NC.
___
bug-l
Updates:
Labels: Patch-new
Comment #1 on issue 2059 by mts...@gmail.com: Bar numbering of alternatives
http://code.google.com/p/lilypond/issues/detail?id=2059
Allows for automatic renumbering of measure numbers at volta repeats.
http://codereview.appspot.com/5440049/
_
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_20
Comment #23 on issue 1572 by adam.spi...@gmail.com: Change chord name
separator and inversion separator, separately
http://code.google.com/p/lilypond/issues/detail?id=1572
Pushed fix to staging as ee5738e01788aa2d.
___
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_20
Comment #36 on issue 1503 by adam.spi...@gmail.com: Feature request:
simplify jazz chord display
http://code.google.com/p/lilypond/issues/detail?id=1503
maestraccio - please could you submit a fresh issue for that? This
Comment #14 on issue 2057 by mts...@gmail.com: Hairpin hits barline at line
break
http://code.google.com/p/lilypond/issues/detail?id=2057
Sorry - previous posted file was incorrect.
Attachments:
hairpin.pdf 36.8 KB
___
bug-lilypond maili
Comment #13 on issue 2057 by mts...@gmail.com: Hairpin hits barline at line
break
http://code.google.com/p/lilypond/issues/detail?id=2057
Attached is the most recent version of the new regtest in light of the
conversation about everything lining up.
Attachments:
xav.pdf 29.1 KB
Updates:
Status: Started
Comment #4 on issue 1236 by adam.spi...@gmail.com: CG+scripts should use
$LILYPOND_GIT
http://code.google.com/p/lilypond/issues/detail?id=1236
Pushed f955789f0e1726c03b554a9fde21494687ae95b8 to staging which addresses
several of the issues here, if not all.
Updates:
Labels: Patch-new
Comment #12 on issue 2057 by mts...@gmail.com: Hairpin hits barline at line
break
http://code.google.com/p/lilypond/issues/detail?id=2057#c12
Adds padding between Hairpins and SpanBars.
http://codereview.appspot.com/5438060
___
Updates:
Status: Fixed
Labels: -Patch-needs_work fixed_2_15_20
Comment #5 on issue 2015 by adam.spi...@gmail.com: Patch: Usability
improvements to {doc,cg}-section.sh and corresponding section of CG
http://code.google.com/p/lilypond/issues/detail?id=2015
Pushed to staging as f
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_20
Comment #7 on issue 2014 by adam.spi...@gmail.com: Patch: Improve HTML
output of regression tests
http://code.google.com/p/lilypond/issues/detail?id=2014
Pushed to staging as 1294535b8f2f0af706bae047e6c4393bb2dea1f1
__
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_20
Comment #5 on issue 2020 by adam.spi...@gmail.com: Patch: avoid cryptic
StopIteration failure from make when 'make check' is run before 'make
test-baseline'
http://code.google.com/p/lilypond/issues/detail?id=2020
Pushe
Comment #11 on issue 2057 by prze...@gmail.com: Hairpin hits barline at
line break
http://code.google.com/p/lilypond/issues/detail?id=2057
It's all about obtaining sane behavior and IMO hairpin length should be the
same whether there is span bar or just bar. Is there any good reason to
ma
Comment #10 on issue 2057 by carl.d.s...@gmail.com: Hairpin hits barline at
line break
http://code.google.com/p/lilypond/issues/detail?id=2057
This second request seems to me to be a new issue, i.e. Hairpins in
parallel with those shortened to avoid collisions with span bars should
also b
Updates:
Labels: -Patch-new Patch-review
Comment #4 on issue 2011 by pkx1...@gmail.com: configure doesn't like
clang++
http://code.google.com/p/lilypond/issues/detail?id=2011
Passes make and make check, I also removed the build dir I use and redid
autogen.sh --noconfigure and then r
Comment #25 on issue 1997 by d...@gnu.org: segfault in
tablature-negative-fret.ly
http://code.google.com/p/lilypond/issues/detail?id=1997
If you look at the GCC bug URL given in comment 17, you'll see that Jakub
Jelinek has given a self-contained example that is supposed to correlate
with
"David Kastrup" wrote in message
news:87r50syvzn@fencepost.gnu.org...
Graham Percival writes:
On Mon, Nov 28, 2011 at 11:16:55AM +0100, David Kastrup wrote:
Graham Percival writes:
> Too hard for people with less than 5 hours of training to
> determine.
I am not sure I understand that
Comment #9 on issue 2057 by x.sche...@gmail.com: Hairpin hits barline at
line break
http://code.google.com/p/lilypond/issues/detail?id=2057
+1, hairpin ends vertically aligned in a similar way.
(i.e. I agree with the comment just above, #c8)
___
b
Comment #8 on issue 2057 by prze...@gmail.com: Hairpin hits barline at line
break
http://code.google.com/p/lilypond/issues/detail?id=2057
I think that for system's integrity and good looking result all hairpins
should have equal length if defined in the same way, thus shortening should
ha
Updates:
Labels: -Patch-new Patch-review
Comment #15 on issue 2051 by pkx1...@gmail.com: Patch: Better pure heights
for slurs
http://code.google.com/p/lilypond/issues/detail?id=2051
Passes Make.
Reg tests here
http://lilypond-stuff.1065243.n5.nabble.com/Tracker-2051-28-November-Test
Graham Percival writes:
> On Mon, Nov 28, 2011 at 11:16:55AM +0100, David Kastrup wrote:
>> Graham Percival writes:
>>
>> > Too hard for people with less than 5 hours of training to
>> > determine.
>>
>> I am not sure I understand that rationale.
>>
>> git log origin
>>
>> Is it there or not
Comment #7 on issue 2057 by k-ohara5...@oco.net: Hairpin hits barline at
line break
http://code.google.com/p/lilypond/issues/detail?id=2057
I received a question about the desired behavior.
Currently a hairpin below the staff group ends directly below the parallel
hairpin above.
At the en
On Mon, Nov 28, 2011 at 11:16:55AM +0100, David Kastrup wrote:
> Graham Percival writes:
>
> > Too hard for people with less than 5 hours of training to
> > determine.
>
> I am not sure I understand that rationale.
>
> git log origin
>
> Is it there or not? Can you think of a _simpler_ test t
Updates:
Labels: -Patch-new Patch-review
Comment #4 on issue 2052 by pkx1...@gmail.com: Patch: Asserts that
footnotes are being numbered correctly.
http://code.google.com/p/lilypond/issues/detail?id=2052
Passes make and make check
James
_
Am 27.11.11 23:31, schrieb TW:
I'm not really a Lilypond user, but I noticed the improper use of
terminology, so I decided at least to try making the world a better
place by reporting it ;-).
OK, thank you for that report. So I understand it applies only to change
"Bindebogen" into
"Haltebogen".
Updates:
Labels: Patch-new
Comment #10 on issue 1875 by d...@gnu.org: tests for flower appear to miss
instantiations of classes
http://code.google.com/p/lilypond/issues/detail?id=1875#c10
Better fix for issue 1875: use -lsupc++ if required.
This will cause working demangling even whe
Actually this "bug" happend after I've tried to adapt an example from the
lsr.
Those snippets do not have the version attached.
'have to admit that I never convert 'em before I try.
Thank you all for this good advise !
2011/11/28 James
> Hello,
>
> On 28 November 2011 14:56, David Kastrup wrote
Updates:
Labels: -Patch-new Patch-review
Comment #6 on issue 2057 by pkx1...@gmail.com: Hairpin hits barline at line
break
http://code.google.com/p/lilypond/issues/detail?id=2057
Passes Make and make check
james
___
bug-lilypond mailing l
Updates:
Labels: -Patch-new Fixed_2_15_21
Comment #8 on issue 1971 by philehol...@gmail.com: Slashed flags no longer
work
http://code.google.com/p/lilypond/issues/detail?id=1971
Fixed with cf93b1df71253b2686ceabacdf49a47e6908da64. To verify - go to the
NR, section 1.2.6 and scroll
Hello,
On 28 November 2011 14:56, David Kastrup wrote:
> ...
> I don't think we advertise this enough.
>
>
>
You might be right and I suppose once we move to a 2.16.x version we will
get more of these types of questions?
Perhaps we might have a standard 'strapline' somewhere
http://lilypond.
Pierre Perol-Schneider writes:
> 2011/11/28 David Kastrup
>> Pierre Perol-Schneider writes:
[...]
>> The syntax has changed in 2.15.10. If you had updated your file using
>>
>> convert-ly -ed
>>
>> on the last working version of that file (with a \version string
>> corresponding to a version
On 2011-11-28 09:44, Colin Hall wrote:
On Mon, Nov 28, 2011 at 01:04:06AM +0100, Xavier Scheuer wrote:
Dear LilyPond developers,
Dear Bug Squad members, could you add this enhancement request to
the tracker? Thanks!
This is by far the most popular enhancement request from the French
users ma
Oups... sorry !
2011/11/28 David Kastrup
> Pierre Perol-Schneider writes:
>
> >> I'm not top posting.
> >
> > Hi to all,
> >
> > % \override Stem #'stroke-style = #"grace"
> > % do not affect Stem
> >
> > \version "2.15.20"
> >
> > \relative c'' {
> > \override Stem #'stroke-style = #"grace"
>
Pierre Perol-Schneider writes:
>> I'm not top posting.
>
> Hi to all,
>
> % \override Stem #'stroke-style = #"grace"
> % do not affect Stem
>
> \version "2.15.20"
>
> \relative c'' {
> \override Stem #'stroke-style = #"grace"
> g8
> }
The syntax has changed in 2.15.10. If you had updated your
> I'm not top posting.
Hi to all,
% \override Stem #'stroke-style = #"grace"
% do not affect Stem
\version "2.15.20"
\relative c'' {
\override Stem #'stroke-style = #"grace"
g8
}
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.o
Updates:
Status: Verified
Labels: -Patch-push fixed_2_15_21
Comment #4 on issue 2050 by carl.d.s...@gmail.com: Patch: Fix compile on
OSX by including std-vector.hh instead of
http://code.google.com/p/lilypond/issues/detail?id=2050
Pushed to staging as 1522c116793b70b50c54b269
Updates:
Status: Started
Labels: -fixed_2_15_21 Patch-countdown
Comment #8 on issue 2048 by carl.d.s...@gmail.com: shiftDurations with
negative 2nd argument loops indefinitely
http://code.google.com/p/lilypond/issues/detail?id=2048
Oops -- wrong patch. THis one is still on co
Updates:
Status: Verified
Labels: -Patch-countdown fixed_2_15_21
Comment #7 on issue 2048 by carl.d.s...@gmail.com: shiftDurations with
negative 2nd argument loops indefinitely
http://code.google.com/p/lilypond/issues/detail?id=2048
Pushed to staging, as commit 1522c116793b70b
Updates:
Labels: Patch-new
Comment #24 on issue 1997 by d...@gnu.org: segfault in
tablature-negative-fret.ly
http://code.google.com/p/lilypond/issues/detail?id=1997#c24
Work around compiler bug, Issue 1997: segfault in tablature-negative-fret.ly
http://codereview.appspot.com/5431088
Comment #23 on issue 1997 by d...@gnu.org: segfault in
tablature-negative-fret.ly
http://code.google.com/p/lilypond/issues/detail?id=1997
The right option for avoiding the bad optimization would appear to be
-fno-optimize-sibling-calls and, frankly, it is actually insane that
-fkeep-inlin
Graham Percival writes:
> On Mon, Nov 28, 2011 at 10:54:31AM +0100, David Kastrup wrote:
>> Hm. Should we really "verify" already when the commit made it to
>> staging?
>
> Yes. Brief discussion was 1-3 weeks ago.
>
>> That makes the state rather arbitrary. I'd wait at least
>> until it has mi
On Mon, Nov 28, 2011 at 10:54:31AM +0100, David Kastrup wrote:
> Hm. Should we really "verify" already when the commit made it to
> staging?
Yes. Brief discussion was 1-3 weeks ago.
> That makes the state rather arbitrary. I'd wait at least
> until it has migrated "properly" to master (since t
lilyp...@googlecode.com writes:
> Updates:
> Status: Verified
>
> Comment #12 on issue 1356 by colingh...@gmail.com: LilyPond-style
> comments embedded in a Scheme expression can't include special
> characters
> http://code.google.com/p/lilypond/issues/detail?id=1356
>
> Verified commit pres
Updates:
Status: Fixed
Labels: -Patch-push Fixed_2_15_21
Comment #14 on issue 1838 by d...@gnu.org: Make accidental styles available
as context mods
http://code.google.com/p/lilypond/issues/detail?id=1838
Pushed as 83e6304ae3cc708a8e4d0462249ca8babae265a3 and the two preceding
Updates:
Status: Verified
Comment #12 on issue 1356 by colingh...@gmail.com: LilyPond-style comments
embedded in a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356
Verified commit present on Savannah
_
Updates:
Labels: Patch-new
Comment #3 on issue 2011 by lilypond...@gmail.com: configure doesn't like
clang++
http://code.google.com/p/lilypond/issues/detail?id=2011#c3
Build: don't check gcc version numbers with clang
Joy, this was totally worth an hour. :( I hate build systems.
Updates:
Status: Fixed
Labels: -Type-Documentation -Patch-push Type-Defect Fix_2_15_21
Comment #11 on issue 1356 by d...@gnu.org: LilyPond-style comments embedded
in a Scheme expression can't include special characters
http://code.google.com/p/lilypond/issues/detail?id=1356
Pu
Updates:
Status: Verified
Comment #2 on issue 2054 by colingh...@gmail.com: CG has out-of-date
instructions for issue classification
http://code.google.com/p/lilypond/issues/detail?id=2054
Verified commit is present on Savannah.
___
bug-li
On Mon, Nov 28, 2011 at 01:04:06AM +0100, Xavier Scheuer wrote:
> Dear LilyPond developers,
>
> Dear Bug Squad members, could you add this enhancement request to
> the tracker? Thanks!
>
> This is by far the most popular enhancement request from the French
> users mailing list: Bar numbering of
Status: Accepted
Owner:
Labels: Type-Enhancement
New issue 2059 by colingh...@gmail.com: Bar numbering of alternatives
http://code.google.com/p/lilypond/issues/detail?id=2059
Requested by Xavier Scheuer x.sche...@gmail.com
This is by far the most popular enhancement request from the French
Updates:
Status: Started
Cc: gra...@percival-music.ca
Comment #22 on issue 1997 by d...@gnu.org: segfault in
tablature-negative-fret.ly
http://code.google.com/p/lilypond/issues/detail?id=1997
Graham, you have a 64bit target. The code generator for that is entirely
different
Comment #21 on issue 1997 by gra...@percival-music.ca: segfault in
tablature-negative-fret.ly
http://code.google.com/p/lilypond/issues/detail?id=1997
hmm, fun and joy here. Brand new mac mini, brand new installation of
ubuntu 11.10. make, make doc, make test-baseline, make check is happy.
65 matches
Mail list logo
