From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Drew Adams" Newsgroups: gmane.emacs.devel Subject: RE: should query-replace-regexp-eval be in the manual? Date: Sun, 15 Apr 2007 15:55:14 -0700 Message-ID: References: <4622A327.5060705@gmail.com> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1176677794 6169 80.91.229.12 (15 Apr 2007 22:56:34 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sun, 15 Apr 2007 22:56:34 +0000 (UTC) To: "Emacs-Devel" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Apr 16 00:56:27 2007 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1HdDdw-000098-AP for ged-emacs-devel@m.gmane.org; Mon, 16 Apr 2007 00:56:24 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HdDiT-00075H-NN for ged-emacs-devel@m.gmane.org; Sun, 15 Apr 2007 19:01:05 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HdDhv-0006IR-Pm for emacs-devel@gnu.org; Sun, 15 Apr 2007 19:00:32 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HdDhu-0006Fh-CS for emacs-devel@gnu.org; Sun, 15 Apr 2007 19:00:31 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HdDhu-0006FE-7C for emacs-devel@gnu.org; Sun, 15 Apr 2007 19:00:30 -0400 Original-Received: from agminet01.oracle.com ([141.146.126.228]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1HdDdL-0005R9-Sy for emacs-devel@gnu.org; Sun, 15 Apr 2007 18:55:48 -0400 Original-Received: from rgmgw1.us.oracle.com (rgmgw1.us.oracle.com [138.1.186.110]) by agminet01.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id l3FMtiS8019037 for ; Sun, 15 Apr 2007 17:55:44 -0500 Original-Received: from acsmt351.oracle.com (acsmt351.oracle.com [141.146.40.151]) by rgmgw1.us.oracle.com (Switch-3.2.4/Switch-3.1.7) with ESMTP id l3FMdfGs023361 for ; Sun, 15 Apr 2007 16:55:44 -0600 Original-Received: from dhcp-amer-whq-csvpn-gw3-141-144-81-24.vpn.oracle.com by acsmt350.oracle.com with ESMTP id 2615829071176677729; Sun, 15 Apr 2007 15:55:29 -0700 X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-Reply-To: <4622A327.5060705@gmail.com> Importance: Normal X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3028 X-Whitelist: TRUE X-Whitelist: TRUE X-Brightmail-Tracker: AAAAAQAAAAI= X-detected-kernel: Linux 2.4-2.6 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:69476 Archived-At: > >> Basically it has been my experience that query-replace-regexp-eval > >> is a nice idea, but in practice quite unusable. \, achieves a > >> similar purpose but with a much more convenient interface. > > > > To get back to the original question: since \, has all of the > > functionality of query-replace-regexp-eval with a more convenient > > interface, query-replace-regexp-eval could be considered obsolete or > > at least obscure. > > > > Since we tell people how to do the same thing more flexibly with \, I > > don't think that query-replace-regexp-eval deserves a place in the > > manual. It would be a lot of additional explanation without any > > conceivable benefit to the user. > > After reading this I think it would be a good idea to tell in the doc > string for query-replace-regexp-eval to use query-replace-regexp + \ > instead. There is never any sense in saying to use something else instead, unless it has truly been deprecated. The question is whether this has a use on its own, which would keep it from being deprecated. In that case, the doc string should explain what that use is. I think that it probably does merit keeping. It has the advantage of simpler syntax, for the use case to which it applies: replacement by an evaled sexp (only). IOW: - `query-regexp-replace' is best all 'round: flexible, general - `query-regexp-replace-eval' has a simpler UI when you are using only eval-replacement - no need to use `\,...'.