Updates:
Summary: automatic negative offset for instrument name positioning
Status: Accepted
Mergedinto: -766
Comment #3 on issue 1093 by n.puttock: automatic negative offset for
instrument name positioning
http://code.google.com/p/lilypond/issues/detail?id=1093
#766 i
Updates:
Labels: Patch
Comment #3 on issue 1249 by ianhuli...@gmail.com: Avoid compilation errors
using Guile V2 during initialization - Part 1 ly-syntax-constructors.scm
http://code.google.com/p/lilypond/issues/detail?id=1249
Patch for review on Rietveld
http://codereview.appspot.com
Updates:
Summary: Avoid compilation errors using Guile V2 during initialization -
Part 1 ly-syntax-constructors.scm
Status: Started
Comment #2 on issue 1249 by ianhuli...@gmail.com: Avoid compilation errors
using Guile V2 during initialization - Part 1 ly-syntax-constructors.scm
ht
Updates:
Summary: Some modules now integrated into Guile V2 Base code - Part 1
Comment #1 on issue 1249 by ianhuli...@gmail.com: Some modules now
integrated into Guile V2 Base code - Part 1
http://code.google.com/p/lilypond/issues/detail?id=1249
The problem code in ly-syntax-construct
"James Lowe" wrote in message
news:ee5ed9503d57144e895fa3d7533e9fd302408...@mail2...
Hello,
-Original Message-
From: bug-lilypond-bounces+james.lowe=datacore@gnu.org on behalf of Phil
Holmes
Sent: Sun 03/10/2010 10:57
To: bug-lilypond@gnu.org
Subject: Re: Lilypond crash
I've at
Comment #3 on issue 1280 by n.puttock: \displayMusic does not properly
quote cons lilypond properties
http://code.google.com/p/lilypond/issues/detail?id=1280
No idea whether this is what was intended, though.
The display code deliberately produces this verbose scheme code: it's a
safety
Hello,
-Original Message-
From: bug-lilypond-bounces+james.lowe=datacore@gnu.org on behalf of Phil
Holmes
Sent: Sun 03/10/2010 10:57
To: bug-lilypond@gnu.org
Subject: Re: Lilypond crash
I've attached a graph of how both use working set memory - it does appear to
be related to try
Updates:
Status: Started
Owner: n.puttock
Labels: Patch
Comment #1 on issue 888 by n.puttock: Enhancement: ly:stencil-scale
http://code.google.com/p/lilypond/issues/detail?id=888
Patch: http://codereview.appspot.com/2275042/
_
Comment #1 on issue 1276 by n.puttock: MetronomeMark 'break-align-symbols
should work with all objects
http://code.google.com/p/lilypond/issues/detail?id=1276
One further note: '(staff-bar) doesn't work since it's reserved in the
engraver for full-bar rests; any acknowledged barline is alr
On Sun, Oct 3, 2010 at 6:15 PM, David Kastrup wrote:
> There is more than one issue. When I post a different description, it
> is likely a different issue.
>
> Should bugs in the current git version (not yet released) be raised only
> on lilypond-devel? If you say that you can't register a bug f
"Phil Holmes" writes:
> "David Kastrup" wrote in message
> news:8762xjcltg@lola.goethe.zz...
>>
>> What is wrong with the above?
>
> Nothing. It's just that it's one of many you've posted, and I wanted
> to know which you felt best illustrated the issue.
There is more than one issue. When
Status: Accepted
Owner:
Labels: Type-Scripts Priority-Critical Maintainability
New issue 1288 by percival.music.ca: convert-ly too greedy
http://code.google.com/p/lilypond/issues/detail?id=1288
convert-ly on the docs does things like:
-...@funindex \RemoveEmptyStaffContext
+...@funindex \S
Comment #15 on issue 1055 by hanwenn: guile 2.0
http://code.google.com/p/lilypond/issues/detail?id=1055
For GUILE 1.9 you may want to decide to just retire the SMOB should be dead
warnings. There is a (gc) call after processing a file which should clean
up all data related to a file, but
"David Kastrup" wrote in message
news:8762xjcltg@lola.goethe.zz...
"Phil Holmes" writes:
David,
It would seem that there are a number of spacing issues with 2.13.35
and as a result I opened
http://code.google.com/p/lilypond/issues/detail?id=1285. Joe has
responded to that to say that he
Comment #14 on issue 1055 by hanwenn: guile 2.0
http://code.google.com/p/lilypond/issues/detail?id=1055
regarding the crashes and --verbose: this is a symptom of GC related bugs
alright: --verbose changes the GUILE evaluator, and memory allocation
patterns. It can certainly influence when ga
"Phil Holmes" writes:
> "David Kastrup" wrote in message
> news:87mxqvcsvr@lola.goethe.zz...
>>
>> Check the output of the following:
>>
>> test = { c-1-^ r f-2-^ r c-3-^ r f-4-^ r c-1-^ r f-2-^ r c-3-^ r }
>> \score {
>> \repeat unfold 8 { \test \test r
>> \transpose c c''' \test \transp
"David Kastrup" wrote in message
news:87mxqvcsvr@lola.goethe.zz...
Check the output of the following:
test = { c-1-^ r f-2-^ r c-3-^ r f-4-^ r c-1-^ r f-2-^ r c-3-^ r }
\score {
\repeat unfold 8 { \test \test r
\transpose c c''' \test \transpose c c''' \test r }
\layout { ragged-bottom
Compiles here with LilyPond 2.13.35 on Linux (4G physical memory).
Compile time is 3'22, memory usage goes up to 1204,5 M.
Thomas
Original-Nachricht
Exploring the question of whether "random" music stresses Lilypond more than
repeated same code, I tried this:
\repeat unfol
Check the output of the following:
test = { c-1-^ r f-2-^ r c-3-^ r f-4-^ r c-1-^ r f-2-^ r c-3-^ r }
\score {
\repeat unfold 8 { \test \test r
\transpose c c''' \test \transpose c c''' \test r }
\layout { ragged-bottom = ##t }
}
It is clear that on the first page, the \layout parameter rag
"Graham Percival" wrote in message
news:20101002172122.ga22...@futoi...
On Sat, Oct 02, 2010 at 06:02:19PM +0100, Phil Holmes wrote:
On my Windows machine, Lilypond stops working at the "Preprocessing
graphical objects" stage. Might be an oddity of my PC and how I run
Lilypond, but don't recko
2010/10/2 Phil Holmes :
> Exploring the question of whether "random" music stresses Lilypond more than
> repeated same code, I tried this:
>
> \repeat unfold 2400 {
> c''4 c' c c,
> }
>
> On my Windows machine, Lilypond stops working at the "Preprocessing
> graphical objects" stage. Might be an o
21 matches
Mail list logo
