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: Emacs manual nodes about text replacement Date: Sun, 16 Nov 2008 23:22:02 -0800 Message-ID: <002901c94885$30274520$0200a8c0@us.oracle.com> References: <005801c94752$053e9e50$0200a8c0@us.oracle.com><873ahrnte2.fsf@jurta.org><001b01c94854$fb91f830$0200a8c0@us.oracle.com> <87zljz9kfy.fsf@cyd.mit.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1226906548 25337 80.91.229.12 (17 Nov 2008 07:22:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 17 Nov 2008 07:22:28 +0000 (UTC) Cc: 'Juri Linkov' , emacs-devel@gnu.org To: "'Chong Yidong'" Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Nov 17 08:23:29 2008 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 1L1ySG-0007hT-QR for ged-emacs-devel@m.gmane.org; Mon, 17 Nov 2008 08:23:29 +0100 Original-Received: from localhost ([127.0.0.1]:42854 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L1yR7-0005Ft-RI for ged-emacs-devel@m.gmane.org; Mon, 17 Nov 2008 02:22:18 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1L1yR2-0005Fc-Ti for emacs-devel@gnu.org; Mon, 17 Nov 2008 02:22:12 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1L1yR1-0005FQ-7j for emacs-devel@gnu.org; Mon, 17 Nov 2008 02:22:12 -0500 Original-Received: from [199.232.76.173] (port=48616 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1L1yR1-0005FN-1q for emacs-devel@gnu.org; Mon, 17 Nov 2008 02:22:11 -0500 Original-Received: from acsinet11.oracle.com ([141.146.126.233]:26977) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1L1yR0-0003qh-MB for emacs-devel@gnu.org; Mon, 17 Nov 2008 02:22:10 -0500 Original-Received: from acsinet13.oracle.com (acsinet13.oracle.com [141.146.126.235]) by acsinet11.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id mAH7Mgrb000723 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK); Mon, 17 Nov 2008 07:22:43 GMT Original-Received: from acsmt700.oracle.com (acsmt700.oracle.com [141.146.40.70]) by acsinet13.oracle.com (Switch-3.3.1/Switch-3.3.1) with ESMTP id mAH7MJAs020694; Mon, 17 Nov 2008 07:22:20 GMT Original-Received: from dradamslap1 (/24.23.165.218) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 17 Nov 2008 07:21:43 +0000 X-Mailer: Microsoft Office Outlook 11 In-Reply-To: <87zljz9kfy.fsf@cyd.mit.edu> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.3350 Thread-Index: AclIWPreCSXuUI3PRvy4Ze0l9YABRAAKPXzw X-Source-IP: acsmt700.oracle.com [141.146.40.70] X-Auth-Type: Internal IP X-CT-RefId: str=0001.0A090209.49211B9E.0079:SCFSTAT928724,ss=1,fgs=0 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 1) 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:105745 Archived-At: > >> Recently Yidong rewrote many parts of the documentation, so > >> please refer to a newer version. > > > > Looking at the CVS version today, it seems to reflect the same > > structure. > > Your opening statement > The main node, Replace, starts by saying that you don't use global > search-and-replace that much in Emacs. > is not true, in the latest version of the manual anyway. Yes, this opening sentence: Global search-and-replace operations are not needed often in Emacs, but they are available. was changed to this in Emacs 23 (good): Emacs provides several commands for performing search-and-replace operations. So you can skip that first statement I made. AFAICT, the rest of my message is still pertinent. The main points: The presentation is backward and misleading. Emphasize query-replace, not unconditional replace. Present the information top-down, not bottom up. Give an overview of what you can do before the details about how to do it. Make it clear that all of the fancy stuff applies to query-replace too, not just to unconditional replace. Please see the original message for details.