Erlend Aasland wrote:
It seems that there is a serious bug in the Lilypond 2.6.4 parser, as most
files I try to typeset results in numerous errors.
For example the following small snippet, which is typeset correctly without
errors in 2.6.3 (and even 2.7.11), generates the following errors:
GNU
Erlend Aasland wrote:
I'm running Lilypond 2.6.4-1, installed from the MacOSX disk image.
which MacOS version?
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.
On 10/12/05, Erlend Aasland <[EMAIL PROTECTED]> wrote:
>
> On 10/12/05, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
> >
> > Erlend Aasland wrote:
> > > The snippet is: \relative { a->\< b->\mf\> c->\! d-> }
> >
> > Can't duplicate.
>
>
> Ok, even this simple snippet (\relative { a b c d }) does not
On 10/12/05, Han-Wen Nienhuys <[EMAIL PROTECTED]> wrote:
>
> Erlend Aasland wrote:
> > The snippet is: \relative { a->\< b->\mf\> c->\! d-> }
>
> Can't duplicate.
Ok, even this simple snippet (\relative { a b c d }) does not generate
correct output (only a blank page with the standard footer). I'
Hi,
It seems that the 'if-no-beam variable no longer does
what it's supposed to in 2.7.12. It never detects
beams and always adds a bracket. Running the
following in 2.6.3 and 2.7.12 should highlight the
problem:
\score {
\new Staff
\relative c' {
\override TupletBracket
#'bracket-vi
Erlend Aasland wrote:
It seems that there is a serious bug in the Lilypond 2.6.4 parser, as most
files I try to typeset results in numerous errors.
For example the following small snippet, which is typeset correctly without
errors in 2.6.3 (and even 2.7.11), generates the following errors:
er
Ed Baskerville wrote:
In the 2.6.4-1 release for Mac OS X, the bundle identifier
(CFBundleIdentifier key) in LilyPond's Info.plist is still
org.pythonmac.unspecified.LilyPond. There's a misspelled key
"CFBundleIndentifier" that *is* org.lilypond.lilypond--looks like a
typo happened at some
It seems that there is a serious bug in the Lilypond 2.6.4 parser, as most
files I try to typeset results in numerous errors.
For example the following small snippet, which is typeset correctly without
errors in 2.6.3 (and even 2.7.11), generates the following errors:
GNU LilyPond 2.6.4
Processing
On Tuesday 11 October 2005 18.48, Nicolas Sceaux wrote:
> Erik Sandberg <[EMAIL PROTECTED]> writes:
> > To me, those property lists look like major bottlenecks (though I
> > haven't done any real profiling). Especially the grob property alists:
> > While I was debugging some time ago, I saw that
>
Erik Sandberg <[EMAIL PROTECTED]> writes:
> To me, those property lists look like major bottlenecks (though I
> haven't done any real profiling). Especially the grob property alists:
> While I was debugging some time ago, I saw that
> Grob::internal_set_property was called over 1000 times in a tri
In the 2.6.4-1 release for Mac OS X, the bundle identifier
(CFBundleIdentifier key) in LilyPond's Info.plist is still
org.pythonmac.unspecified.LilyPond. There's a misspelled key
"CFBundleIndentifier" that *is* org.lilypond.lilypond--looks like a
typo happened at some point.
--Ed
smime.p
On 11/10/05, Mats Bengtsson <[EMAIL PROTECTED]> wrote:
>
> The question from [EMAIL PROTECTED] provided a nice example
> of a LilyPond problem, namely that the page breaking and system
> spacing on one page seem to be affected by what happened on earlier
> pages.
>
> In the following example, you w
Han-Wen Nienhuys wrote:
Mats Bengtsson wrote:
The question from [EMAIL PROTECTED] provided a nice example
of a LilyPond problem, namely that the page breaking and system
spacing on one page seem to be affected by what happened on earlier
pages.
page breaking, like line-breaking, is done b
Mats Bengtsson wrote:
The question from [EMAIL PROTECTED] provided a nice example
of a LilyPond problem, namely that the page breaking and system
spacing on one page seem to be affected by what happened on earlier
pages.
page breaking, like line-breaking, is done by looking for a globally
opti
It's probably best not guessing what is efficient and not, but making
some profiling in typical user situations. The thing is that a part
might be slow, but if it is not used much, it is just a waste of
programmer time to speed it up.
Hans Aberg
___
The question from [EMAIL PROTECTED] provided a nice example
of a LilyPond problem, namely that the page breaking and system
spacing on one page seem to be affected by what happened on earlier
pages.
In the following example, you would expect the output to contain 4
equal pages, but what happens i
On Monday 10 October 2005 18.17, Han-Wen Nienhuys wrote:
> Wiz Aus wrote:
> > Even if it did use pre-compiled scheme, because lilypond supports
> > compiling scores that contain Scheme code, it would still require
> > effectively interpretive processing, which is not doubt a large reason
> > for it
Erik Sandberg wrote:
To me, those property lists look like major bottlenecks (though I haven't done
any real profiling). Especially the grob property alists: While I was
debugging some time ago, I saw that Grob::internal_set_property was called
over 1000 times in a trivial score.
How would it
18 matches
Mail list logo
