From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Vin Shelton Newsgroups: gmane.emacs.help Subject: Re: isearch-whole-buffer? Date: Sat, 25 Mar 2006 18:34:22 -0500 Organization: The XEmacs Development Team Message-ID: References: <-N-dnckRSdxBlrnZnZ2dnUVZ_vudnZ2d@mcgill.ca> <44ydndg4Yss-VbjZnZ2dnUVZ_tqdnZ2d@mcgill.ca> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1143487667 19851 80.91.229.2 (27 Mar 2006 19:27:47 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 27 Mar 2006 19:27:47 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Mon Mar 27 21:27:46 2006 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FNxN7-0006Xh-J9 for geh-help-gnu-emacs@m.gmane.org; Mon, 27 Mar 2006 21:27:25 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FNxN6-0000Jt-Ug for geh-help-gnu-emacs@m.gmane.org; Mon, 27 Mar 2006 14:27:25 -0500 Original-Path: shelby.stanford.edu!newsfeed.stanford.edu!postnews.google.com!news3.google.com!border1.nntp.dca.giganews.com!nntp.giganews.com!local01.nntp.dca.giganews.com!nntp.rcn.net!news.rcn.net.POSTED!not-for-mail Original-NNTP-Posting-Date: Sat, 25 Mar 2006 17:34:26 -0600 Original-Newsgroups: gnu.emacs.help Cancel-Lock: sha1:q4DK9W594exBkk2Ksdg2n7ywnaI= Original-Lines: 50 Original-NNTP-Posting-Host: 209.6.229.49 Original-X-Trace: sv3-pbfj1gMg63RcBBtwxgLLPFsQXiGCU9ASlkH/ZM/IGQrZtJHUwss7GRN6h2PoO2U6JaUqts5ptKhpZy7!Rp7vN+SEh8gdjdSoRbNLEQwuobwHvzrfjkMnTqMM1PeW1lLqTk3FsmUgXsM= Original-X-Complaints-To: abuse@rcn.net X-DMCA-Complaints-To: abuse@rcn.net X-Abuse-and-DMCA-Info: Please be sure to forward a copy of ALL headers X-Abuse-and-DMCA-Info: Otherwise we will be unable to process your complaint properly X-Postfilter: 1.3.32 Original-Xref: shelby.stanford.edu gnu.emacs.help:138381 Original-To: help-gnu-emacs@gnu.org X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:34018 Archived-At: xyblor writes: > B. T. Raven wrote: > >> I'm having trouble imagining why C-s xxxxxxxxxx... and then C-s again to >> force wrapping to the beginning of the buffer doesn't work for you. Even >> if the search string (xxxxxx...) is very long, you don't have to backspace >> to the beginning to return to the mark. You can just C-x C-x. No? > > Being forced to wrap the search is inconvenient when you don't know > how to spell what you are looking for, and you have to press C-s every > time you want to try a different spelling. It's also inconvenient to > start a search when the point is at the end of the buffer, because no > matter what you're looking for, you'll have to press C-s again, and > you don't know you've typed enough characters. > > There's also a more general design issue at play here: it seems to me > that most of the time, when a person initiates a search, s/he wants to > answer the question "where in this buffer will I find this string?" > not "where will I find this string in the portion of the buffer that > is below/above the point?". I find Firefox's "find" (control-f) to be > more sensible in this regard, and I am surprised that in the long > history of Emacs' development, nobody seems to have shared this view; > to such an extent that not only is there no built in function or > variable to enable searching the whole buffer by default, there isn't > even a convenient workaround. I realize it's a minor point, but given > Emacs' extensible nature, I'm supposed to bend it to my will, right? > Or am I just out to lunch on this? It seems to me that Firefox and emacsen are fundamentally different in the sense that a emacs (or any screen-based editor) has a sense of 'point' - where you are right now, vs. a browser's sense that you're viewing a webpage. In the former case it makes sense to search from where you are, but in the latter case it makes more sense to search from the start of the entire webpage. ... at least IMO. As to your problem - is it too cumbersome to type M-< before you type C-s? This does have the disadvantage that C-g doesn't work in exactly the same way, but your original point is still in the mark ring. (Personally, I thought Kevin's advice solution was more elegant than my proposed solution, but sometimes there's a value to explicitness and tastes vary, so perhaps you'd prefer my suggestion.) BTW, if you don't know exactly what you're searching for, isearch-forward-regexp (bound to M-C-s) may help. My $.02. - Vin Shelton