From: Lars Ingebrigtsen <larsi@gnus.org>
To: John Yates <john@yates-sheets.org>
Cc: "Mattias Engdegård" <mattiase@acm.org>,
"Robert Pluim" <rpluim@gmail.com>,
"Drew Adams" <drew.adams@oracle.com>,
"Emacs developers" <emacs-devel@gnu.org>
Subject: Re: master 583cb26 2/3: Improve accuracy in string-replace description (bug#43598)
Date: Tue, 29 Sep 2020 15:40:17 +0200 [thread overview]
Message-ID: <87r1qkem66.fsf@gnus.org> (raw)
In-Reply-To: <CAJnXXoiSta=-bhKzpCYq_VGhgjWbd1h5c3hkhrSgz2dzQ5FMRQ@mail.gmail.com> (John Yates's message of "Mon, 28 Sep 2020 13:44:56 -0400")
John Yates <john@yates-sheets.org> writes:
> Is it guaranteed to be new if no replacements happen?
Nope. It used to be, but it's unnecessary and more inefficient.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-09-29 13:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200927124520.25321.62354@vcs0.savannah.gnu.org>
[not found] ` <20200927124522.BA20F207E0@vcs0.savannah.gnu.org>
2020-09-28 9:42 ` master 583cb26 2/3: Improve accuracy in string-replace description (bug#43598) Robert Pluim
2020-09-28 9:59 ` Mattias Engdegård
2020-09-28 11:09 ` Robert Pluim
[not found] ` <CAJnXXojjUAcRVmsZNWQ2j9rSDv76Y0od4yWfVg11k-Q2tf4NYA@mail.gmail.com>
2020-09-28 13:50 ` Robert Pluim
2020-09-28 16:36 ` John Yates
2020-09-28 16:49 ` Drew Adams
2020-09-28 16:55 ` Eli Zaretskii
2020-09-28 17:11 ` Drew Adams
2020-09-28 18:11 ` Eli Zaretskii
2020-09-28 22:36 ` John Yates
2020-09-28 22:47 ` Drew Adams
2020-09-29 2:35 ` Eli Zaretskii
2020-09-29 4:28 ` Drew Adams
2020-09-29 5:30 ` Eli Zaretskii
2020-09-29 15:28 ` Drew Adams
2020-09-29 2:37 ` Eli Zaretskii
2020-09-29 7:12 ` Robert Pluim
2020-09-29 14:26 ` Eli Zaretskii
2020-09-29 15:23 ` Robert Pluim
2020-09-29 16:02 ` Eli Zaretskii
2020-09-28 17:44 ` John Yates
2020-09-29 13:40 ` Lars Ingebrigtsen [this message]
2020-09-29 14:08 ` Mattias Engdegård
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=87r1qkem66.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=john@yates-sheets.org \
--cc=mattiase@acm.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.