From: Michael Heerdegen <michael_heerdegen@web.de>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 25644@debbugs.gnu.org
Subject: bug#25644: 26.0.50; Problematic transient map in minibuffer-force-complete
Date: Tue, 07 Feb 2017 17:41:35 +0100 [thread overview]
Message-ID: <874m06ar7k.fsf@drachen> (raw)
In-Reply-To: <jwvlgti3ria.fsf-monnier+emacsbugs@gnu.org> (Stefan Monnier's message of "Tue, 07 Feb 2017 11:23:43 -0500")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> > (define-key icomplete-minibuffer-map [return]
> > #'icomplete-force-complete-and-exit)
>
> FWIW, I think this should be
>
> (define-key icomplete-minibuffer-map [?\r]
> #'icomplete-force-complete-and-exit)
> aka
> (define-key icomplete-minibuffer-map (kbd "RET")
> #'icomplete-force-complete-and-exit)
Why?
> BTW, if you do
>
> M-x epatch
> - Answer y to the question whether the patch is in a buffer
> - C-h k RET
>
> what does it say?
It says
| <return> runs the command icomplete-force-complete-and-exit, which is
| an interactive compiled Lisp function in `icomplete.el'.
but I know that this is wrong (it doesn't consider the transient map).
This is one reason why I needed more than one hour before I found out
what's going on.
FWIW `interaction-log' says that the command run has been
| #[0 \303.\305\300`\301\302$)\207 [#<marker at 1 in *Minibuf-1*> #[771 \211\301>\203.
next prev parent reply other threads:[~2017-02-07 16:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 15:52 bug#25644: 26.0.50; Problematic transient map in minibuffer-force-complete Michael Heerdegen
2017-02-07 16:23 ` Stefan Monnier
2017-02-07 16:41 ` Michael Heerdegen [this message]
2019-01-23 17:38 ` Stefan Monnier
2019-01-24 22:54 ` Michael Heerdegen
2019-01-25 13:59 ` Stefan Monnier
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874m06ar7k.fsf@drachen \
--to=michael_heerdegen@web.de \
--cc=25644@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).