From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: Info-search-isearch Date: Mon, 21 Feb 2005 15:47:02 -0800 Message-ID: <200502212347.j1LNl4AH007049@scanner2.ics.uci.edu> References: <200502211754.j1LHs9AH027463@scanner2.ics.uci.edu> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1109031273 25043 80.91.229.2 (22 Feb 2005 00:14:33 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 22 Feb 2005 00:14:33 +0000 (UTC) Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Tue Feb 22 01:14:32 2005 Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1D3Nh0-0002wg-48 for ged-emacs-devel@m.gmane.org; Tue, 22 Feb 2005 01:14:22 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D3Ny2-0000ga-Ri for ged-emacs-devel@m.gmane.org; Mon, 21 Feb 2005 19:31:58 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1D3Nu1-0005Tb-D0 for emacs-devel@gnu.org; Mon, 21 Feb 2005 19:27:49 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1D3Ntz-0005S7-KK for emacs-devel@gnu.org; Mon, 21 Feb 2005 19:27:48 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1D3NqP-0004Kb-Dc for emacs-devel@gnu.org; Mon, 21 Feb 2005 19:24:05 -0500 Original-Received: from [128.195.1.36] (helo=scanner2.ics.uci.edu) by monty-python.gnu.org with esmtp (Exim 4.34) id 1D3NH5-0003mZ-KR for emacs-devel@gnu.org; Mon, 21 Feb 2005 18:47:35 -0500 Original-Received: from vino.ics.uci.edu (dann@vino.ics.uci.edu [128.195.11.198]) by scanner2.ics.uci.edu (8.12.10/8.12.10) with ESMTP id j1LNl4AH007049 for ; Mon, 21 Feb 2005 15:47:04 -0800 (PST) Original-To: emacs-devel@gnu.org Original-Lines: 33 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-96.69, required 5, MSGID_FROM_MTA_SHORT, USER_IN_WHITELIST) 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: main.gmane.org gmane.emacs.devel:33704 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:33704 "Drew Adams" writes: > > Currently only regexp isearch invoked with M-C-s can use > `Info-search' > > and search through multiple Info nodes. But it would be better if > > normal C-s isearch searched through multiple nodes as well. > > This would be actually great, it would match the behavior of standalone > info (which, IMO, is much better). > > Is there any reason not to check this code in? > > 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). Without such a local-failure > indication, you would have to (perhaps unwittingly) continue the search to > another node, and then use `l' to get back where you were. > > IOW, why not have two levels of isearch "failure": 1) no more in the current > node, 2) no more in the current Info "manual"? The behavior of what you propose is different from either the current C-s behavior in an emacs info buffer or in standalone info. The message I was replying to was just asking to make the C-s behavior the same in an info buffer and standalone info, and allow to the user to choose one or the other via a customizable variable.