From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#31796: 27.1; dired-do-find-regexp-and-replace fails to find multiline regexps Date: Tue, 24 Nov 2020 18:35:11 +0200 Message-ID: <83lfequ30g.fsf@gnu.org> References: <10120030-8b8d-b702-add4-8f099f934ed5@chalmers.se> <831rgivl7l.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="21461"; mail-complaints-to="usenet@ciao.gmane.io" Cc: abela@chalmers.se, 31796@debbugs.gnu.org To: Dmitry Gutov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Nov 24 17:53:02 2020 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 1khbYs-0005Sb-OC for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 24 Nov 2020 17:53:02 +0100 Original-Received: from localhost ([::1]:54122 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1khbYr-0003Kn-P8 for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 24 Nov 2020 11:53:01 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:49910) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1khbIQ-00040n-7S for bug-gnu-emacs@gnu.org; Tue, 24 Nov 2020 11:36:02 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:49510) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1khbIP-0003UL-Vc for bug-gnu-emacs@gnu.org; Tue, 24 Nov 2020 11:36:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1khbIP-0000aJ-SJ for bug-gnu-emacs@gnu.org; Tue, 24 Nov 2020 11:36:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 24 Nov 2020 16:36:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 31796 X-GNU-PR-Package: emacs Original-Received: via spool by 31796-submit@debbugs.gnu.org id=B31796.16062357242204 (code B ref 31796); Tue, 24 Nov 2020 16:36:01 +0000 Original-Received: (at 31796) by debbugs.gnu.org; 24 Nov 2020 16:35:24 +0000 Original-Received: from localhost ([127.0.0.1]:32823 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1khbHn-0000ZT-St for submit@debbugs.gnu.org; Tue, 24 Nov 2020 11:35:24 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:59662) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1khbHl-0000ZE-EY for 31796@debbugs.gnu.org; Tue, 24 Nov 2020 11:35:21 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]:47191) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1khbHe-0003FK-Jw; Tue, 24 Nov 2020 11:35:14 -0500 Original-Received: from [176.228.60.248] (port=2776 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1khbHd-0000eV-AM; Tue, 24 Nov 2020 11:35:13 -0500 In-Reply-To: (message from Dmitry Gutov on Tue, 24 Nov 2020 17:43:53 +0200) 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" Xref: news.gmane.io gmane.emacs.bugs:194092 Archived-At: > Cc: 31796@debbugs.gnu.org > From: Dmitry Gutov > Date: Tue, 24 Nov 2020 17:43:53 +0200 > > We've been aware of it for at least two years now. So what are we, then, > negligent, careless, or incompetent? Busy. That, and the fact that no one came up with a clear idea of how to fix this (at least IIRC). > If you're saying we can't afford to break even a minor feature like > this, I don't think there are a lot of options. We should try not to break any features, yes. AFAIK, no one has yet claimed that this cannot be fixed. So the decision whether we can or cannot stay with this broken doesn't have to be made yet.