From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Michael Heerdegen Newsgroups: gmane.emacs.bugs Subject: bug#14013: 24.3.50; dired-isearch-filenames-regexp is matching text outside filenames Date: Tue, 06 Jun 2023 02:27:24 +0200 Message-ID: <87zg5da103.fsf@web.de> References: <87li9hk5e5.fsf@web.de> <87wqt1vd0o.fsf@mail.jurta.org> <87d2ut4mji.fsf@web.de> <87620lvavl.fsf@mail.jurta.org> <87zjxxsd6c.fsf@web.de> <87vc8ke4os.fsf@mail.jurta.org> <86zgmutwx9.fsf@mail.linkov.net> <87o83ab67d.fsf@web.de> <86r185520f.fsf@mail.linkov.net> <87czjn39yf.fsf@web.de> <86y2215rbn.fsf@mail.linkov.net> <87sfbar6j6.fsf@web.de> <86wn0m4fq0.fsf@mail.linkov.net> <87wn0lpkfm.fsf@web.de> <868rcz4vre.fsf@mail.linkov.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="11437"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Cc: Stefan Monnier , 14013@debbugs.gnu.org To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jun 06 02:28:28 2023 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1q6KYm-0002mq-Cn for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 06 Jun 2023 02:28:28 +0200 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1q6KYP-0008HR-Ds; Mon, 05 Jun 2023 20:28:05 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1q6KYN-0008Gv-Ep for bug-gnu-emacs@gnu.org; Mon, 05 Jun 2023 20:28:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1q6KYN-0001Fd-03 for bug-gnu-emacs@gnu.org; Mon, 05 Jun 2023 20:28:03 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1q6KYM-0000LG-Ej for bug-gnu-emacs@gnu.org; Mon, 05 Jun 2023 20:28:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Michael Heerdegen Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 06 Jun 2023 00:28:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 14013 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: patch Original-Received: via spool by 14013-submit@debbugs.gnu.org id=B14013.16860112581284 (code B ref 14013); Tue, 06 Jun 2023 00:28:02 +0000 Original-Received: (at 14013) by debbugs.gnu.org; 6 Jun 2023 00:27:38 +0000 Original-Received: from localhost ([127.0.0.1]:50546 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q6KXx-0000Kd-UB for submit@debbugs.gnu.org; Mon, 05 Jun 2023 20:27:38 -0400 Original-Received: from mout.web.de ([212.227.15.3]:37131) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1q6KXu-0000KP-Q1 for 14013@debbugs.gnu.org; Mon, 05 Jun 2023 20:27:36 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=web.de; s=s29768273; t=1686011245; x=1686616045; i=michael_heerdegen@web.de; bh=cGwuhkV//qHlHoHke9VVRIxiLYfzp2dK4/tgz7EjbDQ=; h=X-UI-Sender-Class:From:To:Cc:Subject:In-Reply-To:References:Date; b=ahPP7AFZ7ZHplWGwXiyKACEJMuFaLEnqtRc+25Cn8kSpnv/bu6KBHzaZD1v8w0AE/enuqya yp76ibHtqjdy2DwcvzGgya9IGmR8hF6f0Ud/v0ig/+XUvR/EjSQxo3qYJJEGL8h9bbtRPcGOK HJzKPeXtqhsaLkjFKSp+FfMrogxkxI4JWesnm5XCuYVW8HO5czdXl5i/y0Y3BbQ1j6DF/1fOp p56y3TZz4lUN8JbcpWkljt+2P7MvXAtgg+rP8CAJpqcyErglOgUG6igCsUGEMxR0kdsCnuoNk oqDEdxnfCAdYfT+k2dxPCTZJFucdAfN+qeSgRmY/GW32bF+rV5LQ== X-UI-Sender-Class: 814a7b36-bfc1-4dae-8640-3722d8ec6cd6 Original-Received: from drachen.dragon ([178.14.74.62]) by smtp.web.de (mrweb006 [213.165.67.108]) with ESMTPSA (Nemesis) id 1MnpL4-1qPevH2LQg-00pM7n; Tue, 06 Jun 2023 02:27:25 +0200 In-Reply-To: <868rcz4vre.fsf@mail.linkov.net> (Juri Linkov's message of "Sun, 04 Jun 2023 10:36:01 +0300") X-Provags-ID: V03:K1:bx/D3rPOvjL/Nu53XN1ajGAtMY1IhhxrHfPSdrv5j7qxuZgZ3Ko cq4h158BV4s69dkWhdHgIgw/u9tB0baa9kpGKyYl0XUCsTBwm558j1sWbrfMx+HqiaCHjCS BzowPnAAV979YXbJggFl4AaXfcGCfGt2oFau5pRdEZwbsbd2ECNa5i4mzOWlRwkXr0NyY6I oBHyvkfVoB1nD6pivfuGQ== UI-OutboundReport: notjunk:1;M01:P0:Y90V0btqhUg=;2arHDIrnHk0CPCMsYOu9sHGTbTT xFl/oo4elScfVdjL44A+vYHhSHUsO7K1pUZ+Ih00HIqVGDAeLlX3GYmB6UwCmjlipl96sd5dp YF3cBp2IKfnj0MXn/6oNmrXQ03vTNDn9iVxu0kmuIbcrD52la3nScV/yTF5k2q1xVxHxmDorO X5uj+ZvKI6ZFyPLYuREtwwfKSG0y/Le3EXE420RvhbI14F7DEwTOBkND8hMRFmKzFjEqvFTTh BtVgO4aBfcxmF7Y0TiFsvGEEozeY0ERVMsJKY3Blpu0G8Lg5kXj4m8zWgYXAgQP38rJblp4Ee JXpJrigcTd3OCYdck+dJrHlVBbtL/v2CHBfNXxxBVX70vSA9iVU35wKuIWaqxRVH/I7hR01C1 11AYhOYFHvfhyDVcjTOq7LatZI5IOMVQNfG/pYtpS78JYNmuKpUeXxy5hEi5kftqKyhlCbiJ3 YnTgb1vbERioxuCImdZgvzkOWxa9StYRFFm59xTUTfWRp8jdEMYz3jiXCY9E7CfU4/j2FEpv8 oXQTnXNGmOWUpUAAFGYKIGf/nm5Po+NDDB+sDqKnGEhjC9WPQpbAv9PtOeo8CJzZpkeAlp3Lf kO8LhHxpeYpMPPOM39hXBLcx5dWcCwfv//qv3k04oPRpIpzeFxogfXCLTG6ZduANQU+yzTje+ CsafKduuk/MZyKiKPgvSqy0BKpvOQs0wRa+LPyx8/lSBmDWPNwhMDPO5ooRfk6yqzus00bjO+ awYA/gt8j4QK8uSeHhTTCB/l2j0PTvWqpCu278bGaqA6a/Bp9XGs7myBXL9Cu7Ldf28QNlCM X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:263037 Archived-At: Juri Linkov writes: > >> > Second question: could we advice (local 'replace-search-function) and > >> > (local 'replace-re-search-function) instead of replacing the value (it > >> > might be nicer to users of other packages)? > >> > >> This looks nicer in theory. But in practice I expect to see a lot of > >> conflicts. > > > > What conflicts? > > Usual conflicts when two pieces of code are working simultaneously > on the same thing. So we need concrete examples to verify if > everything is correct. Not sure I understand. We would do this to get any control over conflicts at all (by using the different types of advices and the depth property). How would such examples behave currently, and why do you think changing the code to use advices would be more problematic? Currently we `setq' and so the last one completely overwrites everything conflicting. Isn't that a problem per se (at least it's the thing I want to mitigate). Michael.