Re: Extent boundaries inconsistent w.r.t. extent properties
Darryl Okahata wrote:
What you probably want is the glyph visibility to be dependent
upon
the "openness" of the extent endpoints. If the extent's
"start-open"
property is non-nil, then the glyph is displayed even if the extent is
invisible; if "start-open" is nil (the extent is closed), then the glyph
is not displayed. Similarly for the endpoint.
Comments?
This won't work for me. My extents all need to be start-open & end-closed in
order to make sure that every keystroke gets inserted into exactly one extent
(my extents run end-to-end across the buffer).
I need to be able to create begin-glyphs for extents despite the fact that my
input model defaults to having characters inserted to the left. In my case,
it would be better for begin-glyphs and end-glyphs to just inherit their
display properties from the extent they are attached to.
Michael