From: Jon Seymour <jon.seymour@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH 0/2] Teach 'git grep' about --open-files-in-pager=[<pager>]
Date: Sat, 27 Mar 2010 06:49:06 +1100 [thread overview]
Message-ID: <2cfc40321003261249g32ba4472x9786a86830ec9813@mail.gmail.com> (raw)
In-Reply-To: <20100326124650.GA12215@coredump.intra.peff.net>
On Fri, Mar 26, 2010 at 11:46 PM, Jeff King <peff@peff.net> wrote:
> On Fri, Mar 26, 2010 at 11:48:41AM +0100, Johannes Schindelin wrote:
>
>> This supports opening the results of a 'git grep' directly in a pager
>> (where the pager can be 'vi', too).
>
> This is not an argument against your patch, but you may be interested in
> an alternate method:
>
> git grep -n $pattern >grep.out
> vim -q grep.out
Or, in bash:
vim -q <(git grep -n $pattern)
though, of course you don't get the exit code from git.
jon.
prev parent reply other threads:[~2010-03-26 19:49 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 10:48 [PATCH 0/2] Teach 'git grep' about --open-files-in-pager=[<pager>] Johannes Schindelin
2010-03-26 10:49 ` [PATCH 1/2] grep: Add the option '--open-files-in-pager' Johannes Schindelin
2010-03-28 4:09 ` Jonathan Nieder
2010-03-29 17:13 ` Johannes Schindelin
2010-03-29 18:17 ` Junio C Hamano
2010-03-26 10:49 ` [PATCH 2/2] grep -P: allow optional argument specifying the pager (or editor) Johannes Schindelin
2010-03-26 10:50 ` Johannes Schindelin
2010-03-26 11:39 ` [PATCH 0/2] Teach 'git grep' about --open-files-in-pager=[<pager>] Bert Wesarg
2010-03-26 16:18 ` Johannes Schindelin
2010-03-26 20:07 ` Bert Wesarg
2010-03-26 12:46 ` Jeff King
2010-03-26 16:14 ` Johannes Schindelin
2010-03-26 20:33 ` Jeff King
2010-03-26 19:32 ` Junio C Hamano
2010-03-26 20:50 ` Francis Moreau
2010-03-27 1:09 ` Junio C Hamano
2010-03-27 15:19 ` Francis Moreau
2010-03-27 17:23 ` Junio C Hamano
2010-03-27 20:29 ` Francis Moreau
2010-03-26 19:49 ` Jon Seymour [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2cfc40321003261249g32ba4472x9786a86830ec9813@mail.gmail.com \
--to=jon.seymour@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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 NNTP newsgroup(s).