From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Stefan Kangas <stefan@marxist.se>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, 43300@debbugs.gnu.org
Subject: bug#43300: [PATCH] Make M-x show new commands for obsolete aliases
Date: Wed, 18 Nov 2020 13:51:19 -0800 (PST) [thread overview]
Message-ID: <cf4d2733-12af-4c2a-aab9-c1168892a7b5@default> (raw)
In-Reply-To: <87y2iyh7fh.fsf@mail.linkov.net>
> > I therefore think we should revert back to the old behavior for
> > commands that are obsolete without an alternative, that is we
> > should not add such commands to the list of completion candidates.
>
> Or maybe still some indication is needed to be displayed, even if there
> is no alias for a new command. Maybe display just " (obsolete)"?
Why? That can give the false impression that the
command doesn't _work_.
(And if for some reason the command really doesn't
work then it's not only obsolete. And a user will
soon enough understand that it doesn't work.)
next prev parent reply other threads:[~2020-11-18 21:51 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 23:59 bug#43300: [PATCH] Make M-x show new commands for obsolete aliases Stefan Kangas
2020-09-10 21:09 ` Lars Ingebrigtsen
2020-09-13 13:06 ` Stefan Kangas
2020-11-18 9:14 ` Juri Linkov
2020-11-18 12:43 ` Basil L. Contovounesios
2020-11-18 13:49 ` Stefan Kangas
2020-11-18 19:10 ` Juri Linkov
2020-11-18 21:51 ` Drew Adams [this message]
2020-11-18 22:06 ` Stefan Kangas
2021-02-16 15:35 ` Stefan Kangas
2021-02-16 16:23 ` Lars Ingebrigtsen
2021-02-16 17:32 ` Stefan Kangas
2021-02-16 17:36 ` Lars Ingebrigtsen
2021-02-17 9:52 ` Stefan Kangas
2021-02-17 11:16 ` Lars Ingebrigtsen
2021-02-17 13:26 ` Basil L. Contovounesios
2021-05-13 10:19 ` 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=cf4d2733-12af-4c2a-aab9-c1168892a7b5@default \
--to=drew.adams@oracle.com \
--cc=43300@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=juri@linkov.net \
--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).