From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: ndame via "Bug reports for GNU Emacs, the Swiss army knife of text editors" Newsgroups: gmane.emacs.bugs Subject: bug#53181: Live preview of regexp replace Date: Tue, 11 Jan 2022 13:28:54 +0000 Message-ID: References: <868rvmiqrj.fsf@mail.linkov.net> Reply-To: ndame 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="9693"; mail-complaints-to="usenet@ciao.gmane.io" Cc: 53181@debbugs.gnu.org, Augusto Stoffel To: Juri Linkov Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Tue Jan 11 15:21:07 2022 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 1n7I1L-0002KO-Jd for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 11 Jan 2022 15:21:07 +0100 Original-Received: from localhost ([::1]:34784 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1n7I1K-0007Cu-6c for geb-bug-gnu-emacs@m.gmane-mx.org; Tue, 11 Jan 2022 09:21:06 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:58672) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1n7HDv-0006jC-Dk for bug-gnu-emacs@gnu.org; Tue, 11 Jan 2022 08:30:04 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:33328) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1n7HDv-0002D3-3H for bug-gnu-emacs@gnu.org; Tue, 11 Jan 2022 08:30:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1n7HDu-0003tf-VV for bug-gnu-emacs@gnu.org; Tue, 11 Jan 2022 08:30:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: ndame Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Tue, 11 Jan 2022 13:30:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 53181 X-GNU-PR-Package: emacs Original-Received: via spool by 53181-submit@debbugs.gnu.org id=B53181.164190774414859 (code B ref 53181); Tue, 11 Jan 2022 13:30:02 +0000 Original-Received: (at 53181) by debbugs.gnu.org; 11 Jan 2022 13:29:04 +0000 Original-Received: from localhost ([127.0.0.1]:54462 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n7HCy-0003rb-04 for submit@debbugs.gnu.org; Tue, 11 Jan 2022 08:29:04 -0500 Original-Received: from mail-40140.protonmail.ch ([185.70.40.140]:63580) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1n7HCw-0003qc-16 for 53181@debbugs.gnu.org; Tue, 11 Jan 2022 08:29:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=protonmail.com; s=protonmail2; t=1641907735; bh=NcAoxGQwAKgP2PoLW0IssI4vlmh3AoIDEaTjIbwvRY8=; h=Date:To:From:Cc:Reply-To:Subject:Message-ID:In-Reply-To: References:From:To:Cc; b=ZLa7k4luSrHI4UbbYOgIxv4VSkofBEB58ite1sBg9vZS+UIp9zVusAdzuEJztRM1d LMpDzOu1CK6Dfs2V2YZceybOIw6iT7xJVH8q2QnZQ+2IlYjQcJ4MisLvvz0sUnPzuf qV+pIqUn2OMPzyZT2wAjNDnGfDNUgUilHk3/QdseU9vqp/acNp2MwgYvHGD0Vh3oKd x+hEA91ZayqcEQQp1wOH2GCWAaeLc/QHG50hWORfxrq0kgA/O8DPh4HaM2ghdZ0bS9 F7OkocZYg9zIlyp4WxMgK4U5XqxA68Q/9VMcYMHoAcLckLNgahK72L5QObj/N8TooL A/ikGOOvuXP3w== In-Reply-To: <868rvmiqrj.fsf@mail.linkov.net> 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" X-ACL-Warn: , ndame Xref: news.gmane.io gmane.emacs.bugs:223937 Archived-At: > This is exactly what Augusto is currently doing in bug#53126. I checked it and it's not the same. It says: " the highlighting and count of matches as one types a regexp or string to replace in `query-replace{-regexp}'." So it may do the first part, the highlighting of the regexp pattern while t= yping, but it does not seem to do the second part, that is showing the replacement= effects in the buffer immediately as the user types the replacement text or pattern= . The second part is just as important, because that shows if the actual repl= acement is correct or it needs some tweaking before starting replacing.