unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: "Drew Adams" <drew.adams@oracle.com>
Subject: RE: Nested grep
Date: Thu, 16 Nov 2006 09:35:41 -0800	[thread overview]
Message-ID: <DNEMKBNJBGPAOPIJOOICAEHPDJAA.drew.adams@oracle.com> (raw)
In-Reply-To: <1163664141.997812.261210@e3g2000cwe.googlegroups.com>

> > OK. I just added similar commands to compile+20.el, for use with Emacs
> > versions prior to 22:
> http://www.emacswiki.org/cgi-bin/wiki/compile%2b20.el.
> > However, since there is no grep-specific keymap prior to Emacs
> 22, I have
> > not bound the new commands.
> >
>
> Thanks, it's working well.  Though I'm missing something like I
> originally suggested: an easy way to go back to the previous grep
> buffer.
>
> I think when one opens a new grep buffer (while keeping the previous
> one) then one usually does it to quickly investigate something which
> occured when perusing the first grep. So it would be logical to have a
> means to easily close the current grep buffer and return to the
> previous one.
>
> Currently, in your implementation pressing 'q' in the grep buffer only
> closes the current one leaving to the user to switch to the previous
> grep buffer. Wouldn't make it more sense for q to switch to the last
> recently used grep buffer if there is one? With an option maybe?

Hi Tamas. Just use `choose-grep-buffer', instead of `q'. That will switch to
another grep buffer in place of the current one. The default value is now
the last-used grep buffer, so just use M-n to get that.

Download the latest compile+20.el - I just added the completion default. I
hadn't bothered to do that before (grep+.el uses `grep-last-buffer', which
isn't defined in Emacs 20).

HTH - Drew

  reply	other threads:[~2006-11-16 17:35 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14 13:35 Nested grep spamfilteraccount
2006-11-14 14:55 ` Robert Thorpe
2006-11-14 15:02 ` Drew Adams
     [not found] ` <mailman.569.1163516549.2155.help-gnu-emacs@gnu.org>
2006-11-14 16:00   ` spamfilteraccount
2006-11-14 16:11 ` Markus Triska
2006-11-14 16:34   ` spamfilteraccount
2006-11-14 16:40     ` Markus Triska
2006-11-14 17:00       ` spamfilteraccount
2006-11-14 17:32         ` spamfilteraccount
2006-11-14 21:54           ` Drew Adams
     [not found]           ` <mailman.604.1163541320.2155.help-gnu-emacs@gnu.org>
2006-11-15  6:35             ` spamfilteraccount
2006-11-15 16:36               ` Drew Adams
     [not found]               ` <mailman.653.1163608715.2155.help-gnu-emacs@gnu.org>
2006-11-15 16:47                 ` spamfilteraccount
2006-11-15 19:02                   ` Drew Adams
     [not found]                   ` <mailman.666.1163617488.2155.help-gnu-emacs@gnu.org>
2006-11-16  8:02                     ` spamfilteraccount
2006-11-16 17:35                       ` Drew Adams [this message]
2006-11-15 17:57             ` Peter Lee
2006-11-17 16:09               ` Drew Adams
2006-11-14 18:21 ` Peter Dyballa
     [not found] <mailman.754.1163779854.2155.help-gnu-emacs@gnu.org>
2006-11-17 17:59 ` Peter Lee

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=DNEMKBNJBGPAOPIJOOICAEHPDJAA.drew.adams@oracle.com \
    --to=drew.adams@oracle.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.
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).