From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: [LONG] Some thougths and a patch for the search menu-bar functions
Date: 11 Sep 2002 22:46:01 +0200 [thread overview]
Message-ID: <5xn0qop852.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <20020910084203.80798.qmail@web11508.mail.yahoo.com>
Damien Terrier <damien_terrier@yahoo.com> writes:
> The most significant change was in the organisation of the search
> functions. Four items in the last sub-menu is enough and it is much
> easier to click on the right one. That's what I don't like in the old
> menu, it starts to be a bit populated. Then, I divided in two and
> then, in two again. That's why the new version asks "Interactive
> Search or Non Interactive Search ?", then "forward or backwards ?"
> then, the choice for one of four item "Search/Repeat Search // Search
> Regepx/Repeat Search Regexp".
I don't use the menus for searches, but I tend to agree that your
approach makes more sense that the current mess (IMHO).
However, your menu strings seems overly verbose to me.
Here is a your proposed menu structure:
Edit
-> Search and Replace
-> Incremental Search
-> Forward
-> I-Search Forward ...
-> I-Search Regexp Forward ...
-> Backwards
-> I-Search Backwards ...
-> I-Search Regexp Backwards ...
-> Non-Incremental Search
-> Forward
-> Search Forward ...
-> Search Regexp Forward ...
-> Backwards
-> Search Backwards ...
-> Search Regexp Backwards ...
-> Replace
-> Replace ...
-> Replace regexp ...
-> Search and replace in tagged files
-> Search in all tagged files
-> Replace in all tagged files
-> Continue Tag Search/Replace
I think this can be further reorganized and simplified:
Edit
-> Search
-> Incremental
-> Forward
-> String ...
-> Regexp ...
-> Backwards
-> String ...
-> Regexp ...
-> Non-Incremental
-> Forward
-> String ...
-> Regexp ...
-> Backwards
-> String ...
-> Regexp ...
-> In tagged files
-> Replace
-> String ...
-> Regexp ...
-> In all tagged files
-> Continue Next Tag
I think this is better in line with many other applications which
separate Search and Replace into two items on the Edit menu.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-09-11 20:46 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-09-10 8:42 [LONG] Some thougths and a patch for the search menu-bar functions Damien Terrier
2002-09-10 11:36 ` Robert J. Chassell
2002-09-10 19:30 ` Thien-Thi Nguyen
2002-09-10 11:47 ` Robert J. Chassell
2002-09-10 12:24 ` Robert J. Chassell
2002-09-11 1:13 ` Miles Bader
2002-09-11 20:46 ` Kim F. Storm [this message]
2002-09-12 16:41 ` Richard Stallman
2002-09-12 21:26 ` Kim F. Storm
2002-09-13 7:40 ` Urban Engberg
2002-09-13 19:33 ` Richard Stallman
2002-09-15 22:40 ` Kim F. Storm
2002-09-16 13:43 ` Kai Großjohann
2002-09-17 15:53 ` Richard Stallman
2002-09-17 19:14 ` Damien Terrier
2002-09-18 17:26 ` Richard Stallman
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=5xn0qop852.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@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 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.