From: "Richard M. Stallman" <rms@gnu.org>
To: Juri Linkov <juri@jurta.org>
Cc: emacs-devel@gnu.org
Subject: Re: Isearch in dired
Date: Sat, 08 Nov 2008 19:26:25 -0500 [thread overview]
Message-ID: <E1Kyy8H-00016m-39@fencepost.gnu.org> (raw)
In-Reply-To: <87d4h6mphd.fsf@jurta.org> (message from Juri Linkov on Sat, 08 Nov 2008 12:59:38 +0200)
I think the most convenient default behavior would be context-dependent,
i.e. match only file names when point is on the file name column - where
point stays most of the time: after opening a dired buffer and through
dired operations including navigation. So it would be natural to do the
same for isearch - never let point leave the file name column.
To search of the entire buffer, the user can move point outside the
file name column. Since this need is very rare, there's no hassle.
That sounds quite convenient. If the prompt says "File name Isearch"
when appropriate, people will understand what's going on.
next prev parent reply other threads:[~2008-11-09 0:26 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-08 9:56 Isearch in dired Richard M. Stallman
2008-11-08 10:59 ` Juri Linkov
2008-11-08 11:33 ` Lennart Borgman
2008-11-08 12:23 ` Alan Mackenzie
2008-11-08 15:22 ` Lennart Borgman
2008-11-08 17:07 ` Juri Linkov
2008-11-09 0:26 ` Richard M. Stallman [this message]
2008-11-09 21:57 ` Juri Linkov
2008-11-08 12:19 ` Alan Mackenzie
2008-11-08 17:08 ` Juri Linkov
2008-11-08 14:10 ` Chong Yidong
2008-11-08 16:05 ` joakim
2008-11-08 17:27 ` Juri Linkov
2008-11-08 17:17 ` Juri Linkov
2008-11-09 0:26 ` Richard M. Stallman
2008-11-08 21:57 ` Lazy " Juri Linkov
2008-11-09 20:54 ` recursive-edit in Isearch Juri Linkov
2008-11-09 21:09 ` Occur in Word Isearch Juri Linkov
2008-11-13 15:29 ` Chong Yidong
2008-11-13 15:30 ` Lazy Isearch in dired Chong Yidong
2008-11-13 15:32 ` Chong Yidong
2008-11-13 16:30 ` Juri Linkov
2008-11-13 17:07 ` Chong Yidong
2008-11-09 14:22 ` Chong Yidong
2008-11-09 15:08 ` Stefan Monnier
2008-11-09 17:59 ` Juri Linkov
2008-11-11 22:55 ` Chong Yidong
2008-11-12 2:59 ` Stefan Monnier
2008-11-12 11:59 ` René Kyllingstad
2008-11-12 15:13 ` Drew Adams
2008-11-12 15:53 ` Richard M. Stallman
2008-11-12 7:55 ` Juri Linkov
2008-11-12 15:08 ` Chong Yidong
2008-11-13 16:57 ` Juri Linkov
2008-11-16 22:22 ` Juri Linkov
2008-11-10 3:11 ` Richard M. Stallman
2008-11-11 21:35 ` Juri Linkov
-- strict thread matches above, loose matches on Subject: below --
2007-08-08 3:05 propose: dired-isearch.el --- isearch in Dired William Xu
2007-08-08 18:46 ` Stefan Monnier
2007-08-08 22:54 ` Juri Linkov
2008-07-23 20:34 ` Juri Linkov
2008-07-24 6:41 ` Mathias Dahl
2008-07-25 0:32 ` Juri Linkov
2008-07-24 13:53 ` Stefan Monnier
2008-07-24 15:52 ` Drew Adams
2008-07-24 17:20 ` Stefan Monnier
2008-07-25 0:33 ` Juri Linkov
2008-07-25 0:40 ` Lennart Borgman (gmail)
2008-07-29 15:45 ` Juri Linkov
2008-07-29 17:56 ` Stefan Monnier
2008-07-30 14:29 ` Juri Linkov
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=E1Kyy8H-00016m-39@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=juri@jurta.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).