bug-lilypond
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 2026 (markup utility) should keep empty-markup positionless


From: James
Subject: Re: Issue 2026 (markup utility) should keep empty-markup positionless
Date: Fri, 3 Feb 2012 22:01:50 +0000

Hello,

On 3 February 2012 21:00, Marek Klein <address@hidden> wrote:
> Hello,
>
> 2012/2/1 Robin Bannister <address@hidden>
>
>> In 
>> http://code.google.com/p/**lilypond/issues/detail?id=**2026#c32<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 successfully and run reg-tests OK.
>>>
>>
>>
>> OK, the docs say \null markup is an "empty markup", merely a single point,
>> but it has _position_, which empty-markup does not.
>> The following snippet demonstrates this difference:
>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>> offset = \markup \translate #'(9 . 9) "offset"
>> \markup \line {  "concat with empty-markup:" \box \concat { \empty-markup
>> \offset }  " concat with null markup: "\box \concat { \null \offset }
>> }
>> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
>>
>
> Is this a bug report? I am not sure; 2026 is still open, is it not better
> to add a coment to the issue?

I think so, but to be honest only David or Ian can probably answer that.

I'd hold off from creating a new tracker for now.

-- 
--

James



reply via email to

[Prev in Thread] Current Thread [Next in Thread]