installed lilypond yesterday, But when I tried to run gcc just now, I said the
command was not found, so I checked my
PATH and it was cleared with only the path to my lilypond install listed!
I don't know if anyone else has had this issue or if it's already been
reported,
but this is really an
Comment #4 on issue 935 by colinpkc...@gmail.com: Enhancement: optional
arguments in music functions
http://code.google.com/p/lilypond/issues/detail?id=935
FWIW, I ran make and make check with no obvious problems. The regtests
showed some long lists of entries in logfiles (graphviz.log and
Updates:
Status: Fixed
Labels: fixed_2_15_12
Comment #2 on issue 1896 by joenee...@gmail.com: lost instrument names
http://code.google.com/p/lilypond/issues/detail?id=1896
Sorry, it didn't show up in my regtests for some reason. Maybe moved grobs
trigger the test, but disappear
Updates:
Labels: -Patch-review Patch-push
Comment #7 on issue 1868 by colinpkc...@gmail.com: Loglevels in our python
scripts (lilypond-book, musicxml2ly, convert-ly)
http://code.google.com/p/lilypond/issues/detail?id=1868
Counted down to 20110918
On Mon, Sep 19, 2011 at 04:10:05PM +0200, m...@apollinemike.com wrote:
> On Sep 19, 2011, at 4:04 PM, Neil Puttock wrote:
>
> > On 19 September 2011 13:05, m...@apollinemike.com
> > wrote:
> >
> >> Perhaps create two new make options:
> >>
> >> make unsafe-test-baseline
> >>
> >> and
> >>
>
Updates:
Labels: Patch-needs_work
Comment #3 on issue 1905 by percival.music.ca: Add note to CG
9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh
or configure
http://code.google.com/p/lilypond/issues/detail?id=1905
probably. Also, Mike uploaded another pat
"m...@apollinemike.com" writes:
> On Sep 19, 2011, at 5:22 PM, Neil Puttock wrote:
>
>> On 19 September 2011 16:16, David Kastrup wrote:
>>
>>> The debug symbols should not affect code speed, and they are present in
>>> the unoptimized build, anyway, unless you are talking about something
>>> c
On Sep 19, 2011, at 5:22 PM, Neil Puttock wrote:
> On 19 September 2011 16:16, David Kastrup wrote:
>
>> The debug symbols should not affect code speed, and they are present in
>> the unoptimized build, anyway, unless you are talking about something
>> completely different from what I think you
On 19 September 2011 16:16, David Kastrup wrote:
> The debug symbols should not affect code speed, and they are present in
> the unoptimized build, anyway, unless you are talking about something
> completely different from what I think you do. I find it disturbing,
> however, that our default bu
Neil Puttock writes:
> On 19 September 2011 15:10, m...@apollinemike.com
> wrote:
>
>> Also, it may be worth it to consider scrapping optimized binary
>> altogether - it'd be good to test how much overhead the unoptimized
>> version introduces with respect to the optimized version.
>
> Eek, you
Comment #15 on issue 1248 by philehol...@googlemail.com: GUB produces a
random "unbound open-file" in regtests
http://code.google.com/p/lilypond/issues/detail?id=1248
Ooh. Just checking. What you're saying is that safe.ly will always
produce the same log output from now on, so we _won't_
On 19 September 2011 15:10, m...@apollinemike.com wrote:
> Also, it may be worth it to consider scrapping optimized binary altogether -
> it'd be good to test how much overhead the unoptimized version introduces
> with respect to the optimized version.
Eek, you don't want to do that. The unop
On Sep 19, 2011, at 4:04 PM, Neil Puttock wrote:
> On 19 September 2011 13:05, m...@apollinemike.com
> wrote:
>
>> Perhaps create two new make options:
>>
>> make unsafe-test-baseline
>>
>> and
>>
>> make unsafe-check
>>
>> These would not have the fail-if-unoptimized check.
>> Then, one wo
Comment #5 on issue 1598 by n.putt...@gmail.com: Dynamics staff on lower
piano staff shifts PianoStaff name
http://code.google.com/p/lilypond/issues/detail?id=1598
Joe, do you have a fix for the regression this introduces? If not, I think
we should revert the patch as soon as possible.
On 19 September 2011 13:05, m...@apollinemike.com wrote:
> Perhaps create two new make options:
>
> make unsafe-test-baseline
>
> and
>
> make unsafe-check
>
> These would not have the fail-if-unoptimized check.
> Then, one would need to make a change to GUB such that, when it runs the
> regtest
Updates:
Status: Verified
Comment #14 on issue 1248 by philehol...@googlemail.com: GUB produces a
random "unbound open-file" in regtests
http://code.google.com/p/lilypond/issues/detail?id=1248
OK. I'm going to update the CG section 8.3 with this information and also
about test-outp
On Sep 19, 2011, at 2:01 PM, lilyp...@googlecode.com wrote:
>
> Comment #2 on issue 1905 by n.putt...@gmail.com: Add note to CG 9.3
> 'Compiling reg tests' to add --disable-optimising when using autogen.sh or
> configure
> http://code.google.com/p/lilypond/issues/detail?id=1905
>
> Won't your
Comment #2 on issue 1905 by n.putt...@gmail.com: Add note to CG
9.3 'Compiling reg tests' to add --disable-optimising when using autogen.sh
or configure
http://code.google.com/p/lilypond/issues/detail?id=1905
Won't your patch break GUB builds?
_
Comment #1 on issue 1905 by mts...@gmail.com: Add note to CG 9.3 'Compiling
reg tests' to add --disable-optimising when using autogen.sh or configure
http://code.google.com/p/lilypond/issues/detail?id=1905
I knew and I still messed it up because I forgot to optimize my binary for
regtest ch
Updates:
Status: Fixed
Labels: fixed_2_15_11
Comment #13 on issue 1248 by reinhold...@gmail.com: GUB produces a
random "unbound open-file" in regtests
http://code.google.com/p/lilypond/issues/detail?id=1248
The safe.ly regtest really causes that output (try to run it manually!
Updates:
Status: Fixed
Labels: fixed_2_15_12
Comment #2 on issue 1888 by reinhold...@gmail.com: Introduce a maximum
depth for markup evaluation
http://code.google.com/p/lilypond/issues/detail?id=1888
Pushed as 16e626a8524421eda692cb19be6d0ec5bff723b7
Updates:
Status: Fixed
Labels: fixed_2_15_12
Comment #23 on issue 380 by reinhold...@gmail.com: Try to auto-detect
cyclic references in header fields (was 'cycling markup reference
segfaults')
http://code.google.com/p/lilypond/issues/detail?id=380
Fixed with commits
e2ebf578
Status: Accepted
Owner:
Labels: Type-Documentation
New issue 1905 by pkx1...@gmail.com: Add note to CG 9.3 'Compiling reg
tests' to add --disable-optimising when using autogen.sh or configure
http://code.google.com/p/lilypond/issues/detail?id=1905
Piers Titus van der Torren piersti...@gm
Updates:
Labels: -fixed_2_15_13 -font fixed_2_15_12
Comment #4 on issue 1883 by bordage@gmail.com: change longas similarly
to how breves were changed
http://code.google.com/p/lilypond/issues/detail?id=1883
Graham reverted the release, so this is fixed_2_15_12.
__
Updates:
Labels: -fixed_2_15_13 fixed_2_15_12
Comment #4 on issue 1887 by bordage@gmail.com: Doc: adding doc strings
for \...DashPattern and \harmonicBy...
http://code.google.com/p/lilypond/issues/detail?id=1887
Graham reverted the release, so this is fixed_2_15_12.
Updates:
Labels: fixed_2_15_12
Comment #8 on issue 1822 by bordage@gmail.com: New short and long lyric
ties.
http://code.google.com/p/lilypond/issues/detail?id=1822
(No comment was entered for this change.)
___
bug-lilypond mailing lis
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_12
Comment #11 on issue 1854 by bordage@gmail.com: Add some polyphonically
directed grobs
http://code.google.com/p/lilypond/issues/detail?id=1854
Pushed as f9251331576c94fa6aa4b85776917d3774b13b63
__
Updates:
Status: Fixed
Labels: -Patch-review
Comment #7 on issue 1822 by bordage@gmail.com: New short and long lyric
ties.
http://code.google.com/p/lilypond/issues/detail?id=1822
Pushed as 2fff263f10fd542454455994aea5ff3bbe075c7d
_
28 matches
Mail list logo
