From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Cc: mattiase@acm.org, rpluim@gmail.com, john@yates-sheets.org
Subject: RE: master 583cb26 2/3: Improve accuracy in string-replace description (bug#43598)
Date: Tue, 29 Sep 2020 08:28:27 -0700 (PDT) [thread overview]
Message-ID: <e0142539-1b2a-41f2-b87b-08fc6324a2f8@default> (raw)
In-Reply-To: <5A5A4570-876A-4EEB-BEBA-F5EA38CEBBB6@gnu.org>
> > > So they are not equal, right?
> >
> > Right. I don't think anyone said they were.
>
> You suggested to use "equal" in the doc string
> for strings which we now agree are not equal.
> Such doc string would confusing.
We're going 'round and 'round.
As I said before, I am not the one who suggested
to use "equal":
I'm not the one who proposed that "equal" part
And the suggestions were _never_ to say that the
input and result strings are equal. It was to
say that the input string _with the changes
applied_ is equal (in fact `equal') to the
returned string. Which is true.
https://lists.gnu.org/archive/html/emacs-devel/2020-09/msg02159.html
I suggest you maybe reread what the suggestions were.
This incessant back & forth quibbling is tiring.
I'm done with this one.
next prev parent reply other threads:[~2020-09-29 15:28 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 [this message]
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
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
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=e0142539-1b2a-41f2-b87b-08fc6324a2f8@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--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 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).