From: Drew Adams <drew.adams@oracle.com>
To: "Lars Ingebrigtsen" <larsi@gnus.org>,
"Mattias Engdegård" <mattiase@acm.org>
Cc: 36372@debbugs.gnu.org
Subject: bug#36372: 27.0.50; replace-regexp-in-string skips START first chars in return value [PATCH]
Date: Wed, 26 Jun 2019 07:01:04 -0700 (PDT) [thread overview]
Message-ID: <732ddb90-5456-45dc-9c79-15d0a0662c28@default> (raw)
In-Reply-To: <m3y31o1mky.fsf@gnus.org>
> So it isn't used in-tree at all. Since it's an (in my opinion) pretty
> useless parameter as it's currently implemented, I think we should
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> deprecate the parameter and remove the documentation.
>
> Then, perhaps, in ten years time we can reintroduce the parameter with
> better semantics. :-)
1. Whether it's used in-tree is not sufficient.
2. Whether it is useless "as it's currently
implemented" is not sufficient. That's what
implementation bugs are about.
3. But I agree that it is likely very rarely used,
if at all. (Searched my code and found no
matches, as one example.)
3. IF it has a use, when fixed as you see fit,
then fix it, and call out the fixed behavior
as an incompatible change. In that case, do
not deprecate it. (I don't know that it has
a use, if fixed, hence "IF".)
next prev parent reply other threads:[~2019-06-26 14:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-25 12:01 bug#36372: 27.0.50; replace-regexp-in-string skips START first chars in return value Mattias Engdegård
2019-06-25 15:26 ` Eli Zaretskii
2019-06-26 9:31 ` bug#36372: 27.0.50; replace-regexp-in-string skips START first chars in return value [PATCH] Mattias Engdegård
2019-06-26 9:38 ` Robert Pluim
2019-06-26 10:01 ` Mattias Engdegård
2019-06-26 11:11 ` Robert Pluim
2019-06-26 10:22 ` Lars Ingebrigtsen
2019-06-26 12:32 ` Robert Pluim
2019-06-26 13:51 ` Lars Ingebrigtsen
2019-06-26 14:01 ` Drew Adams [this message]
2019-06-26 14:51 ` Eli Zaretskii
2019-06-26 15:20 ` Mattias Engdegård
2019-06-26 15:59 ` Clément Pit-Claudel
2019-06-26 17:03 ` Mattias Engdegård
2019-06-26 17:09 ` Eli Zaretskii
2019-06-26 17:41 ` Mattias Engdegård
2019-06-26 15:17 ` Eli Zaretskii
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=732ddb90-5456-45dc-9c79-15d0a0662c28@default \
--to=drew.adams@oracle.com \
--cc=36372@debbugs.gnu.org \
--cc=larsi@gnus.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).