From: Giuseppe Bilotta <giuseppe.bilotta@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Christian Couder <christian.couder@gmail.com>
Subject: Re: [PATCHv2 6/7] web--browse: use (x-)www-browser if available
Date: Sat, 4 Dec 2010 08:49:09 +0100 [thread overview]
Message-ID: <AANLkTinG3moZFNOMBwrc7UTrXuGeUourQp+6OEH5Vcgh@mail.gmail.com> (raw)
In-Reply-To: <20101204004225.GA15906@burratino>
On Sat, Dec 4, 2010 at 1:42 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Giuseppe Bilotta wrote:
>
>> I do believe that Debian encourages the use of sensible-browser (that
>> does the BROWSER and *www-browser check itself) rather than manually
>> going to look at those specifications.
>
> My impression (by analogy with policy §11.4 "Editors and pagers") is
> that one is encouraged to make the default configurable at compile
> time and use
>
> - first $BROWSER
> - then something desktop-specific
> - then the configured default
>
> and set that default to www-browser or x-www-browser, depending on
> whether your program uses X. That way, non-Debian systems benefit
> from the changes you introduce, too.
I'm not entirely sure how non-Debian would benefit from the change at
the current state, but I'm willing to present patches for the
mechanism offered by other distributions (e.g. does anybody know how
RedHad/Fedora sets the preferred browser?)
>> An alternative approach would be to get rid of the *www-browser and
>> BROWSER patches, and just use xdg-open if it's available. Which again
>> raises the issue of how to enforce opening the page in a new tab.
>
> Yes, in this case that is the ideal (assuming xdg-utils has wide
> enough adoption).
>
> I think xdg-open has just as much a reason as we do to encourage
> opening the page in a new tab. Would it be hard to make that happen?
I have no idea. Also, it's sort-of outside the scope of our reach, and
we would have to wait for a change in that effect to 'trickle down'.
--
Giuseppe "Oblomov" Bilotta
next prev parent reply other threads:[~2010-12-04 7:49 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
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 [this message]
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=AANLkTinG3moZFNOMBwrc7UTrXuGeUourQp+6OEH5Vcgh@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).