James pkx1...@gmail.com writes:
On 3 February 2012 21:00, Marek Klein ma...@gregoriana.sk wrote:
Hello,
2012/2/1 Robin Bannister r...@dataway.ch
In
http://code.google.com/p/**lilypond/issues/detail?id=**2026#c32http://code.google.com/p/lilypond/issues/detail?id=2026#c32Ian
Hulin wrote:
Hello,
2012/2/4 Robin Bannister r...@dataway.ch
is it not better to add a coment to the issue?
Perhaps that is the most suitable way of relaying this report. (IMO I
shouldn't need a Google account to report something like this.)
Thanks. I have added a new comment:
Hello,
2012/2/1 Robin Bannister r...@dataway.ch
In
http://code.google.com/p/**lilypond/issues/detail?id=**2026#c32http://code.google.com/p/lilypond/issues/detail?id=2026#c32Ian
Hulin wrote:
This is fixed if we move the definition of the \null markup to the before
the empty-markup
Hello,
On 3 February 2012 21:00, Marek Klein ma...@gregoriana.sk wrote:
Hello,
2012/2/1 Robin Bannister r...@dataway.ch
In
http://code.google.com/p/**lilypond/issues/detail?id=**2026#c32http://code.google.com/p/lilypond/issues/detail?id=2026#c32Ian
Hulin wrote:
This is fixed if we move
Marek Klein wrote:
Is this a bug report?
One view:
This is about a bug in the making, not yet available in an unstable version.
So CG says you should relay this to dev (to which I am not subscribed).
Another view:
Ian's empty-markup patch passed the reg tests.
This in itself is a
In http://code.google.com/p/lilypond/issues/detail?id=2026#c32
Ian Hulin wrote:
This is fixed if we move the definition of the \null markup to the
before the empty-markup declaration and change empty-markup to
(define-public (empty-markup)
make-null-markup))
...
It's built the docs
