From: Eli Zaretskii <eliz@gnu.org>
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 21:08:15 +0300 [thread overview]
Message-ID: <83pou6pnu8.fsf@gnu.org> (raw)
In-Reply-To: <m3lh4uy4hf.fsf@gnus.org> (message from Lars Magne Ingebrigtsen on Sun, 03 Apr 2016 19:41:32 +0200)
> From: Lars Magne Ingebrigtsen <larsi@gnus.org>
> Cc: 22627@debbugs.gnu.org
> Date: Sun, 03 Apr 2016 19:41:32 +0200
>
> 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.
Is it reasonable to assume that an average Emacs session will have
only a couple of Grep buffers? Or that the user will only care about
the last 2 or 3 of them? I think it isn't reasonable, in which case
your use case doesn't scale well enough to the needs of others. By
contrast, having a distinct name will cater both to your use case and
to that of others, where dozens of Grep buffers could exist in the
same session.
Besides, the 'gid' command, which is part of ID-Utils, and runs the
'lid' command, already behaves like I described, so we at least have a
precedent here.
next prev parent reply other threads:[~2016-04-03 18:08 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 [this message]
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=83pou6pnu8.fsf@gnu.org \
--to=eliz@gnu.org \
--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).