From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Improve `replace-regexp-in-string' ergonomics? Date: Wed, 22 Sep 2021 22:15:20 -0400 Message-ID: References: <878rzpw7jo.fsf@gnus.org> <87mto4tl6y.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19063"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: emacs-devel@gnu.org To: Lars Ingebrigtsen Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Sep 23 04:16:53 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 1mTEI9-0004jO-G7 for ged-emacs-devel@m.gmane-mx.org; Thu, 23 Sep 2021 04:16:53 +0200 Original-Received: from localhost ([::1]:58766 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mTEI6-0008QW-Nw for ged-emacs-devel@m.gmane-mx.org; Wed, 22 Sep 2021 22:16:50 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:37078) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mTEGo-0007eI-AN for emacs-devel@gnu.org; Wed, 22 Sep 2021 22:15:31 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:63311) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mTEGj-0004Mf-UJ for emacs-devel@gnu.org; Wed, 22 Sep 2021 22:15:29 -0400 Original-Received: from pmg3.iro.umontreal.ca (localhost [127.0.0.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 96BBA4413E0; Wed, 22 Sep 2021 22:15:22 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg3.iro.umontreal.ca (Proxmox) with ESMTP id 4C9484413FC; Wed, 22 Sep 2021 22:15:21 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1632363321; bh=r9e5fY+elVLNved9RRIE01G9i02pYafv44k7vP5Lu9M=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=E7vfwl7qPzNYBXnqYHW6NKR8wt0dBRu6p3l3fLnKfSpi0c88crMfPDxj8EIFocy0B IBjPX7ESsqo0/LbB0dg8hoeFXm7YWCb0/5JsYHzgEBBSAKlQh0PAJCdzpEI5tbak6L ZO30BG672s1WhEv3qhp1dOW8kJOd/yhDPERW47vsruofzCw+FFJZoik6mcB5fZAwve S+otnfB4sbrBgtIVm3AvUn9J2GMcuyqmzLVRFoC9jG2E+fV7xcGaZKJ6K1KTqJtu77 wNgECve6hcSCiXcqsV+1dkF27u+iyxDLQoyAJ98DKVVqIozTcbq0G1bhXKLPtaNdZB daMmIOQDVA53g== Original-Received: from milanesa (unknown [45.72.241.23]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id EFB621201E6; Wed, 22 Sep 2021 22:15:20 -0400 (EDT) In-Reply-To: <87mto4tl6y.fsf@gnus.org> (Lars Ingebrigtsen's message of "Wed, 22 Sep 2021 22:22:13 +0200") Received-SPF: pass client-ip=132.204.25.50; envelope-from=monnier@iro.umontreal.ca; helo=mailscanner.iro.umontreal.ca X-Spam_score_int: -42 X-Spam_score: -4.3 X-Spam_bar: ---- X-Spam_report: (-4.3 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham 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:275351 Archived-At: >> It'd be nice to have a front-end that lets you write a kind of lex-like >> set of rules, but I think it'd be important for that front-end to allow >> *computing* the replacement rather than only selecting it based on the >> matched regexp. Something like >> >> (foo-replace results >> ("\\[" "(") >> ("\\]" ")") >> ("[[:lower:]]+" (upcase (match-string 0))) >> ("siglo \\([0-9]+\\)" >> (integer-to-roman (string-to-number (match-string 1)))) >> ...) > > Perfect. That looks like a really nice function signature to me. > Perhaps without the parentheses if there's only one replacement to be > done. If someone's interested, `syntax-propertize-rules` solves a similar problem, so some of its code can be reused for that. Stefan