From: Thierry Volpiatto <thievol@posteo.net>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Lars Ingebrigtsen <larsi@gnus.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Improve `replace-regexp-in-string' ergonomics?
Date: Wed, 22 Sep 2021 07:47:14 +0000 [thread overview]
Message-ID: <87wnn9gigt.fsf@posteo.net> (raw)
In-Reply-To: <CAP_d_8X64-MMx3OtbOCWWkkrRnb27RobY6Qe9O0CP9N-ZVYvKw@mail.gmail.com> (Yuri Khan's message of "Wed, 22 Sep 2021 12:22:05 +0700")
Yuri Khan <yuri.v.khan@gmail.com> writes:
> However, I have a hypothesis that what users really want is “I have
> this list of pattern/replacement pairs, and I want to go through each
> occurrence of each pattern in the original text, and replace them with
> their respective replacements”, without thinking about intermediate
> buffer contents. In simple cases, this can be simulated by
> parenthesizing each pattern, joining them all with a \|, and using the
> resulting super-pattern to iterate through occurrences, then,
> depending on which group matched, doing the replacement. (Harder cases
> include those where patterns have capturing groups and/or
> backreferences.)
Instead of using a list like
(pattern replacement pattern replacement etc...)
perhaps a list like (pattern subexp replacement ...) then you can loop
in this list doing the replacement with those 3 elements, something like
this:
(defun tv/replace-regexp-in-string (regexps string &optional fixedcase literal)
(cl-assert (zerop (% (length regexps) 3)))
(cl-loop with str = string
for (m s r) on regexps by 'cdddr
do (setq str (replace-regexp-in-string
m r str
fixedcase literal s))
finally return str))
With previous example it give:
(let ((results "['foo', 'bar', 'baz']"))
(tv/replace-regexp-in-string
'("\\[" 0 "("
"\\]" 0 ")"
",[[:space:]]" 0 " "
"'" 0 "\"")
results))
"(\"foo\" \"bar\" \"baz\")"
--
Thierry
next prev parent reply other threads:[~2021-09-22 7:47 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 4:36 Improve `replace-regexp-in-string' ergonomics? Lars Ingebrigtsen
2021-09-22 5:22 ` Yuri Khan
2021-09-22 6:36 ` Lars Ingebrigtsen
2021-09-22 7:47 ` Thierry Volpiatto [this message]
2021-09-22 5:24 ` Po Lu
2021-09-22 6:37 ` Lars Ingebrigtsen
2021-09-22 10:56 ` Po Lu
2021-09-22 20:08 ` Lars Ingebrigtsen
2021-09-23 0:11 ` Po Lu
2021-09-22 7:33 ` Adam Porter
2021-09-22 8:09 ` Lars Ingebrigtsen
2021-09-22 7:51 ` Andreas Schwab
2021-09-22 8:14 ` Augusto Stoffel
2021-09-22 8:21 ` Adam Porter
2021-09-22 18:01 ` Stefan Monnier
2021-09-22 18:24 ` Basil L. Contovounesios
2021-09-22 22:56 ` Adam Porter
2021-09-22 23:53 ` Eric Abrahamsen
2021-09-22 20:06 ` Lars Ingebrigtsen
2021-09-22 10:59 ` Dmitry Gutov
2021-09-22 20:18 ` Lars Ingebrigtsen
2021-09-22 22:23 ` Dmitry Gutov
2021-09-22 23:24 ` [External] : " Drew Adams
2021-09-22 18:14 ` Stefan Monnier
2021-09-22 19:30 ` Mattias Engdegård
2021-09-22 20:22 ` Lars Ingebrigtsen
2021-09-22 20:29 ` Lars Ingebrigtsen
2021-09-23 2:15 ` Stefan Monnier
2021-10-05 16:18 ` Juri Linkov
2021-10-12 6:53 ` Juri Linkov
2021-10-12 12:10 ` Lars Ingebrigtsen
2021-10-12 12:34 ` Stefan Monnier
2021-10-12 12:41 ` Lars Ingebrigtsen
2021-10-12 13:18 ` Lars Ingebrigtsen
2021-10-12 13:32 ` Mattias Engdegård
2021-10-12 15:48 ` Stefan Monnier
2021-10-12 13:33 ` Thierry Volpiatto
2021-10-12 19:16 ` Juri Linkov
2021-10-12 20:44 ` Thierry Volpiatto
2021-10-13 7:57 ` Juri Linkov
2021-10-13 8:41 ` Thierry Volpiatto
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=87wnn9gigt.fsf@posteo.net \
--to=thievol@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=larsi@gnus.org \
--cc=yuri.v.khan@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).