From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Stefan Kangas <stefan@marxist.se>
Cc: emacs-devel@gnu.org
Subject: Re: master 1b0a922 1/2: Make M-x show obsolete commands (Bug#43300)
Date: Sun, 13 Sep 2020 15:35:38 -0400 [thread overview]
Message-ID: <jwvsgbl79ti.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20200913130616.6B79C20B2C@vcs0.savannah.gnu.org> (Stefan Kangas's message of "Sun, 13 Sep 2020 09:06:16 -0400 (EDT)")
> Make M-x show obsolete commands (Bug#43300)
> * lisp/simple.el (read-extended-command): Don't hide obsolete
> commands.
> (read-extended-command--annotation): Show an annotation for obsolete
> commands that says what their new name is.
I think this doesn't push users away from obsolete commands
strongly enough. If removing them from the list of completions is not
an option any more, then maybe we could/should force a kind of
"confirmation". e.g. `M-x <obsolete-command> RET` would emit a short
"Really call obsolete `obsolete-command`?" and wait for an extra RET
before going ahead.
Stefan
> lisp/simple.el | 21 ++++++++-------------
> 1 file changed, 8 insertions(+), 13 deletions(-)
>
> diff --git a/lisp/simple.el b/lisp/simple.el
> index b5002dd..16ff863 100644
> --- a/lisp/simple.el
> +++ b/lisp/simple.el
> @@ -1881,22 +1881,17 @@ to get different commands to edit and resubmit."
> '(metadata
> (annotation-function . read-extended-command--annotation)
> (category . command))
> - (let ((pred
> - (if (memq action '(nil t))
> - ;; Exclude obsolete commands from completions.
> - (lambda (sym)
> - (and (funcall pred sym)
> - (or (equal string (symbol-name sym))
> - (not (get sym 'byte-obsolete-info)))))
> - pred)))
> - (complete-with-action action obarray string pred))))
> + (complete-with-action action obarray string pred)))
> #'commandp t nil 'extended-command-history)))
>
> (defun read-extended-command--annotation (command-name)
> - (let* ((function (and (stringp command-name) (intern-soft command-name)))
> - (binding (where-is-internal function overriding-local-map t)))
> - (when (and binding (not (stringp binding)))
> - (format " (%s)" (key-description binding)))))
> + (let* ((fun (and (stringp command-name) (intern-soft command-name)))
> + (binding (where-is-internal fun overriding-local-map t))
> + (obsolete (get fun 'byte-obsolete-info)))
> + (cond (obsolete
> + (format " (%s)" (car obsolete)))
> + ((and binding (not (stringp binding)))
> + (format " (%s)" (key-description binding))))))
>
> (defcustom suggest-key-bindings t
> "Non-nil means show the equivalent key-binding when M-x command has one.
next parent reply other threads:[~2020-09-13 19:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200913130614.15564.25449@vcs0.savannah.gnu.org>
[not found] ` <20200913130616.6B79C20B2C@vcs0.savannah.gnu.org>
2020-09-13 19:35 ` Stefan Monnier [this message]
2020-09-18 10:33 ` master 1b0a922 1/2: Make M-x show obsolete commands (Bug#43300) Stefan Kangas
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=jwvsgbl79ti.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=stefan@marxist.se \
/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).