From: Miles Bader <miles@gnu.org>
Subject: Re: isearch-whole-buffer?
Date: Sun, 26 Mar 2006 11:07:40 +0900 [thread overview]
Message-ID: <87odzudklv.fsf@catnip.gol.com> (raw)
In-Reply-To: <44ydndg4Yss-VbjZnZ2dnUVZ_tqdnZ2d@mcgill.ca> (xyblor's message of "Sat, 25 Mar 2006 17:48:13 -0500")
xyblor <fake@invalid.email> writes:
> 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
I find the Emacs method far more natural than the search-whole-buffer
method -- it's extremely confusing if a search _can't_ fail because it
just automatically wraps.
In other words, the Emacs method gives you more easily usable
information about your search. To find out if you've reached the last
occurance of a string in an "auto wrap" system, you've got to always
note the position of your last match, and manually compare to the
position after hitting search, which is quite annoying in practice.
The fact that Emacs basically _does_ give you the "whole buffer"
functionality with just one more repetition of the search key seems like
a pretty good way to satisfy both scenarios with a minimum of fuss.
-Miles
--
`...the Soviet Union was sliding in to an economic collapse so comprehensive
that in the end its factories produced not goods but bads: finished products
less valuable than the raw materials they were made from.' [The Economist]
next prev parent reply other threads:[~2006-03-26 2:07 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-24 15:10 isearch-whole-buffer? xyblor
2006-03-24 16:09 ` isearch-whole-buffer? Kevin Rodgers
2006-03-24 16:58 ` isearch-whole-buffer? Kevin Rodgers
[not found] ` <mailman.19.1143219602.14013.help-gnu-emacs@gnu.org>
2006-03-25 18:42 ` isearch-whole-buffer? xyblor
2006-03-25 20:56 ` isearch-whole-buffer? B. T. Raven
2006-03-25 22:48 ` isearch-whole-buffer? xyblor
2006-03-25 23:34 ` isearch-whole-buffer? Vin Shelton
2006-03-26 2:07 ` Miles Bader [this message]
2006-03-26 10:42 ` isearch-whole-buffer? Peter Dyballa
2006-03-26 1:02 ` isearch-whole-buffer? Johan Bockgård
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87odzudklv.fsf@catnip.gol.com \
--to=miles@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).