From: Stefan Kangas <stefankangas@gmail.com>
To: "Mattias Engdegård" <mattiase@acm.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 56641@debbugs.gnu.org
Subject: bug#56641: Deprecate `lsh`
Date: Tue, 19 Jul 2022 12:20:01 -0400 [thread overview]
Message-ID: <CADwFkmn8nkZRjsdmv6xV9eLSLvAB6-apuAWNV-24koxcpGd-Dw@mail.gmail.com> (raw)
In-Reply-To: <52FF0BFF-F19C-4ABA-82BE-8FE3277B726D@acm.org>
Mattias Engdegård <mattiase@acm.org> writes:
> Adding a few words to the doc string may suffice, but a byte-compiler
> warning would help.
What we have done in such cases is declare it obsolete but add a comment
that we want to keep it around for longer. See `interactive-p', that
was not deleted in Emacs 28 despite having been obsolete for over a
decade.
next prev parent reply other threads:[~2022-07-19 16:20 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 13:38 bug#56641: Deprecate `lsh` Mattias Engdegård
2022-07-19 13:52 ` Eli Zaretskii
2022-07-19 14:44 ` Stefan Kangas
2022-07-19 15:40 ` Eli Zaretskii
2022-07-19 15:53 ` Mattias Engdegård
2022-07-19 16:20 ` Stefan Kangas [this message]
2022-07-19 16:38 ` Eli Zaretskii
2022-07-20 1:25 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-20 2:36 ` Eli Zaretskii
2022-07-20 3:20 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-20 11:24 ` Eli Zaretskii
2022-07-20 11:57 ` Mattias Engdegård
2022-07-20 12:21 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-20 12:44 ` Eli Zaretskii
2022-07-20 14:30 ` Mattias Engdegård
2022-07-21 1:43 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-21 7:47 ` Mattias Engdegård
2022-07-23 7:26 ` Lars Ingebrigtsen
2022-07-23 10:32 ` Mattias Engdegård
2022-07-23 11:20 ` Lars Ingebrigtsen
2022-07-23 13:18 ` Eli Zaretskii
2022-07-23 13:20 ` Lars Ingebrigtsen
2022-07-23 15:42 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-07-23 16:51 ` Mattias Engdegård
2022-07-24 3:38 ` Basil L. Contovounesios via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=CADwFkmn8nkZRjsdmv6xV9eLSLvAB6-apuAWNV-24koxcpGd-Dw@mail.gmail.com \
--to=stefankangas@gmail.com \
--cc=56641@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=mattiase@acm.org \
/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).