unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>, Eli Zaretskii <eliz@gnu.org>
Cc: 22627@debbugs.gnu.org
Subject: bug#22627: 25.1.50; Wishlist: It would be nice if the grep buffer had a history
Date: Sun, 3 Apr 2016 11:06:02 -0700 (PDT)	[thread overview]
Message-ID: <d230948c-d4f5-4e7c-a813-c3c40aba858c@default> (raw)
In-Reply-To: <m3lh4uy4hf.fsf@gnus.org>

> > Unlike Web pages, Grep searches are not connected by any links, so
> > traversing the history one buffer at a time will be frustrating and
> > unnatural, when there are a lot of them.  By contrast, naming them
> > uniquely will allow switching to the right one immediately.
> 
> That's true, so having an additional feature for multiple-buffer grep
> commands would also be nice, but it's an orthogonal issue.  My common
> use case is that I grep for "featurep 'xemacs", and then I grep for a
> different function, and when I'm finished with that, I just want to
> return to my previous search.  The `r'/`l' commands fit that perfectly.

What's wrong with hitting the up arrow or `C-p' to retrieve
previous `grep' command input?  If you want an earlier one
and don't want to cycle to it, use `M-r'.  As usual.

You can also use `C-x ESC ESC' to repeat previous commands,
editing the command as needed.  As usual.

Nothing new here.  I don't see what wishlist feature you're
looking for.  Command `grep' already has a minibuffer history.
And `M-x' already has a command history.  What's the problem?





  parent reply	other threads:[~2016-04-03 18:06 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-11  5:52 bug#22627: 25.1.50; Wishlist: It would be nice if the grep buffer had a history Lars Ingebrigtsen
2016-02-11 20:39 ` Eli Zaretskii
2016-04-03 17:12   ` Lars Magne Ingebrigtsen
2016-04-03 17:27     ` Eli Zaretskii
2016-04-03 17:41       ` Lars Magne Ingebrigtsen
2016-04-03 17:47         ` Lars Magne Ingebrigtsen
2016-04-03 18:04           ` John Wiegley
2016-04-03 18:09           ` Eli Zaretskii
2016-04-03 18:26             ` Lars Magne Ingebrigtsen
2016-04-03 18:39               ` Eli Zaretskii
2016-04-03 22:47             ` John Wiegley
2016-04-04  1:53               ` Drew Adams
2016-04-03 18:06         ` Drew Adams [this message]
2016-04-03 18:08         ` Eli Zaretskii
2016-04-03 18:15           ` Lars Magne Ingebrigtsen
2016-04-03 18:18             ` Drew Adams
2016-04-03 17:41     ` Óscar Fuentes
2016-02-12  0:53 ` Juri Linkov
2017-10-16 19:16 ` Charles A. Roelli
2017-10-16 21:30   ` Lars Ingebrigtsen
2017-10-17 18:16     ` Charles A. Roelli
     [not found] <<87lh6rx08h.fsf@gnus.org>
     [not found] ` <<8337sz9e2l.fsf@gnu.org>
2016-02-11 22:04   ` Drew Adams
2016-02-12 12:35     ` Richard Stallman
     [not found] <<<87lh6rx08h.fsf@gnus.org>
     [not found] ` <<<8337sz9e2l.fsf@gnu.org>
     [not found]   ` <<ab01ab95-621a-460d-81ca-aa1c106fb314@default>
     [not found]     ` <<E1aUCwx-0003Vi-7S@fencepost.gnu.org>
2016-02-12 14:42       ` Drew Adams

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=d230948c-d4f5-4e7c-a813-c3c40aba858c@default \
    --to=drew.adams@oracle.com \
    --cc=22627@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=larsi@gnus.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).