From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Lebon <jonathan.lebon@gmail.com>
Cc: git@vger.kernel.org, peff@peff.net
Subject: Re: [PATCH 1/4] diff-highlight: add `less -r` to cmd in README
Date: Mon, 02 Nov 2015 18:41:53 -0800 [thread overview]
Message-ID: <xmqq7flzerda.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <1446516334-27652-2-git-send-email-jonathan.lebon@gmail.com> (Jonathan Lebon's message of "Mon, 2 Nov 2015 21:05:31 -0500")
Jonathan Lebon <jonathan.lebon@gmail.com> writes:
> As it is, the suggested command for trying out diff-highlight will just
> dump the whole git log output to the terminal. Let's pipe it through
> `less` so users aren't surprised on the first try.
That justifies the "less" part but not your choice of "-r".
I am assuming that you are telling "less" not to show the ANSI
"color" escape sequences using the caret notation with "-r", which
is a very natural and sensible thing to do when using `highlight`.
But if that is the case, you don't want "-r" (raw control chars for
everything). You would want to say "-R", I think.
Other than that, looks like a sensible thing to do to me.
Thanks.
> Signed-off-by: Jonathan Lebon <jonathan.lebon@gmail.com>
> ---
> contrib/diff-highlight/README | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/contrib/diff-highlight/README b/contrib/diff-highlight/README
> index 836b97a..bbbfdda 100644
> --- a/contrib/diff-highlight/README
> +++ b/contrib/diff-highlight/README
> @@ -44,9 +44,9 @@ Use
>
> You can try out the diff-highlight program with:
>
> ----------------------------------------------
> -git log -p --color | /path/to/diff-highlight
> ----------------------------------------------
> +------------------------------------------------------
> +git log -p --color | /path/to/diff-highlight | less -r
> +------------------------------------------------------
>
> If you want to use it all the time, drop it in your $PATH and put the
> following in your git configuration:
next prev parent reply other threads:[~2015-11-03 2:42 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-03 2:05 [PATCH 0/4] diff-highlight: make a few improvements Jonathan Lebon
2015-11-03 2:05 ` [PATCH 1/4] diff-highlight: add `less -r` to cmd in README Jonathan Lebon
2015-11-03 2:41 ` Junio C Hamano [this message]
2015-11-03 3:12 ` Jonathan Lebon
2015-11-03 21:14 ` Jeff King
2015-11-03 21:51 ` Junio C Hamano
2015-11-03 21:55 ` Jeff King
2015-11-03 2:05 ` [PATCH 2/4] diff-highlight: factor out prefix/suffix functions Jonathan Lebon
2015-11-03 21:17 ` Jeff King
2015-11-03 2:05 ` [PATCH 3/4] diff-highlight: match up lines before highlighting Jonathan Lebon
2015-11-03 21:44 ` Jeff King
2015-11-03 22:03 ` Jeff King
2015-11-17 5:18 ` Jonathan Lebon
2015-11-17 22:50 ` Jeff King
2015-11-03 2:05 ` [PATCH 4/4] diff-highlight: add maxhunksize config option Jonathan Lebon
2015-11-03 21:46 ` Jeff King
2015-11-03 22:07 ` [PATCH 0/4] diff-highlight: make a few improvements Jeff King
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=xmqq7flzerda.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jonathan.lebon@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.