Re: Extent boundaries inconsistent w.r.t. extent properties

Michael Toomim <toomim(a)cs.berkeley.edu&gt; 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. > >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 don't understand how this would not work for you. As your extents are start-open, begin-glyphs would always be visible, regardless of the extent visibility.