Re: address@hidden: Overlay string not displayed on text with `display' property]

[Kim F. Storm]

address@hidden (Kim F. Storm) writes:

> Richard Stallman <address@hidden> writes:
>
>> Would you please DTRT and ack?
>
> I have tried to find a simple way to fix this (assuming it is a bug),
> but it is non-trivial to fix.
>
> OTOH, it may not be a bug at all -- if we accept that overlays at invisible
> buffer positions (e.g. if replaced by a display string), are ignored.

Thinking more about the implications of mixing overlay properties and
display string properties at the same buffer position, I've mostly
convinced myself that the current behaviour is ok, i.e. that we _must_
ignore overlays at buffer positions "hidden by" a display string.

IMO, the semantics of mixing overlays and display strings (that may
also have properties) is too unclear to be of any real use -- and a
big headache to get right.

There may be _some_ overlay properties where it could make sense,
e.g. before-string and after-string, but doing a lot of work just to
make those work is not worth the trouble IMO.  So I think we should
simply document the current behaviour.

-- 
Kim F. Storm <address@hidden> http://www.cua.dk