Comment #14 on issue 2024 by d...@gnu.org: Patch: Let #{ ... #} pass its $
handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024
@Reinhold: had a change of mind: I don't want to disturb this countdown,
and the syntax when changing those 5 commands (actually
Updates:
Labels: -Patch-countdown Patch-push
Comment #25 on issue 1986 by colinpkc...@gmail.com: Patch: Fixes slope
errors from incorrect X extents in Beam::print.
http://code.google.com/p/lilypond/issues/detail?id=1986
Counted down to 2008
Updates:
Labels: -Patch-countdown Patch-push
Comment #3 on issue 2017 by colinpkc...@gmail.com: Patch: Correct forward
declarations (struct vs. class)
http://code.google.com/p/lilypond/issues/detail?id=2017
Countred down to 2008
Updates:
Labels: -Patch-countdown Patch-push
Comment #4 on issue 2019 by colinpkc...@gmail.com: Patch: Caches pure
translations for full score.
http://code.google.com/p/lilypond/issues/detail?id=2019
counted down to 2008
___
bug
Updates:
Labels: -Patch-countdown Patch-push
Comment #3 on issue 2023 by colinpkc...@gmail.com: Patch: Makes
line-breaking possibilities more available to grobs
http://code.google.com/p/lilypond/issues/detail?id=2023
counted down to 2008
Comment #1 on issue 2031 by carl.d.s...@gmail.com: no lilydev available
http://code.google.com/p/lilypond/issues/detail?id=2031
That image is available for web-browser download. I have downloaded it,
and it is now available at
http://www.et.byu.edu/~sorensen/ubuntu-lilydev-remix-1.1.iso
I
Comment #29 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
OK, so you got the new regtests
# input/regression/beamlet-point-toward-beat.ly
# input/regression/beamlet-test.ly
Why they didn't
Updates:
Labels: -Patch-new Patch-review
Comment #7 on issue 2018 by pkx1...@gmail.com: Patch: parser.yy: allow
postevents in function arguments in general
http://code.google.com/p/lilypond/issues/detail?id=2018
Passes make and no reg test diffs.
James
_
Comment #12 on issue 2024 by d...@gnu.org: Patch: Let #{ ... #} pass its $
handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024
Uh, the # syntax is not old, it is different in meaning (namely
auto-exporting). I should definitely hope that display-lily-music
Comment #11 on issue 2024 by reinhold...@gmail.com: Patch: Let #{ ... #}
pass its $ handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024
Hmm, most of the diffs is just due to different snippet hashes, which
should actually not count as a diff any more (app
Comment #28 on issue 11 by pkx1...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Carl,
I went back and reapplied the patch:
--snip--
lowe@jlowe-lilybuntu2:~/lilypond-git$ git status
# On branch master
# Changed but not updated:
Hello,
On Tue, Nov 8, 2011 at 10:20 PM, wrote:
> Updates:
> Blockedon: -2001
>
> Comment #6 on issue 2018 by d...@gnu.org: Patch: parser.yy: allow postevents
> in function arguments in general
> http://code.google.com/p/lilypond/issues/detail?id=2018
>
> Issue 2001 went to dev/staging, th
Issue 2001: Patch: Patch series (available at branch dev/syntax) for more
argument list power.
http://code.google.com/p/lilypond/issues/detail?id=2001
This issue is no longer blocking issue 2018.
See http://code.google.com/p/lilypond/issues/detail?id=2018
--
You received this message because yo
Updates:
Blockedon: -2001
Comment #6 on issue 2018 by d...@gnu.org: Patch: parser.yy: allow
postevents in function arguments in general
http://code.google.com/p/lilypond/issues/detail?id=2018
Issue 2001 went to dev/staging, this patch should be reviewable against it
(and hopefully s
Comment #5 on issue 2018 by d...@gnu.org: Patch: parser.yy: allow
postevents in function arguments in general
http://code.google.com/p/lilypond/issues/detail?id=2018#c5
parser.yy: allow postevents in function arguments in general
This change is on top of the dev/syntax branch still in review
Updates:
Status: Fixed
Labels: -Patch-countdown Fixed_2_15_17
Comment #12 on issue 2001 by d...@gnu.org: Patch: Patch series (available
at branch dev/syntax) for more argument list power.
http://code.google.com/p/lilypond/issues/detail?id=2001
Been on countdown almost for two
Updates:
Labels: -Patch-new Patch-review
Comment #10 on issue 2024 by pkx1...@gmail.com: Patch: Let #{ ... #} pass
its $ handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024
Thanks everyone, I changed VERSION and it passed make, there no pictoral
r
Comment #9 on issue 2024 by d...@gnu.org: Patch: Let #{ ... #} pass its $
handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024#c9
Issue 2024: Let #{ ... #} pass its $ handling to environment cloning
Consists of the patches:
Adapt docs to new $ and #{ ... #
Comment #2 on issue 2029 by pkx1...@gmail.com: Patch: Adds some info about
pure properties to the CG.
http://code.google.com/p/lilypond/issues/detail?id=2029
Mike,
attached is a git formatted patch that passes make. I've not yet done a
full make doc.
james
PS you can edit the commit inf
Comment #8 on issue 2024 by d...@gnu.org: Patch: Let #{ ... #} pass its $
handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024
For testing, James, edit VERSION and set PATCHLEVEL to 18. I was half of a
mind to do this in the Rietveld issue myself, but dec
Updates:
Status: Started
Labels: -Patch-new Patch-needs_work
Comment #1 on issue 2029 by pkx1...@gmail.com: Patch: Adds some info about
pure properties to the CG.
http://code.google.com/p/lilypond/issues/detail?id=2029
Mike a few texi formatting problems here now I look.
I'll
Updates:
Labels: -Patch-needs_work Patch-new
Comment #7 on issue 2024 by gra...@percival-music.ca: Patch: Let #{ ... #}
pass its $ handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024
as the message says, it's the version number.
Hold on a bit, I'll
Status: Accepted
Owner:
Labels: Type-Critical
New issue 2031 by gra...@percival-music.ca: no lilydev available
http://code.google.com/p/lilypond/issues/detail?id=2031
the link to lilydev in the CG is wrong, and we're not certain about
files.lilynet.net
We can find alternate hosting, but
Updates:
Status: Started
Labels: -Patch-new Patch-needs_work
Comment #6 on issue 2024 by pkx1...@gmail.com: Patch: Let #{ ... #} pass
its $ handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024
This didn't pass 'make'. Not sure if it is JUST t
Comment #27 on issue 11 by carl.d.s...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
This regtest difference is intentional.
There should also be two new regtests, I believe. Are they not included?
Thanks for all you do, James!
Updates:
Labels: -Patch-new Patch-review
Comment #18 on issue 2000 by pkx1...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000
Passes Make, all reg test diffs here:
http://lilypond-stuff.1065243.n5.nabble.com/Tracker-is
Updates:
Labels: -Patch-new Patch-review
Comment #4 on issue 2025 by pkx1...@gmail.com: Make safe utility available
via new (scm safe-utility-defs) scheme module.
http://code.google.com/p/lilypond/issues/detail?id=2025
Passes make and no reg test diffs
James
___
Updates:
Labels: -Patch-new Patch-review
Comment #26 on issue 11 by pkx1...@gmail.com: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
Passes Make and one reg test diff attached,
james
Attachments:
Screenshot.png 72.7 KB
___
Hi Graham,
On 08/11/11 18:20, lilyp...@googlecode.com wrote:
>
> Comment #5 on issue 2024 by gra...@percival-music.ca: Patch: Let #{ ...
> #} pass its $ handling to environment cloning
> http://code.google.com/p/lilypond/issues/detail?id=2024
>
> sigh. ok, I'll reformat my computer and stick 10.
Comment #5 on issue 2024 by gra...@percival-music.ca: Patch: Let #{ ... #}
pass its $ handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024
sigh. ok, I'll reformat my computer and stick 10.04 back on it so we can
have a release. I'll try to do my benchmar
Comment #4 on issue 1392 by carl.d.s...@gmail.com: Internals Reference
should document \paper variables
http://code.google.com/p/lilypond/issues/detail?id=1392
The internals reference is completely auto-generated from the code. If we
want to add paper variables to the IR, we need to develo
On Tue, 8 Nov 2011 16:26:13 -
"Phil Holmes" wrote:
> Using Windows and any version 2.14 and 2.15.15 I don't get a crash.
> Which OS are you using, please?
Fedora 16 x86_64.
c++ (GCC) 4.6.2 20111027 (Red Hat 4.6.2-1)
2.14 and 2.14.1 should not be affected. The breakage was committed
between
"Pavel Roskin" wrote in message
news:2007182705.36e40645@mj...
Hello!
Lilypond 2.14.2 and the current revision from stable/2.14 crash on this
file:
\version "2.14.2"
\score {
\new PianoStaff <<
\new Staff = "right" { \change Staff="left" }
\new Staff = "left" { s1 }
>>
\layout { }
Status: Accepted
Owner:
Labels: Type-Crash
New issue 2030 by pkx1...@gmail.com: 2.14.2, dynamic cast crash introduced
in commit 6f6369c0
http://code.google.com/p/lilypond/issues/detail?id=2030
Hello!
Lilypond 2.14.2 and the current revision from stable/2.14 crash on this
file:
\version
Hello,
On Mon, Nov 7, 2011 at 11:27 PM, Pavel Roskin wrote:
> Hello!
>
> Lilypond 2.14.2 and the current revision from stable/2.14 crash on this
> file:
Added as http://code.google.com/p/lilypond/issues/detail?id=2030
--
--
James
___
bug-lil
Comment #17 on issue 2000 by mts...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000#c17
Fixes NoteColumn vs SpanBar collisions.
http://codereview.appspot.com/5323062
___
bug-lilypo
On Nov 8, 2011, at 8:00 AM, Trevor Daniels wrote:
>
>> New issue 2029 by mts...@gmail.com: Patch: Adds some info about pure
>> properties to the CG.
>> http://code.google.com/p/lilypond/issues/detail?id=2029
>>
>> Adds some info about pure properties to the CG.
>>
>> http://codereview.appspot.c
New issue 2029 by mts...@gmail.com: Patch: Adds some info about
pure
properties to the CG.
http://code.google.com/p/lilypond/issues/detail?id=2029
Adds some info about pure properties to the CG.
http://codereview.appspot.com/5364048
Mike
Did you upload the right patch? I don't see anythin
Comment #4 on issue 2024 by d...@gnu.org: Patch: Let #{ ... #} pass its $
handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024
I am rather serious about this. The last upload removes all uses of
ly:export _via_ convertrules. Automatically, even though th
Updates:
Labels: Patch-new
Comment #16 on issue 2000 by mts...@gmail.com: Patch: Fixes NoteColumn vs
SpanBar collisions.
http://code.google.com/p/lilypond/issues/detail?id=2000#c16
Adds some info about pure properties to the CG.
http://codereview.appspot.com/5364048
___
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2029 by mts...@gmail.com: Patch: Adds some info about pure
properties to the CG.
http://code.google.com/p/lilypond/issues/detail?id=2029
Adds some info about pure properties to the CG.
http://codereview.appspot.com/5364048
Comment #3 on issue 2024 by d...@gnu.org: Patch: Let #{ ... #} pass its $
handling to environment cloning
http://code.google.com/p/lilypond/issues/detail?id=2024#c3
Issue 2024: Let #{ ... #} pass its $ handling to environment cloning
Consists of the patches:
Adapt docs to new $ and #{ ... #
Hi David
On 08/11/11 08:45, David Kastrup wrote:
> Ian Hulin writes:
>
>> o Move all the markup macros and markup definition procedures to a new
>> (scm markup-facility-defs) module (this is the artist formerly known
>> markup-macros.scm and the remaining code in markup.scm)
>>- add (use-
Updates:
Labels: Patch-new
Comment #3 on issue 2025 by ianhuli...@gmail.com: Make safe utility
available via new (scm safe-utility-defs) scheme module.
http://code.google.com/p/lilypond/issues/detail?id=2025
Patch available on Rietveld http://codereview.appspot.com/5339050/
Ian Hulin writes:
> o Move all the markup macros and markup definition procedures to a new
> (scm markup-facility-defs) module (this is the artist formerly known
> markup-macros.scm and the remaining code in markup.scm)
>- add (use-modules (scm markup-facility-defs)) to all the scheme
>
45 matches
Mail list logo
