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: Looking at function Date: Mon, 11 Jul 2022 20:29:22 -0400 Message-ID: References: <86edz8k6q1.fsf@mail.linkov.net> <86y1wzv4uv.fsf@mail.linkov.net> <3c642f4d-471b-d6d2-8519-b4707e1193ba@yandex.ru> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="40129"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) Cc: Juri Linkov , emacs-devel@gnu.org To: Dmitry Gutov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Tue Jul 12 02:30:45 2022 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 1oB3nY-000AEn-Ok for ged-emacs-devel@m.gmane-mx.org; Tue, 12 Jul 2022 02:30:44 +0200 Original-Received: from localhost ([::1]:38902 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oB3nX-0001BB-Aw for ged-emacs-devel@m.gmane-mx.org; Mon, 11 Jul 2022 20:30:43 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49562) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oB3mN-0000TD-9R for emacs-devel@gnu.org; Mon, 11 Jul 2022 20:29:31 -0400 Original-Received: from mailscanner.iro.umontreal.ca ([132.204.25.50]:39480) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oB3mK-0008Pm-Hl for emacs-devel@gnu.org; Mon, 11 Jul 2022 20:29:29 -0400 Original-Received: from pmg2.iro.umontreal.ca (localhost.localdomain [127.0.0.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id C71E5805C8; Mon, 11 Jul 2022 20:29:24 -0400 (EDT) Original-Received: from mail01.iro.umontreal.ca (unknown [172.31.2.1]) by pmg2.iro.umontreal.ca (Proxmox) with ESMTP id 9D97A80539; Mon, 11 Jul 2022 20:29:23 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=iro.umontreal.ca; s=mail; t=1657585763; bh=c4YwOGqZi3+I0vMBZHWvqtFwW/LidmM9j9l15VgH4G0=; h=From:To:Cc:Subject:In-Reply-To:References:Date:From; b=lDjFFzW73XL9WOValSklrzkhvbBDGSNwRVMEVpbDOPZyfXI5Wx2NCu+t6bgZ0miEQ HfvvubHr0wWZt6GzWUs8ohX9S9Ys8mpN+4RvV6bdV4NBf9Ly2rHY8qFsXzc4uve0JD PiPbdiLNZilygqTZtfmbTgfwk0DIgofy1N7dJDAnwjNO9QnwxedpzBo6ej+Uh0dyg/ z467lN5LUdAJ5sQ5XpPy+q92Cgk6PNypjcXIEa+DkqKdvBLmbfiyZKwCJ3GdG2ZOyI Uc8/OysyMBT/hYobJetkcSGrgtael6P+48EMHgMS8C2aPK07Z6Adg2hamVH/J5AOMD fGAoROpEN4lyw== Original-Received: from pastel (unknown [45.72.196.165]) by mail01.iro.umontreal.ca (Postfix) with ESMTPSA id 60572120227; Mon, 11 Jul 2022 20:29:23 -0400 (EDT) In-Reply-To: <3c642f4d-471b-d6d2-8519-b4707e1193ba@yandex.ru> (Dmitry Gutov's message of "Tue, 12 Jul 2022 03:19:42 +0300") 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, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 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:292064 Archived-At: Dmitry Gutov [2022-07-12 03:19:42] wrote: > On 11.07.2022 22:14, Juri Linkov wrote: >>>> 1. Replace =E2=80=98looking-at=E2=80=99 with a call to the search func= tion, >>>> but keep it at point by prepending =E2=80=98\\=3D=E2=80=99 to the= regexp. >>>> Can it break a complex regexp? >>> >>> I suppose it can. Even a simple one (that has \\| inside without >>> a grouping). >> This is what the fix for xref successfully uses in bug#53758 >> with changes in perform-replace from bug#14013. (However, >> none of these variants is suitable for replacing another call >> of looking-at in isearch-search-and-update.) > > Right. Because xref basically uses literal matching, no alternations. > But it will break more complex cases. I can't see why "\\=3D\\(?:...\\)" would break anything, personally. Stefan