From: Robert Pluim <rpluim@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: "Mattias Engdegård" <mattiase@acm.org>, 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 14:32:40 +0200 [thread overview]
Message-ID: <m2lfxo8r2v.fsf@gmail.com> (raw)
In-Reply-To: <m3pnn03aup.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 26 Jun 2019 12:22:06 +0200")
>>>>> On Wed, 26 Jun 2019 12:22:06 +0200, Lars Ingebrigtsen <larsi@gnus.org> said:
Larsi> Robert Pluim <rpluim@gmail.com> writes:
>> I think this is one of those 'who could possibly be relying on this
>> behaviour' bugs that bites you hard if you change things, so
>> documentation is probably best.
Larsi> Yup. But this is very unusual behaviour for such a function, so even if
Larsi> documented, it's going to cause confusion...
Larsi> Has anybody grepped through the Emacs tree to see whether anybody uses
Larsi> the parameter, and if so, whether it's expecting the wrong behaviour?
'grep'? Sounds complicated. I ran a combination of find-dired and
diredp-do-apply-function over the lisp sources, and none of the 656
calls to replace-regexp-in-string have 7 arguments.
Robert
next prev parent reply other threads:[~2019-06-26 12:32 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 [this message]
2019-06-26 13:51 ` Lars Ingebrigtsen
2019-06-26 14:01 ` Drew Adams
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2lfxo8r2v.fsf@gmail.com \
--to=rpluim@gmail.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 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.