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: isearch-forward and Info-search Date: Fri, 11 Mar 2005 06:40:40 -0800 Message-ID: References: <877jkfq7v0.fsf@jurta.org> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1110552294 18156 80.91.229.2 (11 Mar 2005 14:44:54 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 11 Mar 2005 14:44:54 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Mar 11 15:44:53 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D9lKX-0003pg-GN for ged-emacs-devel@m.gmane.org; Fri, 11 Mar 2005 15:41:33 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D9lZd-0006Nw-9K for ged-emacs-devel@m.gmane.org; Fri, 11 Mar 2005 09:57:09 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D9lZM-0006Km-Uw for emacs-devel@gnu.org; Fri, 11 Mar 2005 09:56:53 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D9lZJ-0006IZ-Cb for emacs-devel@gnu.org; Fri, 11 Mar 2005 09:56:51 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D9lZI-0006H3-Q0 for emacs-devel@gnu.org; Fri, 11 Mar 2005 09:56:48 -0500 Original-Received: from [141.146.126.230] (helo=agminet03.oracle.com) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1D9lJq-0002V0-GE for emacs-devel@gnu.org; Fri, 11 Mar 2005 09:40:50 -0500 Original-Received: from agminet03.oracle.com (localhost [127.0.0.1]) by agminet03.oracle.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id j2BEelrN030950; Fri, 11 Mar 2005 06:40:47 -0800 Original-Received: from rgmsgw300.us.oracle.com (rgmsgw300.us.oracle.com [138.1.191.49]) by agminet03.oracle.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id j2BEej5W030918; Fri, 11 Mar 2005 06:40:46 -0800 Original-Received: from rgmsgw300.us.oracle.com (localhost [127.0.0.1]) by rgmsgw300.us.oracle.com (Switch-3.1.4/Switch-3.1.0) with ESMTP id j2BEejsG000651; Fri, 11 Mar 2005 07:40:45 -0700 Original-Received: from dradamslap (dhcp-amer-whq-csvpn-gw3-141-144-82-173.vpn.oracle.com [141.144.82.173]) by rgmsgw300.us.oracle.com (Switch-3.1.4/Switch-3.1.0) with SMTP id j2BEegke000631 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Fri, 11 Mar 2005 07:40:44 -0700 Original-To: "Juri Linkov" X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook IMO, Build 9.0.6604 (9.0.2911.0) In-reply-to: <877jkfq7v0.fsf@jurta.org> X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441 Importance: Normal 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 X-MailScanner-To: ged-emacs-devel@m.gmane.org Xref: news.gmane.org gmane.emacs.devel:34472 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:34472 > Would you like it if isearch failed before proceeding to the > next Info node? > > I would. I suggested this long ago. It should first wrap, as Richard > suggested. After the entire Info node has been searched, it should > fail. A subsequent invocation should continue through the manual. > IOW, isearch the node completely first (wrapping), then inform the > user that there are no more occurrences in the node, then continue > on to other nodes. IMO, this behavior is too confusing. I agree, and I don't know why I suggested here to first wrap. In fact, what you describe was what I suggested originally: > But it would be better if > normal C-s isearch searched through multiple nodes as well. I like being able to confine an isearch to the current node. Currently, I can use `s' for global search and `C-s' (or `C-M-s') for local (node) search. So, to me, it would be desirable to have some indication that the end of the current node was reached without finding another occurrence of the string - e.g. "Failing isearch in node Foo: bar". Except for being able to overwrap isearch in the node (no great loss), this would give the advantages of both approaches (local and global search).... IOW, why not have two levels of isearch "failure": 1) no more in the current node, 2) no more in the current Info "manual"?