From: Lennart Borgman <lennart.borgman@gmail.com>
To: Juri Linkov <juri@jurta.org>
Cc: 1863@emacsbugs.donarmstrong.com, jidanni@jidanni.org
Subject: bug#1863: Improved grep prompt
Date: Fri, 16 Jan 2009 01:54:06 +0100 [thread overview]
Message-ID: <e01d8a50901151654r2d1a13d4n869912e30504e845@mail.gmail.com> (raw)
In-Reply-To: <87fxjkccbk.fsf@jurta.org>
On Fri, Jan 16, 2009 at 1:31 AM, Juri Linkov <juri@jurta.org> wrote:
>>>> In your case I myself see nothing that can help then ;-) but I think
>>>> newbees would benefit from having all the search and replace commands
>>>> under search and replace in the edit menu.
>>>
>>> I can't believe we still don't have these useful commands in the menu.
>>> But why do you think they should be placed in the Edit menu?
>>
>> That is where the search and replace commands normally are. Why do you
>> doubt they should be there?
>
> The `Grep' menu entry is traditionally in the Tools menu because it reads
> an external command like `Compile' and `Shell Command' do. So perhaps we
> should add `rgrep' and `lgrep' to the Tools menu.
I think menus should see things from the users view, not from an
internal view. Emacs itself does not really care how the menus look
...
I would expect nearly all users to look for these commands in the Edit menu.
next prev parent reply other threads:[~2009-01-16 0:54 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 2:07 bug#1863: Improved grep prompt jidanni
2009-01-14 1:18 ` Juri Linkov
2009-01-14 1:33 ` jidanni
2009-01-14 23:52 ` Juri Linkov
2009-01-15 0:40 ` jidanni
2009-01-15 1:09 ` Lennart Borgman
2009-01-15 1:27 ` Juri Linkov
2009-01-15 1:55 ` Lennart Borgman
2009-01-16 0:31 ` Juri Linkov
2009-01-16 0:54 ` Lennart Borgman [this message]
2009-01-16 9:27 ` richardeng
2009-01-15 2:54 ` Stefan Monnier
2018-04-15 22:12 ` Lars Ingebrigtsen
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=e01d8a50901151654r2d1a13d4n869912e30504e845@mail.gmail.com \
--to=lennart.borgman@gmail.com \
--cc=1863@emacsbugs.donarmstrong.com \
--cc=jidanni@jidanni.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 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.