From: "Mattias Engdegård" <mattiase@acm.org>
To: Robert Pluim <rpluim@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Drew Adams <drew.adams@oracle.com>,
emacs-devel@gnu.org
Subject: Re: master baf331e 3/3: Rename replace-in-string to string-replace
Date: Mon, 28 Sep 2020 18:28:09 +0200 [thread overview]
Message-ID: <CEEB7CE3-9BA4-453E-885B-D25C15905BF2@acm.org> (raw)
In-Reply-To: <m21rilx5zl.fsf@gmail.com>
28 sep. 2020 kl. 17.42 skrev Robert Pluim <rpluim@gmail.com>:
> Yes, itʼs an unfortunate clash. Then again, how much XEmacs code still
> exists that depends on it?
In the Emacs tree, prolog-mode used replace-in-string for regexp-matching replacement. This was taken as an indication that repurposing that name would have been risky.
The change of names may have been wise or unnecessarily prudent; I haven't found any other use of replace-in-string in the wild that isn't explicitly guarded by a test for XEmacs. Nevertheless, 'string-replace' isn't a bad name.
next prev parent reply other threads:[~2020-09-28 16:28 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CEEB7CE3-9BA4-453E-885B-D25C15905BF2@acm.org \
--to=mattiase@acm.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=rpluim@gmail.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.