From: Robert Pluim <rpluim@gmail.com>
To: Stefan Kangas <stefan@marxist.se>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: master baf331e 3/3: Rename replace-in-string to string-replace
Date: Mon, 28 Sep 2020 17:25:15 +0200 [thread overview]
Message-ID: <m25z7xx6sk.fsf@gmail.com> (raw)
In-Reply-To: <CADwFkm=8mq4Mi-SjCMfRRzF2oobug2SLOqHsjkCdoX5S3qsweA@mail.gmail.com> (Stefan Kangas's message of "Mon, 28 Sep 2020 16:56:28 +0200")
>>>>> On Mon, 28 Sep 2020 16:56:28 +0200, Stefan Kangas <stefan@marxist.se> said:
Stefan> Robert Pluim <rpluim@gmail.com> writes:
>> Do we need a (defalias 'string-replace-regexp
>> 'replace-regexp-in-string)?
Stefan> Or (define-obsolete-function-alias 'replace-regexp-in-string
Stefan> #'string-replace-regexp "28.1")
Obsoleting such a commonly used function just because we have an
additional name for it would cause lots of needless warnings in
perfectly fine elisp. e.g., just because we have 'first' is not a
reason to declare 'car' obsolete.
Robert
--
next prev parent reply other threads:[~2020-09-28 15:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200926222500.20662.9159@vcs0.savannah.gnu.org>
[not found] ` <20200926222503.227F720441@vcs0.savannah.gnu.org>
2020-09-28 9:32 ` master baf331e 3/3: Rename replace-in-string to string-replace Robert Pluim
2020-09-28 11:14 ` Lars Ingebrigtsen
2020-09-28 12:21 ` Robert Pluim
2020-09-28 15:21 ` Drew Adams
2020-09-28 15:42 ` Robert Pluim
2020-09-28 16:28 ` Mattias Engdegård
2020-09-28 16:31 ` tomas
2020-09-28 17:21 ` Stefan Monnier
2020-09-28 17:30 ` Drew Adams
2020-09-29 13:29 ` Lars Ingebrigtsen
2020-09-28 13:45 ` Stefan Monnier
2020-09-28 14:01 ` Lars Ingebrigtsen
2020-09-28 14:56 ` Stefan Kangas
2020-09-28 15:25 ` Robert Pluim [this message]
2020-09-28 15:41 ` Drew Adams
2020-09-28 15:45 ` Robert Pluim
2020-09-28 16:01 ` Drew Adams
2020-09-28 15:38 ` Drew Adams
2020-09-28 15:50 ` Robert Pluim
2020-09-28 16:03 ` Drew Adams
2020-09-28 15:44 ` Lars Ingebrigtsen
2020-09-29 13:22 ` 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=m25z7xx6sk.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.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).