Comment #12 on issue 1821 by tdaniels...@googlemail.com: GUB argument list
too long
http://code.google.com/p/lilypond/issues/detail?id=1821
The problem seems to be the value of MAX_ARG_STRLEN (131072) which limits
the length of each individual command line argument. The failing length
Comment #13 on issue 1821 by tdaniels...@googlemail.com: GUB argument list
too long
http://code.google.com/p/lilypond/issues/detail?id=1821
Another possibility, maybe for the short-term, would be to build using
shorter directory names or paths. These are repeated for every entry in
the
Comment #36 on issue 1663 by philehol...@googlemail.com: Images missing on
web site
http://code.google.com/p/lilypond/issues/detail?id=1663
Latest state is that I'm not working on this, pending delivery of a faster
PC to assist make doc. The other news is that web-big-page is in an even
Comment #7 on issue 720 by philehol...@googlemail.com: incorrect bbox
values for EPS images
http://code.google.com/p/lilypond/issues/detail?id=720
See also regression test system-extents.ly. This looks very much like the
slur has been cropped.
Attachments:
system-extents.png
Comment #4 on issue 1826 by ianhuli...@gmail.com: Guile 2.0 compat:
`conditional-circle-markup' definition needs to be relocated
http://code.google.com/p/lilypond/issues/detail?id=1826
Re comment 2:
Hi Reinhold,
Things are a bit more complicated in Guile V2.0, because now you can be
Comment #14 on issue 1821 by d...@gnu.org: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
Uh, does that mean we are using absolute paths? From my painful
experiences as a project manager, I can tell that this would be a terrible
idea. Not only do we
Comment #15 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
Judging from the logfile from comment 3:
http://lilypond.org/~graham/lilypond-test.log
it is indeed using absolute paths.
Note that the only people using GUB are
lilyp...@googlecode.com wrote in message
news:15-9567054385019064696-5785647612212700228-lilypond=googlecode@googlecode.com...
Comment #15 on issue 1821 by percival.music.ca: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
Judging from the logfile from
Comment #16 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
Ah, I see it's basically a problem of out-of-source builds (I'm always
using in-source builds, mainly for convenience). Each file needs to have
the full
Comment #17 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
For out-of-source builds, there is no way we can use relative pathes!
Inside the make file, the $^ needs to expand all pathes to absolute pathes,
since
Status: Accepted
Owner:
Labels: Type-Other
New issue 1853 by reinhold...@gmail.com: EPS backend adds small extra
padding on the right (~0.5-1 mm)
http://code.google.com/p/lilypond/issues/detail?id=1853
All snippets processed through lilypond-book set an explicit line-with
(with
Updates:
Status: Fixed
Labels: fixed_2_15_9
Comment #2 on issue 1847 by reinhold...@gmail.com: Lilypond-book: Get rid
of lilyquote option, use quote instead
http://code.google.com/p/lilypond/issues/detail?id=1847
Pushed as Graham said I should push without waiting for a
Updates:
Status: Fixed
Labels: fixed_2_15_9
Comment #14 on issue 1816 by reinhold...@gmail.com: Lilypond-book music
runs off right side of the page
http://code.google.com/p/lilypond/issues/detail?id=1816
Pushed as 93d4e8aa80360c95696e065b9fd4744f269f4ea8
Updates:
Status: Duplicate
Mergedinto: 1836
Comment #1 on issue 1853 by reinhold...@gmail.com: EPS backend adds small
extra padding on the right (~0.5-1 mm)
http://code.google.com/p/lilypond/issues/detail?id=1853
Oops, Graham told me to open a bug report for this. Apparently,
Comment #1 on issue 1836 by reinhold...@gmail.com: lilypond produces images
0.5-1mm too wide
http://code.google.com/p/lilypond/issues/detail?id=1836
Issue 1853 has been merged into this issue.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
Comment #2 on issue 1836 by reinhold...@gmail.com: lilypond produces images
0.5-1mm too wide
http://code.google.com/p/lilypond/issues/detail?id=1836
Example for this behavior is attached to bug 1853
___
bug-lilypond mailing list
Updates:
Status: Fixed
Labels: fixed_2_15_9
Comment #4 on issue 1644 by reinhold...@gmail.com: get_working_directory ()
issue?
http://code.google.com/p/lilypond/issues/detail?id=1644
Already fixed with commit
if the return value from getcwd is NULL then the getcwd failed and
Comment #5 on issue 1644 by reinhold...@gmail.com: get_working_directory ()
issue?
http://code.google.com/p/lilypond/issues/detail?id=1644
Oops, that should have been (middle-mouse-paste accicent...):
Already fixed with commit 638ad29c79717fc1ba895b14aee256dd3a03f25b
Updates:
Status: Fixed
Labels: -Patch-review fixed_2_15_9
Comment #3 on issue 905 by reinhold...@gmail.com: LilyPond should accept
UTF-8 BOM signatures even if preceded with other chars
http://code.google.com/p/lilypond/issues/detail?id=905
Pushed as commit
lilyp...@googlecode.com writes:
Comment #17 on issue 1821 by reinhold...@gmail.com: GUB argument list
too long
http://code.google.com/p/lilypond/issues/detail?id=1821
For out-of-source builds, there is no way we can use relative pathes!
I don't see why not.
After
Updates:
Status: Started
Owner: reinhold...@gmail.com
Labels: Patch-new
Comment #18 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
Patch is up for review at
Comment #19 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
It seems that Graham's commit 340d7b49e816a5930ae39e17212415f16c8d152d
makes lys-to-tely expect the filenames in --input-filenames=FILE to be one
per
Updates:
Status: Started
Owner: reinhold...@gmail.com
Labels: Patch-new
Comment #1 on issue 1825 by reinhold...@gmail.com: convert-ly produces no
output having run on up-to-date source
http://code.google.com/p/lilypond/issues/detail?id=1825
Patch is up at
Updates:
Labels: -Patch-new Patch-review
Comment #14 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, one reg test change - probably expected. Attached.
Attachments:
Updates:
Labels: -Patch-new Patch-needs_work
Comment #2 on issue 1825 by pkx1...@gmail.com: convert-ly produces no
output having run on up-to-date source
http://code.google.com/p/lilypond/issues/detail?id=1825
passes make and reg tests and I ran a make doc too (seemed relevant) and
Comment #3 on issue 1825 by pkx1...@gmail.com: convert-ly produces no
output having run on up-to-date source
http://code.google.com/p/lilypond/issues/detail?id=1825
Sorry forgot to attach file...here it is.
Attachments:
lily-63af708e.ly 1.1 KB
Updates:
Labels: -Patch-new Patch-needs_work
Comment #20 on issue 1821 by pkx1...@gmail.com: GUB argument list too long
http://code.google.com/p/lilypond/issues/detail?id=1821
(No comment was entered for this change.)
___
bug-lilypond
Status: Accepted
Owner: bordage@gmail.com
Labels: Type-Enhancement Patch-new
New issue 1854 by pkx1...@gmail.com: Add some polyphonically directed grobs
http://code.google.com/p/lilypond/issues/detail?id=1854
Accidental suggestions, dynamics, ligatures and spanned trills added to
Updates:
Labels: -Patch-new Patch-review
Comment #1 on issue 1854 by pkx1...@gmail.com: Add some polyphonically
directed grobs
http://code.google.com/p/lilypond/issues/detail?id=1854
Passes make but get two reg tests show up that look ok but that need a
second opinion.
Attached
Comment #2 on issue 1854 by reinhold...@gmail.com: Add some polyphonically
directed grobs
http://code.google.com/p/lilypond/issues/detail?id=1854
Both changes are desired: The first one in so far as there are now some
more grobs that get their direction set in \voiceOne, and the second
Updates:
Labels: -Patch-needs_work Patch-new
Comment #4 on issue 1825 by reinhold...@gmail.com: convert-ly produces no
output having run on up-to-date source
http://code.google.com/p/lilypond/issues/detail?id=1825
That is the regtest that David's commit yesterday broke (the one about
Comment #21 on issue 1821 by reinhold...@gmail.com: GUB argument list too
long
http://code.google.com/p/lilypond/issues/detail?id=1821
Yes, as I mentioned in comment 19, this needs a change to Graham's
--input-filenames feature in lys-to-tely.py. I didn't want to change it
before hearing
Status: Accepted
Owner: mts...@gmail.com
Labels: Type-Enhancement Patch-new
New issue 1855 by pkx1...@gmail.com: Prevents nested tuplets from colliding
http://code.google.com/p/lilypond/issues/detail?id=1855
http://codereview.appspot.com/4808082/
Updates:
Labels: -Patch-new Patch-review
Comment #5 on issue 1825 by pkx1...@gmail.com: convert-ly produces no
output having run on up-to-date source
http://code.google.com/p/lilypond/issues/detail?id=1825
Then passes make and reg tests. So I guess this can be set to review
Comment #5 on issue 1826 by ianhuli...@gmail.com: Guile 2.0 compat:
`conditional-circle-markup' definition needs to be relocated
http://code.google.com/p/lilypond/issues/detail?id=1826
Ooops, I meant it could go in its own define-woodwind-markup-macros.scm
in the last comment,
Ian
Updates:
Owner: bordage@gmail.com
Comment #6 on issue 1839 by bordage@gmail.com: Improves some parmesan
noteheads.
http://code.google.com/p/lilypond/issues/detail?id=1839
And another patch set.
The design has been enhanced and the longas and maximas of every ancient
style
Comment #3 on issue 1856 by percival.music.ca: lots of extra space at
beginning of bar
http://code.google.com/p/lilypond/issues/detail?id=1856
spanner-break-beyond-parent.ly
hairpin-barline-break.ly
instrument-name-hara-kiri.ly
dynamics-broken-hairpin.ly
page-break-turn-toplevel.ly
37 matches
Mail list logo
