On Sun, 2012-10-21 at 22:58 +0200, David Faure wrote:
On Friday 19 October 2012 17:09:50 David Faure wrote:
Better solution yet, imho: Screw being too clever.
- Have apps list protocols they support. Eg
Protocols=x-scheme-handler/http;x-scheme-handler/https;
Never ever do
On Monday 22 October 2012 09:45:31 Bastien Nocera wrote:
On Sun, 2012-10-21 at 22:58 +0200, David Faure wrote:
On Friday 19 October 2012 17:09:50 David Faure wrote:
Better solution yet, imho: Screw being too clever.
- Have apps list protocols they support. Eg
On Mon, 2012-10-22 at 10:30 +0200, David Faure wrote:
On Monday 22 October 2012 09:45:31 Bastien Nocera wrote:
On Sun, 2012-10-21 at 22:58 +0200, David Faure wrote:
On Friday 19 October 2012 17:09:50 David Faure wrote:
Better solution yet, imho: Screw being too clever.
-
On Friday 19 October 2012 17:09:50 David Faure wrote:
Better solution yet, imho: Screw being too clever.
- Have apps list protocols they support. Eg
Protocols=x-scheme-handler/http;x-scheme-handler/https;
Never ever do this, for the reasons above. HTTP is too complex to send all
I don't believe that was the case.
chromium.desktop has the
same:
MimeType=text/html;text/xml;application/xhtml+xml;text/mml;x-scheme-handler/http;x-scheme-handler/https;
J. Leclanche
On Sun, Oct 21, 2012 at 9:58 PM, David Faure fa...@kde.org wrote:
On Friday 19 October 2012 17:09:50 David
On Sunday 30 September 2012 00:38:39 Jerome Leclanche wrote:
There are a lot of issues with coming up with a good system for this.
Say you get a uri to an image: http://example.com/image.png. You want that
uri to open in an image viewer that supports http.
- What happens if the uri isn't
On Wed, 2012-10-03 at 22:04 +0400, Сергей Давыдов wrote:
Feel free to read the archives of this mailing-list to know
why adding a
list of protocols isn't a good idea, and actually harms
interoperability.
I've found
On Sun, 2012-09-30 at 00:38 +0100, Jerome Leclanche wrote:
There are a lot of issues with coming up with a good system for this.
Say you get a uri to an image: http://example.com/image.png. You want
that uri to open in an image viewer that supports http.
- What happens if the uri
On Tue, 2012-10-02 at 17:44 +0400, Сергей Давыдов wrote:
Behavior will largely depend on the actual program xdg-open
delegates to.
E.g. on KDE the KIO subsystem knows how to determine the MIME
type of a
resource and will look up the application
On Sunday, 2012-09-30, Jerome Leclanche wrote:
- What happens if the uri isn't an image? It should instead be opened in a
browser. But xdg-open cannot know how to open and sniff arbitrary
protocols, so it either has to open in an http reader *first* that then
forwards it to an image viewer,
Behavior will largely depend on the actual program xdg-open delegates to.
E.g. on KDE the KIO subsystem knows how to determine the MIME type of a
resource and will look up the application associated with it.
I would guess that this is also true for GNOME and their IO framework.
It is true
11 matches
Mail list logo
