From: Eli Zaretskii <eliz@gnu.org>
To: "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
Date: Tue, 25 Jun 2019 18:26:22 +0300 [thread overview]
Message-ID: <83tvcdlm8x.fsf@gnu.org> (raw)
In-Reply-To: <CE959479-5645-40FD-AC18-303276F04DF1@acm.org> (message from Mattias Engdegård on Tue, 25 Jun 2019 14:01:49 +0200)
> From: Mattias Engdegård <mattiase@acm.org>
> Date: Tue, 25 Jun 2019 14:01:49 +0200
>
> (replace-regexp-in-string "a" "X" "abcab" t t nil 2)
>
> would be expected to return
>
> "abcXb"
>
> but the actual return value is
>
> "cXb"
>
> This was probably not intended. The manual text is
>
> This function copies STRING and searches it for matches for REGEXP,
> and replaces them with REP. It returns the modified copy. If
> START is non-‘nil’, the search for matches starts at that index in
> STRING, so matches starting before that index are not changed.
>
> The question is whether it is too late to fix the bug, or if it needs to be documented.
Both, I think ;-)
Thanks.
next prev parent reply other threads:[~2019-06-25 15:26 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 [this message]
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
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=83tvcdlm8x.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=36372@debbugs.gnu.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.