From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Juri Linkov Newsgroups: gmane.emacs.bugs Subject: bug#52558: Option for easier typing of regexps Date: Sun, 23 Jan 2022 20:09:11 +0200 Organization: LINKOV.NET Message-ID: <867daquxx4.fsf@mail.linkov.net> References: <86v8zkkgxn.fsf@mail.linkov.net> <8635moe8z1.fsf@mail.linkov.net> <86wnk0ctxp.fsf@mail.linkov.net> <87tudvj1cw.fsf@gnus.org> <86y237zja6.fsf@mail.linkov.net> <87wniq8w8n.fsf@gnus.org> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="18464"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (x86_64-pc-linux-gnu) Cc: ndame , 52558@debbugs.gnu.org To: Lars Ingebrigtsen Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Sun Jan 23 19:26:40 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 1nBhZY-0004dk-2E for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 23 Jan 2022 19:26:40 +0100 Original-Received: from localhost ([::1]:38526 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1nBhZW-0007Yt-7Q for geb-bug-gnu-emacs@m.gmane-mx.org; Sun, 23 Jan 2022 13:26:38 -0500 Original-Received: from eggs.gnu.org ([209.51.188.92]:40860) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1nBhXz-0007Xn-8L for bug-gnu-emacs@gnu.org; Sun, 23 Jan 2022 13:25:11 -0500 Original-Received: from debbugs.gnu.org ([209.51.188.43]:48322) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1nBhXy-0005hW-Sl for bug-gnu-emacs@gnu.org; Sun, 23 Jan 2022 13:25:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1nBhXy-0003zp-O8 for bug-gnu-emacs@gnu.org; Sun, 23 Jan 2022 13:25:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Juri Linkov Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Sun, 23 Jan 2022 18:25:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 52558 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: moreinfo Original-Received: via spool by 52558-submit@debbugs.gnu.org id=B52558.164296228915303 (code B ref 52558); Sun, 23 Jan 2022 18:25:02 +0000 Original-Received: (at 52558) by debbugs.gnu.org; 23 Jan 2022 18:24:49 +0000 Original-Received: from localhost ([127.0.0.1]:41219 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nBhXl-0003yj-GH for submit@debbugs.gnu.org; Sun, 23 Jan 2022 13:24:49 -0500 Original-Received: from relay5-d.mail.gandi.net ([217.70.183.197]:47277) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1nBhXe-0003y4-P6 for 52558@debbugs.gnu.org; Sun, 23 Jan 2022 13:24:43 -0500 Original-Received: (Authenticated sender: juri@linkov.net) by mail.gandi.net (Postfix) with ESMTPSA id CBC321C0002; Sun, 23 Jan 2022 18:24:34 +0000 (UTC) In-Reply-To: <87wniq8w8n.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 23 Jan 2022 13:36:24 +0100") 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:224953 Archived-At: >>>> - (isearch-regexp-function (or delimited-flag >>>> + (isearch-regexp-function (or replace-regexp-function >>>> + delimited-flag >>>> (and replace-char-fold >>> >>> Re-skimming this thread, I think these extensions make sense, so perhaps >>> you should just push them? (With a NEWS item, I guess.) >> >> This patch was pushed, but does it really need a NEWS item? >> It was intended as a basis for a new user-facing feature >> that could be now implemented and described in NEWS. > > What was the new user-facing feature? I thought the point of this was > to just allow users to implement their own replace-regexp-function and > have it work more consistently, which your change fixed... This means that after adding a NEWS item this feature request can be closed?