From: Junio C Hamano <gitster@pobox.com>
To: Evan Farrer <evan.farrer@gmail.com>
Cc: git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH/RFC] Add support for the google-chrome web browser
Date: Mon, 04 Jan 2010 21:40:07 -0800 [thread overview]
Message-ID: <7vr5q56rew.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20100105051906.GA22799@efarrerlx.appsig.com> (Evan Farrer's message of "Mon\, 4 Jan 2010 22\:19\:06 -0700")
Evan Farrer <evan.farrer@gmail.com> writes:
> Signed-off-by: Evan Farrer <Evan.Farrer@gmail.com>
> ---
> Documentation/git-web--browse.txt | 1 +
> git-web--browse.sh | 6 +++---
> 2 files changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/git-web--browse.txt b/Documentation/git-web--browse.txt
> index 278cf73..0994139 100644
> --- a/Documentation/git-web--browse.txt
> +++ b/Documentation/git-web--browse.txt
> @@ -25,6 +25,7 @@ The following browsers (or commands) are currently supported:
> * links
> * lynx
> * dillo
> +* google-chrome
Hmmm, the support added by this patch for the chrome is, together with
w3m, links, and open, to simply run the command with given arguments
without any other magic.
Perhaps valid_custom_tool() function should be changed to simply return $1
if $browser_cmd is not found, like this:
valid_custom_tool ()
{
browser_cmd=$(git config "browser.$1.cmd")
: ${browser_cmdn:=$1}
}
Then we don't even have to add any specific support for "google-chrome" or
anything that takes "$command $path..." and opens the documents.
Is there a downside in this approach?
next prev parent reply other threads:[~2010-01-05 5:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-05 5:19 [PATCH/RFC] Add support for the google-chrome web browser Evan Farrer
2010-01-05 5:40 ` Junio C Hamano [this message]
2010-01-05 17:20 ` Avery Pennarun
2010-01-05 18:39 ` Junio C Hamano
2010-01-05 18:56 ` Avery Pennarun
2010-01-05 19:56 ` 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=7vr5q56rew.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=chriscool@tuxfamily.org \
--cc=evan.farrer@gmail.com \
--cc=git@vger.kernel.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.
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).