I'd put `chromium-browser` next to `google-chrome` in the list.
Other than that, looks good to me. I'm happy to make the above change
when committing, if that works for you.
On Tue, Nov 8, 2016 at 8:01 PM, 'Reuben Thomas' via Racket Developers
<racke...@googlegroups.com> wrote:
>>
>> Thanks, I'll take that back to the xdg-utils list, and prepare a
>> simple PR to add chromium-browser.
>
> Attached, a patch to improve the browser list. See the commit log for
> details.
Openning a URL on windows had the same problem and the solution was to
generate a temporary "trampoline" html page that redirects to the actual
page (with the query part): the same code could be used for xdg.
On Wed, Nov 9, 2016 at 6:24 PM, 'Reuben Thomas' via Racket Developers
<racke...@googlegroups.com> wrote:
>
> That's a good idea, but I don't think there is much point. xdg-open is
> meant mainly to open files. For Racket, we know we are trying to run a
> browser. There are other methods to do this, e.g. sensible-browser
> and x-www-browser.
xdg-open still has an advantage of being installed more (eg, on Fedora I
don't see either of the other two things installed by default), and at
least trying to be a standard...
On Mon, Nov 14, 2016 at 4:31 PM, Reuben Thomas <r...@sc3d.org> wrote:On 13 November 2016 at 03:54, Eli Barzilay <e...@barzilay.org> wrote:
xdg-open still has an advantage of being installed more (eg, on
Fedora I don't see either of the other two things installed by
default), and at least trying to be a standard...
Yes indeed. I have filed freedesktop bug #98648 about this.
I saw that, but it's been this way for a very long time, and even if it
does get resolved quickly now, it'll be a while until it propagates.
Therefore there's value in making it work now.