From: storm@cua.dk (Kim F. Storm)
Cc: rms@gnu.org, assign@gnu.org, emacs-devel@gnu.org
Subject: Re: Assignment of misc packages for emacs
Date: 17 May 2002 01:39:57 +0200 [thread overview]
Message-ID: <5x3cwr4q7m.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <200205151927.g4FJRRW26103@rum.cs.yale.edu>
"Stefan Monnier" <monnier+gnu/emacs@rum.cs.yale.edu> writes:
Re: M-x match --
>
> I personally use
>
> C-u M-x grep RET <edit things to look like ../**/*.[ch]> RET
>
> > The latter doesn't (easily) allow you to start the search in another
> > directory, and it finds (duplicate) matches in backup files (such as
> > xterm.c~), and IMO the prompt is _completely obscure_ unless you are a
> > UNIX shell expert...
>
> Agreed, that's why I prefer zsh's ** construct. I think C-u M-x grep RET
> should be more aggressive in its choice of initial command (it only
> chooses the files' extension for you the first time you invoke it).
> The reason why it's so conservative was because I wanted to install
> my code without having to convince anybody that the new behavior was better
> so I kept 100% compatibility with the old behavior.
I've never liked M-x grep for the very reason that I have to edit the command.
>
> > > I am not sure it is worth reading the directory rather than just using
> > > the current directory.
> > This is VERY useful (I use it very often), and to use the current
> > directory, just hit RET.
>
> I must say that I generally prefer the C-u M-x grep approach which does
> not force you into a series of questions, but just presents you with
> the "complete default" and lets you edit it to your liking.
One additional trick is that M-x match prompts you for the directory
using ido-read-directory, meaning that it is very easy to navigate to
a completely different base directory.
> > Yes, you could argue that this is a separate issue -- but I think the
> > menu need to be efficient to get the maximum usability...
>
> You're probably right that we should improve the compilation-mode's support
> for such browsing. Maybe only for *grep* buffers, but maybe not.
> But that just means rebinding next-error (and previous-error) to more
> keys than just C-x `.
Right. I'll look at the new grep code (I wasn't aware that grep had been
rewritten) as well as my own code again to see whether I can enhance the
standard code rather than add a separate package.
BTW, M-x match uses jit-lock to fontify the matches in the *Match*
buffer. And when you visit a match, it is temporarily highlighted in
the target buffer (using an overlay).
Re: mini-menu --
>
> > I can see the similarity in functionality, but for the simple use for
> > which it is intended, I like mine better, as it is less intrusive and
> > more similar to a keymap "with intermediate help in echo area".
>
> I'm still not clear how it compares to HierarKey menus
> (see PCL-CVS's `d' prefix or the M-g prefix in the global map).
I wasn't aware of the HierarKey feature (it's a very well hidden "fact").
It compares almost 1:1 ... except I don't like HierarKey menus
to show the full key bindings, e.g.
Set face: default (M-g d), bold (M-g b), italic (M-g i), l = bold-italic (M-g l), undeline (M-g u), Other ... (M-g o)
With mini-menu, this would be much simpler, e.g.
Set face: d)efault b)old i)talic bo(l)d-italic u)ndeline o)ther ...
I guess we could hack the HierarKey menus to look like that --
then mini-menu would definitely have no purpose at all!
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
next prev parent reply other threads:[~2002-05-16 23:39 UTC|newest]
Thread overview: 109+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200205050534.g455YfF01634@aztec.santafe.edu>
2002-05-05 22:02 ` Assignment of misc packages for emacs Kim F. Storm
2002-05-06 23:07 ` Alex Schroeder
2002-05-08 1:16 ` Miles Bader
2002-05-08 1:47 ` Stefan Monnier
2002-05-09 2:45 ` Richard Stallman
2002-05-07 14:08 ` Kai Großjohann
2002-05-08 13:58 ` Richard Stallman
2002-05-08 1:31 ` Miles Bader
2002-05-08 6:23 ` Thien-Thi Nguyen
2002-05-14 19:41 ` Richard Stallman
2002-05-14 19:41 ` Richard Stallman
2002-05-14 23:44 ` Kim F. Storm
2002-05-15 1:08 ` Miles Bader
2002-05-15 21:37 ` Kim F. Storm
2002-05-16 1:19 ` Miles Bader
2002-05-17 19:29 ` Richard Stallman
2002-05-17 21:42 ` Kim F. Storm
2002-05-17 19:29 ` Richard Stallman
2002-05-17 21:31 ` Kim F. Storm
2002-05-16 7:22 ` Richard Stallman
2002-05-16 23:41 ` Kim F. Storm
2002-05-15 4:51 ` Eli Zaretskii
2002-05-15 8:41 ` Andreas Schwab
2002-05-15 10:20 ` Eli Zaretskii
2002-05-15 11:08 ` Andreas Schwab
2002-05-15 21:41 ` Kim F. Storm
2002-05-15 19:27 ` Stefan Monnier
2002-05-15 20:37 ` Andreas Schwab
2002-05-16 23:39 ` Kim F. Storm [this message]
2002-05-16 22:49 ` Stefan Monnier
2002-05-17 6:27 ` Eli Zaretskii
2002-05-17 7:10 ` Miles Bader
2002-05-17 9:21 ` Andreas Schwab
2002-05-17 11:13 ` Miles Bader
2002-05-17 9:40 ` Eli Zaretskii
2002-05-17 11:15 ` Miles Bader
2002-05-17 10:47 ` Kim F. Storm
2002-05-17 10:08 ` Stefan Monnier
2002-05-17 11:20 ` Miles Bader
2002-05-17 12:07 ` Kim F. Storm
2002-05-17 11:28 ` Miles Bader
2002-05-18 18:48 ` Richard Stallman
2002-05-18 21:39 ` Kim F. Storm
2002-05-19 19:40 ` Richard Stallman
2002-05-18 22:37 ` Stefan Monnier
2002-05-19 19:40 ` Richard Stallman
2002-05-16 23:07 ` Miles Bader
2002-05-18 18:48 ` Richard Stallman
2002-05-19 11:57 ` Miles Bader
2002-05-19 14:41 ` Stefan Monnier
2002-05-19 15:12 ` Miles Bader
2002-05-20 6:38 ` Miles Bader
2002-05-20 9:57 ` Alex Schroeder
2002-05-20 10:06 ` Kai Großjohann
2002-05-20 21:34 ` Richard Stallman
2002-05-21 9:54 ` Mario Lang
2002-05-21 10:23 ` Miles Bader
2002-05-22 22:29 ` Richard Stallman
2002-05-21 10:20 ` Miles Bader
2002-05-22 22:27 ` Richard Stallman
2002-05-23 7:08 ` Miles Bader
2002-05-23 16:49 ` Mario Lang
2002-05-23 22:21 ` Miles Bader
2002-06-04 17:27 ` Miles Bader
2002-06-05 14:42 ` Stefan Monnier
2002-06-06 1:07 ` Miles Bader
2002-06-06 1:37 ` Stefan Monnier
2002-06-06 1:46 ` Miles Bader
2002-06-06 7:57 ` Miles Bader
2002-06-07 0:45 ` Richard Stallman
2002-06-07 0:45 ` Richard Stallman
2002-06-05 23:10 ` Kim F. Storm
2002-06-06 1:09 ` Miles Bader
2002-06-06 1:24 ` Miles Bader
2002-06-07 0:45 ` Richard Stallman
2002-06-07 23:26 ` Kim F. Storm
2002-06-08 1:09 ` Miles Bader
2002-06-08 19:15 ` Richard Stallman
2002-06-06 12:04 ` Richard Stallman
2002-06-06 12:41 ` Miles Bader
2002-06-06 13:37 ` Stefan Monnier
2002-06-06 13:45 ` Miles Bader
2002-06-07 23:23 ` Richard Stallman
2002-06-08 4:06 ` Miles Bader
2002-06-09 15:19 ` Richard Stallman
2002-06-10 14:35 ` Stefan Monnier
2002-06-11 19:25 ` Richard Stallman
2002-07-07 22:46 ` What happened to the key-menu patch? Kim F. Storm
2002-07-09 7:00 ` Miles Bader
2002-07-09 13:58 ` Stefan Monnier
2002-07-10 2:43 ` Miles Bader
2002-07-10 18:12 ` Stefan Monnier
2002-07-10 10:43 ` Richard Stallman
2002-07-11 17:13 ` Stefan Monnier
2002-07-12 17:37 ` Richard Stallman
2002-07-12 18:07 ` Stefan Monnier
2002-07-13 14:20 ` Richard Stallman
2002-07-13 17:37 ` Stefan Monnier
2002-07-15 1:09 ` Richard Stallman
2002-07-09 18:51 ` Richard Stallman
2002-07-10 2:45 ` Miles Bader
2002-07-10 19:20 ` Richard Stallman
2002-05-20 14:48 ` Assignment of misc packages for emacs Richard Stallman
2002-05-18 18:48 ` Richard Stallman
2002-05-18 20:07 ` Kim F. Storm
2002-05-19 19:40 ` Richard Stallman
2002-05-16 7:21 ` Richard Stallman
2002-05-16 7:21 ` Richard Stallman
2002-05-15 7:44 ` D. Goel
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=5x3cwr4q7m.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=assign@gnu.org \
--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).