From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org, Drew Adams <drew.adams@oracle.com>
Cc: 22627@debbugs.gnu.org, larsi@gnus.org
Subject: bug#22627: 25.1.50; Wishlist: It would be nice if the grep buffer had a history
Date: Fri, 12 Feb 2016 06:42:55 -0800 (PST) [thread overview]
Message-ID: <9b7d4a41-c5d9-4169-92b5-2fd053f5d694@default> (raw)
In-Reply-To: <<E1aUCwx-0003Vi-7S@fencepost.gnu.org>>
>> . You can automatically rename the current grep buffer to reflect
>> the args using
>> (add-hook 'grep-mode-hook 'grepp-rename-buffer-to-last-no-confirm)
>>
>> . You can rename it thus on demand using `r'.
>>
>> . `+' renames current grep buffer uniquely (without the args) and
>> switches to buffer `*grep*'
>>
>> . `b' reads a grep buffer name and switches to that buffer. A grep
>> buffer here is any buffer whose name matches `'\\*grep\\*', which
>> includes those whose names include the arguments.
>
> It would be nice to put buttons at the start of the buffer
> to do some of these things. That way, users would not need
> to remember commands for them.
Maybe. But there is something to be said for keeping the buffer
content as just `grep' output. In `grep+.el' I've added the commands
to the menu-bar `Grep' menu instead. (And there is `C-h m', which
mentions the keys in my version of `grep'.)
https://www.emacswiki.org/emacs/download/grep%2b.el
next parent reply other threads:[~2016-02-12 14:42 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
[not found] <<87lh6rx08h.fsf@gnus.org>
[not found] ` <<8337sz9e2l.fsf@gnu.org>
2016-02-11 22:04 ` bug#22627: 25.1.50; Wishlist: It would be nice if the grep buffer had a history Drew Adams
2016-02-12 12:35 ` Richard Stallman
2016-02-11 5:52 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
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
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=9b7d4a41-c5d9-4169-92b5-2fd053f5d694@default \
--to=drew.adams@oracle.com \
--cc=22627@debbugs.gnu.org \
--cc=larsi@gnus.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).