From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>,
43300@debbugs.gnu.org, Stefan Monnier <monnier@iro.umontreal.ca>,
Juri Linkov <juri@linkov.net>
Subject: bug#43300: [PATCH] Make M-x show new commands for obsolete aliases
Date: Tue, 16 Feb 2021 18:36:59 +0100 [thread overview]
Message-ID: <87eehfvrr8.fsf@gnus.org> (raw)
In-Reply-To: <CADwFkmnc8oe1mUkGcR2bD+yCRnOOctphFBfBb8cB0X-yT35TWA@mail.gmail.com> (Stefan Kangas's message of "Tue, 16 Feb 2021 11:32:27 -0600")
Stefan Kangas <stefan@marxist.se> writes:
> I find myself going back and forth: with the new filtering, there is
> suddenly a hope that `M-x' can produce a clean list of useful commands.
Yeah, that's true -- `M-x gnus-summary-toggle-truncation' is pretty
annoying to have appear here (it's an obsolete alias)... On the other
hand, it could be tagged with a mode (somehow) and that would also make
it go away (outside of Gnus summary buffers).
> The feature discussed here makes the list less clean, for reasons that
> are only temporarily useful. This is compounded by the fact that we
> maintain backwards compatibility aliases for such a long time. But of
> course there are also benefits to this more gentle obsoletion, as you
> say.
>
> Here's an idea:
>
> How about showing only obsolete aliases that are new in this major
> version? That could give us almost all the benefits without any of the
> drawbacks.
Hm! That's a pretty attractive option. So commands deprecate faster
than functions... makes sense to me.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-02-16 17:36 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
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 [this message]
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=87eehfvrr8.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43300@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=juri@linkov.net \
--cc=monnier@iro.umontreal.ca \
--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).