From: "Robert J. Chassell" <bob@rattlesnake.com>
Subject: Re: follow mode for occur
Date: Sat, 5 Jun 2004 07:56:09 -0400 (EDT) [thread overview]
Message-ID: <m1BWZmT-000UNSC@rattlesnake.com> (raw)
In-Reply-To: <200406041841.i54IfIU5017651@amrm2.ics.uci.edu> (message from Dan Nicolaescu on Fri, 4 Jun 2004 11:41:18 -0700)
Today's CVS snapshot, Sat, 2004 Jun 5 10:53 UTC
GNU Emacs 21.3.50.41 (i686-pc-linux-gnu, GTK+ Version 2.2.4)
I just tried Dan Nicolaescu's new follow minor mode for occur. In a
short test, it works fine for both *Occur* and *compilation* buffers.
Should this mode be on by default?
I think so. I really like this. I don't know how non-programmers who
first use Emacs will respond, but I think they will like it, too.
I suppose a menu entry is a good idea, too. I don't use the menus so
my only thought about them is that we should make sure they have good
human factors.
Presumably occur and its follow mode fit into `Tools' along with grep
and multi-occur. Or perhaps a human factors analysis will put them
into `Edit' along with isearch. On thinking more about this, I think
they should all go into `Edit'.
Perhaps the listing could add `Search and List' between the existing
`Search' and `Replace' entries, like this:
Search ->
Search and List ->
Replace ->
After all, these capabilities are all various forms of navigation
used in editing:
* search and list within a single `file' (that is how many people
think of buffers) for occur and occur follow mode
* search and list within the buffers you have visited for
multi-occur
* search and list within a set of files for grep
By the way, it looks to me that isearch should come before string
search in the `Edit -> Search' menu. It is easy to learn isearch and
easy to switch from string search to isearch if you already know
string search. So the better interface should come first. Put
`string search' in a sub-sub-menu.
--
Robert J. Chassell Rattlesnake Enterprises
As I slowly update it, bob@rattlesnake.com
I rewrite a "What's New" segment for http://www.rattlesnake.com
next prev parent reply other threads:[~2004-06-05 11:56 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-27 0:35 follow mode for occur Dan Nicolaescu
2004-05-27 15:16 ` Sun Yi Ming
2004-05-27 16:48 ` Dan Nicolaescu
2004-05-28 8:43 ` Emacs-devel list IS slow [was Re: follow mode for occur] Kim F. Storm
2004-05-29 14:16 ` Eli Zaretskii
2004-05-28 10:37 ` follow mode for occur Sun Yi Ming
2004-05-28 8:47 ` Juri Linkov
2004-05-28 18:56 ` Dan Nicolaescu
2004-06-04 18:41 ` Dan Nicolaescu
2004-06-04 19:18 ` David Kastrup
2004-06-05 11:56 ` Robert J. Chassell [this message]
2004-05-28 12:44 ` Stephen Eglen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m1BWZmT-000UNSC@rattlesnake.com \
--to=bob@rattlesnake.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.