From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?utf-8?Q?Mattias_Engdeg=C3=A5rd?= Newsgroups: gmane.emacs.devel Subject: Re: Improve `replace-regexp-in-string' ergonomics? Date: Wed, 22 Sep 2021 21:30:18 +0200 Message-ID: <6187FEAD-AAC3-4522-BCE3-AA5FD3973570@acm.org> References: <878rzpw7jo.fsf@gnus.org> Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.21\)) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="29239"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Lars Ingebrigtsen , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Wed Sep 22 21:34:21 2021 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mT80a-0007LE-0q for ged-emacs-devel@m.gmane-mx.org; Wed, 22 Sep 2021 21:34:20 +0200 Original-Received: from localhost ([::1]:45986 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mT80Y-0004Ck-Jk for ged-emacs-devel@m.gmane-mx.org; Wed, 22 Sep 2021 15:34:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:60594) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mT7ww-0001Ol-8g for emacs-devel@gnu.org; Wed, 22 Sep 2021 15:30:35 -0400 Original-Received: from mail72c50.megamailservers.eu ([91.136.10.82]:58972 helo=mail92c50.megamailservers.eu) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mT7wq-0006xk-Dt for emacs-devel@gnu.org; Wed, 22 Sep 2021 15:30:30 -0400 X-Authenticated-User: mattiase@bredband.net DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=megamailservers.eu; s=maildub; t=1632339022; bh=NwzjfJMgWuf0Dxgfiik2MUkmfDiixA5i/YJNow1D7Fc=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=dXrVDls3aGDG3UIcnY60L0HPMhL4R4Yq1YPxLa9Q5Ji1+b35mCDz+s133UgrN8koA fwLDsclkJJHTU/H+KW/RAHvrUyzIGi8lGhaNGUYHVcMUSORc00m4BdQEE6UHNI5OLB CIalZiQPrpAhdHJWa/k0O9Te3MyVkCHfwy5SRcfc= Feedback-ID: mattiase@acm.or Original-Received: from stanniol.lan (c-b952e353.032-75-73746f71.bbcust.telenor.se [83.227.82.185]) (authenticated bits=0) by mail92c50.megamailservers.eu (8.14.9/8.13.1) with ESMTP id 18MJUJma026366; Wed, 22 Sep 2021 19:30:21 +0000 In-Reply-To: X-Mailer: Apple Mail (2.3445.104.21) X-CTCH-RefID: str=0001.0A742F1C.614B844E.0012, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 X-CTCH-VOD: Unknown X-CTCH-Spam: Unknown X-CTCH-Score: 0.000 X-CTCH-Flags: 0 X-CTCH-ScoreCust: 0.000 X-CSC: 0 X-CHA: v=2.4 cv=C7OKdSD+ c=1 sm=1 tr=0 ts=614b844e a=von4qPfY+hyqc0zmWf0tYQ==:117 a=von4qPfY+hyqc0zmWf0tYQ==:17 a=kj9zAlcOel0A:10 a=M51BFTxLslgA:10 a=iRZporoAAAAA:8 a=jNTa_4MuRp6mRUJ4vPUA:9 a=CjuIK1q_8ugA:10 a=NOBgFS-JBQ2l-kSd6-zu:22 X-Origin-Country: SE Received-SPF: softfail client-ip=91.136.10.82; envelope-from=mattiase@acm.org; helo=mail92c50.megamailservers.eu X-Spam_score_int: -11 X-Spam_score: -1.2 X-Spam_bar: - X-Spam_report: (-1.2 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.io gmane.emacs.devel:275335 Archived-At: 22 sep. 2021 kl. 20.14 skrev Stefan Monnier : > 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.