From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@gmail.com>
Subject: Re: [PATCHv2 6/7] web--browse: use (x-)www-browser if available
Date: Fri, 3 Dec 2010 18:57:37 +0100 [thread overview]
Message-ID: <AANLkTik=pGND-EYQ2HYTmevVd5S9pXZBNSpDsnafOF2V@mail.gmail.com> (raw)
In-Reply-To: <AANLkTimAdrqYezL5jf9OR_J5XdYW-KYhYy9n_VQAUSD8@mail.gmail.com>
On Fri, Dec 3, 2010 at 6:40 PM, Christian Couder
<christian.couder@gmail.com> wrote:
> Hi,
>
>> Custom commands may also be specified.
>>
>> +If no default browser is specified, and /usr/bin/x-www-browser
>> +(under X) or /usr/bin/www-browser is present, they are used to determine
>> +the browser to use.
>
> It looks like /usr/bin/gnome-www-browser is missing.
Good catch. I'll add it.
>> + echo >&2 "$basename ($browser) is not a supported browser, skipping"
>
> Why not:
>
> echo >&2 "$basename (from $testexe) is not a supported browser, skipping"
>
> ?
>
> Otherwise we might get something like:
>
> "newbrowser (newbrowser) is not a supported browser, skipping"
I rephrased it to:
echo >&2 "$testexe (detected as $browser) is not a supported browser, skipping"
>> @@ -133,7 +185,7 @@ if test -z "$browser" ; then
>> fi
>> done
>> test -z "$browser" && die "No known browser available."
>> -else
>> +else if test -z "$browser_path"; then
>
> Now that you reset $browser above, I am not sure this test -z
> "$browser_path" is useful...
I believe it is. If the *www-browser detection was successful,
_that's_ what we want to launch, so we want to skip the
init_browser_path in that else section, which we would hit if we
didn't check for $browser_path. We also don't want to repeat the
valid_tool check, since we know it's valid already.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2010-12-03 17:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-03 16:47 [PATCHv2 0/7] web--browse cleanup and extensions Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 1/7] CodingGuidelines: mention whitespace preferences for shell scripts Giuseppe Bilotta
2010-12-03 21:43 ` Junio C Hamano
2010-12-03 22:02 ` Giuseppe Bilotta
2010-12-03 22:28 ` Junio C Hamano
2010-12-03 22:46 ` Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 2/7] web--browse: coding style Giuseppe Bilotta
2010-12-07 23:38 ` Junio C Hamano
2010-12-03 16:47 ` [PATCHv2 3/7] web--browse: split valid_tool list Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 4/7] web--browse: support opera, seamonkey and elinks Giuseppe Bilotta
2010-12-03 22:01 ` Junio C Hamano
2010-12-03 22:22 ` Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 5/7] web--browse: better support for chromium Giuseppe Bilotta
2010-12-03 21:57 ` Junio C Hamano
2010-12-03 22:25 ` Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 6/7] web--browse: use (x-)www-browser if available Giuseppe Bilotta
2010-12-03 17:40 ` Christian Couder
2010-12-03 17:57 ` Giuseppe Bilotta [this message]
2010-12-03 22:15 ` Junio C Hamano
2010-12-03 22:45 ` Giuseppe Bilotta
2010-12-04 0:42 ` Jonathan Nieder
2010-12-04 7:49 ` Giuseppe Bilotta
2010-12-03 16:47 ` [PATCHv2 7/7] web--browse: look at the BROWSER env var Giuseppe Bilotta
2010-12-03 17:08 ` Jonathan Nieder
2010-12-03 17:16 ` Jonathan Nieder
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='AANLkTik=pGND-EYQ2HYTmevVd5S9pXZBNSpDsnafOF2V@mail.gmail.com' \
--to=giuseppe.bilotta@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).