[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#25644: 26.0.50; Problematic transient map in minibuffer-force-comple

From: Michael Heerdegen
Subject: bug#25644: 26.0.50; Problematic transient map in minibuffer-force-complete
Date: Tue, 07 Feb 2017 16:52:19 +0100


[I CC Stefan because he has installed the fix for #12221 that added the
code that bites me]

I like to use icomplete-mode, but I prefer to have the bindings of RET
and C-j switched.

This sometimes collides with the transient-map installed by

Here is a random recipe for emacs -Q:


#+begin_src emacs-lisp
(define-key icomplete-minibuffer-map [return]       
(define-key icomplete-minibuffer-map [(control ?j)] #'exit-minibuffer)

Now (just a silly example):

M-x epatch

- Answer y to the question whether the patch is in a buffer
- Hit RET to confirm the suggested default

Note that nothing happens, or you get a `ding'.  The second RET works
OTOH.  Without the "Setup" part it works as expected however.

I debugged a bit and found that in the first place, the transient map
installed by minibuffer-force-complete shadows the (my) binding of RET.

Someone with insight into that code (Stefan, probably): am I'm doing
something forbidden, or should we improve that code?



In GNU Emacs (x86_64-pc-linux-gnu, GTK+ Version 3.22.7)
 of 2017-02-06 built on drachen
Repository revision: d45dbccc5d2360818e70bbb0bc816c62c8cf6cbe
Windowing system distributor 'The X.Org Foundation', version 11.0.11901000
System Description:     Debian GNU/Linux 9.0 (stretch)

reply via email to

[Prev in Thread] Current Thread [Next in Thread]