GNU bug report logs - #10459
Overlay keymaps ignored until point is moved when overlay is created from timer

Previous Next

To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 10459 in the body.
You can then email your comments to 10459 AT debbugs.gnu.org in the normal way.

Toggle the display of automated, internal messages from the tracker.

Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):

From: Toby Cubitt <tsc25 <at> cantab.net>
To: bug-gnu-emacs <at> gnu.org
Subject: Overlay keymaps ignored until point is moved when overlay is created
	from timer
Date: Sun, 8 Jan 2012 16:14:54 +0100

Emacs versions known to be affected:
------------------------------------
23.2.1, 24 (recent bzr checkout).


Steps to reproduce:
-------------------

1. Define the following function:

(defun test ()
  (interactive)
  (run-with-timer 
   2 nil
   (lambda ()
     (setq overlay (make-overlay 4 8))
     (overlay-put overlay 'face '(background-color . "black"))
     (let ((map (make-sparse-keymap)))
       (overlay-put overlay 'keymap map)
       (define-key map "t" (lambda () (interactive) 
			     (message "overlay keymap binding")))))))

2. Position point somewhere between 4 and 8.

3. M-x test

4. type "t" (*without* moving point first)


Expected output:
----------------
Overlay keymap binding should display the message "overlay keymap binding".


Actual output:
--------------
Default `self-insert-command' binding inserts character "t" into the buffer.


Additional information:
-----------------------
Note that moving the point, e.g. one character to the right and then back,
in between septs 3. and 4. seems to activate the overlay keymap binding,
so that typing "t" in step 4. displays the correct message.

-- 
Dr T. S. Cubitt
Mathematics and Quantum Information group
Department of Mathematics
Complutense University
Madrid, Spain

Message #8 received at 10459 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
To: Toby Cubitt <toby-predictive-dated-1327275432.bb87aa <at> dr-qubit.org>
Cc: 10459 <at> debbugs.gnu.org
Subject: Re: bug#10459: Overlay keymaps ignored until point is moved when
	overlay is created from timer
Date: Sun, 08 Jan 2012 22:52:54 -0500

Yes, this is a known limitation: the set of active keymaps is computed
before waiting for the next key sequence.

You might be able to get around this problem by pushing some dummy event
(which you then bind to `ignore' in some keymap) onto
unread-command-event from your timer, just to force a refresh.


        Stefan

Message #11 received at 10459 <at> debbugs.gnu.org (full text, mbox):

From: Stefan Monnier <monnier <at> iro.umontreal.ca>
To: Toby Cubitt <tsc25 <at> cantab.net>
Cc: 10459 <at> debbugs.gnu.org
Subject: Re: bug#10459: Overlay keymaps ignored until point is moved when
	overlay is created from timer
Date: Mon, 16 Jan 2012 09:34:51 -0500

> I've tested this, and it does indeed work. Thanks Stefan.

Cool.  It's an ugly hack, but for now it's the best I can offer ;-(

> At the moment, for the dummy event, I'm using a keyboard event for an
> unlikely unicode character with every modifier set. Is there some better
> choice than this?

Use a symbol like `toby-cubitt-dummy-event'.


        Stefan

Message #14 received at 10459 <at> debbugs.gnu.org (full text, mbox):

From: Toby Cubitt <toby-predictive-dated-1327924137.9ab140 <at> dr-qubit.org>
To: Stefan Monnier <monnier <at> IRO.UMontreal.CA>
Cc: 10459 <at> debbugs.gnu.org
Subject: Re: bug#10459: Overlay keymaps ignored until point is moved when
	overlay is created from timer
Date: Mon, 16 Jan 2012 12:48:11 +0100

On Sun, Jan 08, 2012 at 10:52:54PM -0500, Stefan Monnier wrote:
> Yes, this is a known limitation: the set of active keymaps is computed
> before waiting for the next key sequence.
> 
> You might be able to get around this problem by pushing some dummy event
> (which you then bind to `ignore' in some keymap) onto
> unread-command-event from your timer, just to force a refresh.

I've tested this, and it does indeed work. Thanks Stefan.

At the moment, for the dummy event, I'm using a keyboard event for an
unlikely unicode character with every modifier set. Is there some better
choice than this?

Toby
-- 
Dr T. S. Cubitt
Mathematics and Quantum Information group
Department of Mathematics
Complutense University
Madrid, Spain

email: tsc25 <at> cantab.net
web:   www.dr-qubit.org

Message #21 received at 10459-done <at> debbugs.gnu.org (full text, mbox):

From: Dmitry Gutov <dgutov <at> yandex.ru>
To: Toby Cubitt <toby-predictive-dated-1327924137.9ab140 <at> dr-qubit.org>
Cc: 10459-done <at> debbugs.gnu.org, Stefan Monnier <monnier <at> IRO.UMontreal.CA>
Subject: Re: bug#10459: Overlay keymaps ignored until point is moved when
 overlay is created from timer
Date: Sun, 05 Oct 2014 05:21:25 +0400

Version: 24.4

> On Sun, Jan 08, 2012 at 10:52:54PM -0500, Stefan Monnier wrote:
>> Yes, this is a known limitation: the set of active keymaps is computed
>> before waiting for the next key sequence.

This has been fixed around the start of 24.4 development: the set of
keymaps is recomputed at the start of a key sequence.

The examples in this and merged bugs work for me now. Please feel free
to reopen if you see a case where the problem's not fixed.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.