Saul Tobin writes:
> ly:context-property-where-defined returns differently depending on if
> a property is unset or explicitly set to '() – I'm guessing this is
> one of the things you had in mind by "not really pretty"?
I think one of the uglier things is that ly:context-property can be
given a
ly:context-property-where-defined returns differently depending on if a
property is unset or explicitly set to '() – I'm guessing this is one of
the things you had in mind by "not really pretty"?
On Sat, Jan 4, 2025 at 5:18 PM David Kastrup wrote:
> Dan Eble writes:
>
> > Old-timers,
> >
> > Fo
Dan Eble writes:
> Old-timers,
>
> For some reason, I had it in my head that a context property could not
> be set to *unspecified*, but now that I have looked again, I see that
> that is false. It is possible to set a property to *unspecified* and
> mask the value from the enclosing context, ju
Old-timers,
For some reason, I had it in my head that a context property could not
be set to *unspecified*, but now that I have looked again, I see that
that is false. It is possible to set a property to *unspecified* and
mask the value from the enclosing context, just like setting any other
