From: "René Scharfe" <rene.scharfe@lsrfire.ath.cx>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Nazri Ramliy <ayiehere@gmail.com>,
gitster@pobox.com, git@vger.kernel.org,
johannes.schindelin@gmx.de
Subject: Re: [PATCH] Bugfix: grep: Do not colorize output when -O is set
Date: Tue, 06 Jul 2010 22:19:03 +0200 [thread overview]
Message-ID: <4C338FB7.8060005@lsrfire.ath.cx> (raw)
In-Reply-To: <20100706193845.GA7438@burratino>
Am 06.07.2010 21:38, schrieb Jonathan Nieder:
> Hi,
>
> René Scharfe wrote:
>
>> Hmm, but with --open-files-in-pager without argument or -Oless colours
>> may be handled correctly and desirable.
>
> Sorry I missed this before. Is there really a pager that will accept
> \e[36m as a command-line argument and do something reasonable with it?
I was missing that -O enforces -l, and that it makes the pager open all
files directly from the worktree, one by one. Somehow I assumed that it
would pipe something like the output of "grep -h -C inf" to the pager,
colour marks and all -- similar to what is done without -O, except that
it would start a new pager for each file.
I think the "pager" part of the long option name confused me, but that's
a weak excuse. Just ignore me, your original patch was fine.
[snip]
> Probably a better solution is to recommend -C option, possibly
> implementing -C infinity so people don’t have to use -C 1000000.
Hmm, that could be useful, also with -A and -B.
René
next prev parent reply other threads:[~2010-07-06 20:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-02 10:02 [PATCH] Bugfix: grep: Do not colorize output when -O is set Nazri Ramliy
2010-07-02 16:19 ` René Scharfe
2010-07-06 19:38 ` Jonathan Nieder
2010-07-06 20:19 ` René Scharfe [this message]
2010-07-02 19:21 ` Jonathan Nieder
2010-07-03 1:20 ` Nazri Ramliy
2010-07-03 2:55 ` [PATCH v2] grep -O: Do not pass color sequences as filenames to pager Jonathan Nieder
2010-07-03 7:59 ` [PATCH] Bugfix: grep: Do not colorize output when -O is set Jakub Narebski
2010-07-06 20:04 ` [PATCH] t/README: document more test helpers Jonathan Nieder
2010-07-06 20:23 ` Ævar Arnfjörð Bjarmason
2010-07-07 4:25 ` Junio C Hamano
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=4C338FB7.8060005@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=ayiehere@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=johannes.schindelin@gmx.de \
--cc=jrnieder@gmail.com \
/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).