From: Drew Adams <drew.adams@oracle.com>
To: Gregory Heytings <gregory@heytings.org>,
martin rudalics <rudalics@gmx.at>
Cc: "60252@debbugs.gnu.org" <60252@debbugs.gnu.org>
Subject: bug#60252: 29.0.60; help-fns--describe-function-or-command-prompt asks for confirmation
Date: Thu, 22 Dec 2022 23:25:05 +0000 [thread overview]
Message-ID: <SJ0PR10MB54881DD2627B0B45735B5A02F3E89@SJ0PR10MB5488.namprd10.prod.outlook.com> (raw)
In-Reply-To: <86f81b9e45a3d6576082@heytings.org>
> I suggest
>
> (define-key minibuffer-local-must-match-map (kbd "RET") #'minibuffer-
> force-complete-and-exit)
Why?
Needing to do that is something new. The binding has
been `minibuffer-complete-and-exit' since Day One.
next prev parent reply other threads:[~2022-12-22 23:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 9:21 bug#60252: 29.0.60; help-fns--describe-function-or-command-prompt asks for confirmation martin rudalics
2022-12-22 10:54 ` Eli Zaretskii
2022-12-22 14:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-22 15:30 ` Eli Zaretskii
2022-12-22 16:41 ` martin rudalics
2022-12-22 16:48 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-22 16:53 ` Eli Zaretskii
2022-12-22 21:14 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-23 7:26 ` Eli Zaretskii
2022-12-22 21:32 ` Gregory Heytings
2022-12-22 23:25 ` Drew Adams [this message]
2022-12-23 7:02 ` Juri Linkov
2022-12-23 14:43 ` Eli Zaretskii
2022-12-23 16:36 ` Drew Adams
2022-12-23 7:32 ` Eli Zaretskii
2022-12-23 16:47 ` Drew Adams
2022-12-23 18:43 ` Eli Zaretskii
2022-12-23 20:45 ` Drew Adams
2022-12-24 6:43 ` Eli Zaretskii
2022-12-23 7:24 ` Eli Zaretskii
2022-12-23 11:21 ` Gregory Heytings
2022-12-23 12:39 ` Eli Zaretskii
2022-12-23 8:33 ` martin rudalics
2022-12-23 11:19 ` Gregory Heytings
2022-12-24 8:38 ` martin rudalics
2022-12-23 11:34 ` Eli Zaretskii
2022-12-24 8:38 ` martin rudalics
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=SJ0PR10MB54881DD2627B0B45735B5A02F3E89@SJ0PR10MB5488.namprd10.prod.outlook.com \
--to=drew.adams@oracle.com \
--cc=60252@debbugs.gnu.org \
--cc=gregory@heytings.org \
--cc=rudalics@gmx.at \
/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).