unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Lennart Borgman (gmail)" <lennart.borgman@gmail.com>
To: Drew Adams <drew.adams@oracle.com>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Search menu   [was: Change grep -> lgrep, rgrep in Tools menu?]
Date: Fri, 21 Mar 2008 21:41:54 +0100	[thread overview]
Message-ID: <47E41D92.9050002@gmail.com> (raw)
In-Reply-To: <006501c8650b$316298d0$864a908d@us.oracle.com>

Drew Adams wrote:
>> why is grep in the tools menu and not in edit - Search?
> 
> I agree that Grep should be on the Search menu. I moved it there in my own
> code long ago.
> 
> FWIW - 
> 
> I also did the following to the Search menu:
> 
> * Moved it to the top level, instead of as an Edit submenu. 
> * Moved the Replace, Bookmarks, and Go To submenus to it.
> * Added an Occurrences item (`occur').
> * Added a Tags submenu (`find-tag', `find-tag-regexp',
>   `apropos-tags', `tags-search').
> 
> Screenshot of the menu attached. All except the Icicles submenu is vanilla
> Emacs stuff, just renamed and rearranged.
> 
> There are lots of powerful search tools in Emacs, and it is good to make
> them more evident.
> 
> BTW - Although I removed a lot from the Edit menu, I added other things to
> it - things that are more about editing: submenus Fill (filling), Edit
> Region, and Sort Region, for instance. And items Delete Matching Lines and
> Delete Non-Matching Lines (`flush-lines', `keep-lines').

I still think it would be good to replace

   Tools
     grep

with

   Edit
     Search
       lgrep
       rgrep

For Drews suggestion and earlier discussion see here:

http://www.nabble.com/Change-grep--%3E-lgrep,-rgrep-in-Tools-menu--td15184987.html

Also, occur is missing from the search sub-menu.

I believe those things are essential for beginners. The menus are 
perhaps most useful for the beginners. My earlier question did not evoke 
much response, maybe because this question is not so important for most 
readers here.

I suggest we change the Edit menu. Maybe Drew's suggestion is good too, 
but I feel that it can be troublesome with too many menus.

If someone feels very strongly against changing the menus, then please 
say so. Otherwise I think it is just a matter of doing it (in a sane way).




      reply	other threads:[~2008-03-21 20:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-30 15:36 Change grep -> lgrep, rgrep in Tools menu? Lennart Borgman (gmail)
2008-01-31  1:06 ` Richard Stallman
2008-01-31  8:46   ` Lennart Borgman (gmail)
2008-01-31  8:55     ` William Xu
2008-01-31  9:05       ` Lennart Borgman (gmail)
2008-01-31 10:24         ` William Xu
2008-02-01 15:24   ` Lennart Borgman (gmail)
2008-02-01 19:46     ` Search menu [was: Change grep -> lgrep, rgrep in Tools menu?] Drew Adams
2008-03-21 20:41       ` Lennart Borgman (gmail) [this message]

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=47E41D92.9050002@gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=drew.adams@oracle.com \
    --cc=emacs-devel@gnu.org \
    --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).