unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Óscar Fuentes" <ofv@wanadoo.es>
To: Lars Magne Ingebrigtsen <larsi@gnus.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, 03 Apr 2016 19:41:00 +0200	[thread overview]
Message-ID: <87inzy380j.fsf@wanadoo.es> (raw)
In-Reply-To: <m3pou6y5t3.fsf@gnus.org> (Lars Magne Ingebrigtsen's message of "Sun, 03 Apr 2016 19:12:56 +0200")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Eli Zaretskii <eliz@gnu.org> writes:
>
>>> From: Lars Ingebrigtsen <larsi@gnus.org>
>>> Date: Thu, 11 Feb 2016 16:52:14 +1100
>>> 
>>> `g' works fine for redoing, but it would be great if you could return to
>>> the previous (and next) with the normal `r'/`n' commands.
>>
>> We could have an optional feature whereby the Grep buffer is named
>> something like "*grep-the-command-line-used*".  Then as long as the
>> next Grep command is different, you will have a new buffer for its
>> output, and Bob's your uncle.

That's what ag.el (which drives the `ag' search command) does. For
instance:

*ag search text:foo dir:/home/oscar/bar*

which makes convenient locating an ag buffer by searched text and/or
directory. It tends to create large buffer names which don't play well
with tools that have a limited sprace for buffer names (ibuffer) but
otherwise it is useful.

> Having multiple grep buffers would also be a nice feature,

I do that with compilation-buffer-name-function.

[snip]





  parent reply	other threads:[~2016-04-03 17:41 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
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 [this message]
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=87inzy380j.fsf@wanadoo.es \
    --to=ofv@wanadoo.es \
    --cc=22627@debbugs.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).