[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Improve `replace-regexp-in-string' ergonomics?
From: |
Mattias Engdegård |
Subject: |
Re: Improve `replace-regexp-in-string' ergonomics? |
Date: |
Wed, 22 Sep 2021 21:30:18 +0200 |
22 sep. 2021 kl. 20.14 skrev Stefan Monnier <monnier@iro.umontreal.ca>:
> It'd be nice to have a front-end that lets you write a kind of lex-like
> set of rules
In particular since sequential substitution (replace A with A', then B with B',
...) is often very error-prone: it's order-sensitive, and sometimes there is no
correct order at all.
People use chains of replace-regexp-in-string because it's simple and it's
there but when a simultaneous replacement is called for then we should provide
such a construct, not make it easier to do the wrong thing.
- Re: Improve `replace-regexp-in-string' ergonomics?, (continued)
Re: Improve `replace-regexp-in-string' ergonomics?, Lars Ingebrigtsen, 2021/09/22
Re: Improve `replace-regexp-in-string' ergonomics?, Dmitry Gutov, 2021/09/22
Re: Improve `replace-regexp-in-string' ergonomics?, Stefan Monnier, 2021/09/22