[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#11840: 24.1.50; nil keymap element on high priority overlay should f
bug#11840: 24.1.50; nil keymap element on high priority overlay should fallthrough to low priority overlay
Mon, 2 Jul 2012 12:32:48 -0400
On Mon, Jul 2, 2012 at 10:39 AM, Stefan Monnier
>> One more symptom, and I doubt this could be anything but a bug: if you
>> delete the high priority overlay, we *still* don't use the lower
>> priority overlay's keymap!
> This is a limitation of the way properties are "merged".
> More specifically, in most cases properties coming from different
> overlays (and from text-properties) are *not* merged. Instead, the
> property of the highest-priority overlay is used.
For the problem you cited, that seems to be irrelevant... if you
create two overlays o1 and o2, and delete o2, the editor should act
the same as if you just created o1. If not, in what sense are you
actually deleting the overlay? There should be no merge involved when
only considering one overlay.