From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Stefan Monnier via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org> Newsgroups: gmane.emacs.help Subject: Re: Query replace question Date: Thu, 17 Mar 2022 14:49:40 -0400 Message-ID: <jwvtubw4dso.fsf-monnier+emacs@gnu.org> References: <20220317111952.zwm7bmvtsdnede7i.ref@Ergus> <20220317111952.zwm7bmvtsdnede7i@Ergus> Reply-To: Stefan Monnier <monnier@iro.umontreal.ca> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="27595"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:268pyGV3BQFJwjGGF3kA8QJpBE0= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Mar 17 19:55:05 2022 Return-path: <help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org> Envelope-to: geh-help-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 <help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org>) id 1nUvH6-00072B-BM for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 17 Mar 2022 19:55:04 +0100 Original-Received: from localhost ([::1]:49202 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from <help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org>) id 1nUvH4-00070g-6u for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 17 Mar 2022 14:55:02 -0400 Original-Received: from eggs.gnu.org ([209.51.188.92]:36132) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <geh-help-gnu-emacs@m.gmane-mx.org>) id 1nUvC2-0008Ul-Rd for help-gnu-emacs@gnu.org; Thu, 17 Mar 2022 14:49:50 -0400 Original-Received: from ciao.gmane.io ([116.202.254.214]:54744) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from <geh-help-gnu-emacs@m.gmane-mx.org>) id 1nUvC1-0001Hm-6c for help-gnu-emacs@gnu.org; Thu, 17 Mar 2022 14:49:50 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from <geh-help-gnu-emacs@m.gmane-mx.org>) id 1nUvBy-000AB2-3i for help-gnu-emacs@gnu.org; Thu, 17 Mar 2022 19:49:46 +0100 X-Injected-Via-Gmane: http://gmane.org/ Received-SPF: pass client-ip=116.202.254.214; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-Spam_score_int: -16 X-Spam_score: -1.7 X-Spam_bar: - X-Spam_report: (-1.7 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.249, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=no autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the GNU Emacs text editor <help-gnu-emacs.gnu.org> List-Unsubscribe: <https://lists.gnu.org/mailman/options/help-gnu-emacs>, <mailto:help-gnu-emacs-request@gnu.org?subject=unsubscribe> List-Archive: <https://lists.gnu.org/archive/html/help-gnu-emacs> List-Post: <mailto:help-gnu-emacs@gnu.org> List-Help: <mailto:help-gnu-emacs-request@gnu.org?subject=help> List-Subscribe: <https://lists.gnu.org/mailman/listinfo/help-gnu-emacs>, <mailto:help-gnu-emacs-request@gnu.org?subject=subscribe> Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" <help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org> Xref: news.gmane.io gmane.emacs.help:136643 Archived-At: <http://permalink.gmane.org/gmane.emacs.help/136643> Ergus [2022-03-17 12:19:52] wrote: > I am wondering if there is some functionality in vanilla to enable > dynamic match highlight during query replace or query-replace regex > while composing the regex? Similar to isearch lazy highlight, > regex-highlight or re-builder; but for query-replace and the rest of the > replace family? You can do the query&replace from Isearch: C-u C-s <regexp> M-C-% <replacement> RET In my world, this is the normal way to do a "query replace". I only invoked straight query-replace when I want to repeat a previous replacement. Stefan