From: Eli Zaretskii <eliz@gnu.org>
To: Howard Melman <hmelman@gmail.com>
Cc: 54964@debbugs.gnu.org
Subject: bug#54964: 28.1; mistatement in NEWS about read-extended-command-predicate
Date: Sat, 16 Apr 2022 09:35:25 +0300 [thread overview]
Message-ID: <83mtgl1qoi.fsf@gnu.org> (raw)
In-Reply-To: <4DA6706F-6B98-4CA5-B1A5-EAFBDAB3125F@gmail.com> (message from Howard Melman on Fri, 15 Apr 2022 16:16:07 -0400)
> From: Howard Melman <hmelman@gmail.com>
> Date: Fri, 15 Apr 2022 16:16:07 -0400
>
> The Emacs 28.1 NEWS item:
>
> ** New 'declare' forms to control completion of commands in 'M-x'.
>
> ends with:
>
> Note that these forms will only have their effect if the
> 'read-extended-command-predicate' user option is customized to call
> 'command-completion-default-include-p' or a similar function. The
> default value of 'read-extended-command-predicate' is nil, which means
> no commands that match what you have typed are excluded from being
> completion candidates.
>
> But I think this isn't true because the new command
> execute-extended-command-for-buffer bound to M-S-x by
> default will filter the commands based on these declare forms.
What you say is true, but how is it relevant to the 'declare' forms
mentioned in that NEWS entry? M-S-x doesn't use any of them, and the
NEWS entry doesn't describe that command, it only describes the two
new 'declare' forms.
next prev parent reply other threads:[~2022-04-16 6:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 20:16 bug#54964: 28.1; mistatement in NEWS about read-extended-command-predicate Howard Melman
2022-04-16 6:35 ` Eli Zaretskii [this message]
2022-04-16 9:27 ` Lars Ingebrigtsen
2022-04-16 10:52 ` Eli Zaretskii
2022-04-16 10:59 ` Lars Ingebrigtsen
2022-04-16 11:09 ` Eli Zaretskii
2022-04-16 13:30 ` Howard Melman
2022-04-16 13:55 ` Eli Zaretskii
2022-04-16 14:20 ` Howard Melman
2022-04-16 14:25 ` Lars Ingebrigtsen
2022-04-16 16:23 ` Eli Zaretskii
2022-04-16 16:27 ` Lars Ingebrigtsen
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=83mtgl1qoi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=54964@debbugs.gnu.org \
--cc=hmelman@gmail.com \
/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).