unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 16:55:30 +0300	[thread overview]
Message-ID: <83zgklyvxp.fsf@gnu.org> (raw)
In-Reply-To: <lyo81140lo.fsf@new-host-2.home> (message from Howard Melman on Sat, 16 Apr 2022 09:30:27 -0400)

> From: Howard Melman <hmelman@gmail.com>
> Date: Sat, 16 Apr 2022 09:30:27 -0400
> 
> If the NEWS entry in question is just about M-x then you are
> correct that it is fine.  But if it's about these declare
> forms in general then it seems to be problematic.  I read it
> as the latter for two reasons.  First the header:
> 
>    ** New 'declare' forms to control completion of commands in 'M-x'.
> 
> reads to me as being about "New 'declare' forms" which are
> (incidently) used to control completion in M-x. That they
> are also used in M-S-x seems relevant though it's not
> stated.
> 
> Second, the final paragraph in question, talks about "these
> forms" and doesn't mention M-x so I took "excluded from being
> completion candidates" to mean from all commands.
> 
> This entry read to me as if it was written before
> execute-extended-command-for-buffer existed and wasn't
> updated after it was.
> 
> I think adding to the end something like: "from M-x (though
> they are used by M-S-x which see below)". would clarify it.

There's no real way for us to clarify NEWS entries after the
corresponding Emacs version was released, since we cannot
retroactively modify released versions, and Emacs 28.2 will have its
own section in NEWS, separate from Emacs 28.1.  And since this is
about something that is not even explicitly stated in NEWS, but your
inference from what is written there, I don't see an urgent need to
try to find some way of clarifying it.  The downside, I presume, is
that someone else could perhaps be led to the same erroneous
conclusion as you were.  We'll have to live with that, I guess.





  reply	other threads:[~2022-04-16 13:55 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
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 [this message]
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=83zgklyvxp.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).