Re: Retrieving information about breaks

[David Kastrup]

Urs Liska <address@hidden> writes:

> Am 23.01.2015 um 18:27 schrieb David Kastrup:
>> Urs Liska <address@hidden> writes:
>>
>>> Am 23.01.2015 um 18:17 schrieb Urs Liska:
>>>> Hi David,
>>>>
>>>> thanks, that works great.
>>>> It did *not* write to a file, but that's not the issue here.
>>>> The main point is that it listens to implicit break events.
>>>>
>>>> Probably the page breaks are even irrelevant for my case: finding a
>>>> way to recompile individual systems.
>>>>
>>>> what it doesn't do yet is handle mid-measure breaks, but I know
>>>> where I can look that up ;-)
>>>>
>>>> So this isn't a feature request anymore ...
>>> Ha, just one nitpick: you can remove the (eq? #t here:
>>>
>>>     (if (and (grob::has-interface grob 'paper-column-interface)
>>>              (ly:grob-property grob 'non-musical))
>> Unlikely.  Unless you add a fourth argument #f to the ly:grob-property
>> call.  The default fallback '() evaluates as true.
>>
>
> But when
>
> (ly:grob-property grob 'non-musical)
>
> evaluates to #t then

This is about the case where

(ly:grob-property grob 'non-musical) evaluates to '().

> (eq? #t (ly:grob-property grob 'non-musical))
>
> also evaluates to #t.
> Or did I miss anything?

The default case of '().

-- 
David Kastrup