From xemacs-m  Mon Jun  2 17:27:57 1997
Received: from crystal.WonderWorks.COM (crystal.WonderWorks.com [192.203.206.1])
	by xemacs.org (8.8.5/8.8.5) with ESMTP id RAA06134
	for <xemacs-beta@xemacs.org>; Mon, 2 Jun 1997 17:27:55 -0500 (CDT)
Received: by crystal.WonderWorks.COM 
	id QQcsgf17681; Mon, 2 Jun 1997 18:27:51 -0400 (EDT)
Date: Mon, 2 Jun 1997 18:27:51 -0400 (EDT)
Message-Id: <QQcsgf17681.199706022227@crystal.WonderWorks.COM>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
From: Kyle Jones <kyle_jones@wonderworks.com>
To: xemacs-beta@xemacs.org
Subject: Misfeature of the local-map property in rear-closed extents
In-Reply-To: <199706022055.WAA04163@zuse.dina.kvl.dk>
References: <199706022055.WAA04163@zuse.dina.kvl.dk>
X-Mailer: VM 6.32 under 20.3 XEmacs Lucid (beta3)
X-Face: /cA45WHG7jWq>(O3&Z57Y<"WsX5ddc,4c#w0F*zrV#=M
        0@~@,s;b,aMtR5Sqs"+nU.z^CSFQ9t`z2>W,S,]:[+2^
        Nbf6v4g>!&,7R4Ot4Wg{&tm=WX7P["9%a)_da48-^tGy
        ,qz]Z,Zz\{E.,]'EO+F)@$KtF&V

Per Abrahamsen writes:
 > The `local-map' property doesn't apply when point is at the
 > end of an extent.  I believe it should iff the extent is
 > rear-closed.

Thorny.  This could produce confusing results given a end-closed
extent adjactent to s start-closed extent.  Consider extents [1, 5]
and [5, 9) with point = 5.  The block cursor will be over a
character in the [5, 9) extent but the keymap used might end up
being the one associated with the [1, 5] extent, as a fallback
from the [5, 9) extent.

I see your problem, but I'm not totally convinced of the cure yet.
Maybe David Moore, who has been hacking the extents code more than 
I have, would have further insight into this.

