From: Juri Linkov <juri@jurta.org>
To: Alan Mackenzie <acm@muc.de>
Cc: Lennart Borgman <lennart.borgman@gmail.com>,
rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Isearch in dired
Date: Sat, 08 Nov 2008 19:07:55 +0200 [thread overview]
Message-ID: <87zlkajgos.fsf@jurta.org> (raw)
In-Reply-To: <20081108122354.GB3616@muc.de> (Alan Mackenzie's message of "Sat, 8 Nov 2008 12:23:54 +0000")
>> > 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.
>
> ..., except you'd have to move point into that column to start.
Most of the time point already is on file names, and moving it away is
very easy.
>> It is a nice idea if you know what is going on, but how do you tell
>> the user what is going on? Changing the prompt is one possibility, but
>> it is maybe not enough?
Changing the prompt is not a bad idea. We can display the prompt as e.g.
Filename I-search:
> How about highlighting the file column (or lowlighting the rest of the
> window) when you press C-\(M-\)?[rs]?
This will cause almost the same horrible visual effect as typing `C-M-s .'
;-)
>> (This reminds me again of that the search part of the menus in Emacs
>> should include all search commands that comes with Emacs. And there
>> should be an easy way to add other search commands there too.)
Maybe in a dired buffer the `Search' menu should duplicate search-related
menu items from `Operate' and `Immediate' submenus.
--
Juri Linkov
http://www.jurta.org/emacs/
next prev parent reply other threads:[~2008-11-08 17:07 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 [this message]
2008-11-09 0:26 ` Richard M. Stallman
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=87zlkajgos.fsf@jurta.org \
--to=juri@jurta.org \
--cc=acm@muc.de \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman@gmail.com \
--cc=rms@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.
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).