From: Sebastian Pipping <webmaster@hartwork.org>
To: Jeff King <peff@peff.net>
Cc: Nicolas Sebrecht <nicolas.s.dev@gmx.fr>,
Junio C Hamano <gitster@pobox.com>,
Thomas Rast <trast@student.ethz.ch>, Git ML <git@vger.kernel.org>
Subject: Re: Parameter --color-words not documented for "git show"
Date: Fri, 21 Jan 2011 01:27:54 +0100 [thread overview]
Message-ID: <4D38D30A.3040707@hartwork.org> (raw)
In-Reply-To: <20110121002020.GA7874@sigill.intra.peff.net>
On 01/21/11 01:20, Jeff King wrote:
>> I agree with Thomas here. (1) is the only option I find acceptable,
>> personally. If you'd rather not do that, then at least know I now.
>> Great to have --color-words around btw.
>
> I'm curious why (4) doesn't work for you. I assumed you came to the
> problem by one of:
>
> - you wanted to know which options "git show" had, so you looked in
> the manpage. Nothing told you about "--color-words", nor referred
> you to a list of diff options. With (4), you would find that it
> accepted all diff options, and then go read the list of diff options
> (if you weren't already familiar with it).
>
> - you knew about --color-words, and wondered if "git show" supported
> it. In the current case, searching the page turns up nothing. In
> option (4), a search would find it (with a reference to diff options
> if you wanted more details).
>
> The downside is that you sometimes have to be referred. The upside to me
> is that it becomes explicit that there is a concept of "diff options"
> that you can look up easily and which we can refer to easily in other
> parts of the manual. That helps establish a mental model of how git's
> options work.
>
> So is it just that being referred is annoying, or something else?
Actually that approach is perfect. I misunderstood (4) on the first
read somehow. Really not my day today, sorry. I would love to see you
push (4) forward.
Best,
Sebastian
next prev parent reply other threads:[~2011-01-21 0:28 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-20 19:58 Parameter --color-words not documented for "git show" Sebastian Pipping
2011-01-20 20:27 ` Thomas Rast
2011-01-20 20:43 ` Sebastian Pipping
2011-01-20 21:25 ` Junio C Hamano
2011-01-20 23:16 ` Nicolas Sebrecht
2011-01-20 23:34 ` Jeff King
2011-01-21 0:05 ` Sebastian Pipping
2011-01-21 0:20 ` Jeff King
2011-01-21 0:27 ` Sebastian Pipping [this message]
2011-01-21 6:08 ` Junio C Hamano
2011-01-21 16:16 ` Jeff King
2011-01-21 10:08 ` Maaartin
2011-01-21 16:17 ` Jeff King
2011-01-23 10:35 ` Jakub Narebski
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=4D38D30A.3040707@hartwork.org \
--to=webmaster@hartwork.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=nicolas.s.dev@gmx.fr \
--cc=peff@peff.net \
--cc=trast@student.ethz.ch \
/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.