Nicolas Sceaux wrote:
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
Would you register with google so I can add you as a project member?
It says I need an invitation code, or use a portable phone in New
Zealand or Philippines to get one...
I guess this is the gmail thing. I sent you an invi
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> It would be nice if you also updated the issue at
>
> http://code.google.com/p/lilypond/issues/detail?id=147&can=2&q=
>
> Would you register with google so I can add you as a project member?
It says I need an invitation code, or use a portable phon
Nicolas Sceaux escreveu:
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
Hello Nicolas,
the display-lily.scm module retains references to the parser, and
objects created in the parser across processed files. This is bad
practice, and makes tracing memory leaks across files hard.
Can this be chan
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> Hello Nicolas,
>
> the display-lily.scm module retains references to the parser, and
> objects created in the parser across processed files. This is bad
> practice, and makes tracing memory leaks across files hard.
>
> Can this be changed? The parser
Han-Wen Nienhuys <[EMAIL PROTECTED]> writes:
> Hello Nicolas,
>
> the display-lily.scm module retains references to the parser, and
> objects created in the parser across processed files. This is bad
> practice, and makes tracing memory leaks across files hard.
>
> Can this be changed? The parser
Hello Nicolas,
the display-lily.scm module retains references to the parser, and
objects created in the parser across processed files. This is bad
practice, and makes tracing memory leaks across files hard.
Can this be changed? The parser argument is passed in the music
function, and all s
