On 03/28/2012 11:19 AM, Ed Greshko wrote:
On 03/28/2012 08:26 PM, Patrick O'Callaghan wrote:
Because I'm not trying to set a handler for BitTorrent. That part
already works. As I noted in my OP, the problem here is that magnet
links are not signalled by a special file extension or MIME type, just
by a magnet: protocol flag at the start of the URI. Here's an example of
one:
magnet:?xt=urn:btih:29b30e19144ee41266e40096ffa09714b6541103&dn= ... etc.
IOW it's analogous to http: or file: or email: but I can't get a clear
answer on the mechanics of how this is handled by KDE. Clearly something
in my KDE setup thinks that these things should be handled by Ktorrent,
but where is this stated and how do I change it? I repeat that no
Ktorrent .desktop file on my system even mentions magnet, so what's
going on?
OK.... I see what you're after....
Doing a little "test"....
If I use chrome and click on a magnet link it will call ktorrent. If I erase
ktorrent it will call transmission. If I erase transmission it will do nothing.
If I use firefox, it will only use transmission....but when it does it brings up a
dialog box asking if I want to use it or choose another application. So, one could
pick ktorrent or in your case qBittorrent.
Now, the question is...what is the installation of ktorrent or transmission doing
that make chrome aware that it can deal with the magnet protocol
Firefox honours the setting you put in using the gconftool-2 commands
this page, but Chromium appears no to.
http://pclosmag.com/html/Issues/201203/page14.html
begin:vcard
fn:Patrick Boutilier
n:Boutilier;Patrick
org:;Nova Scotia Department of Education
adr:;;2021 Brunswick Street;Halifax;NS;B3K 2Y5;Canada
email;internet:boutilpj@xxxxxxxxxxx
title:WAN Communications Specialist
tel;work:902-424-6800
tel;fax:902-424-0874
version:2.1
end:vcard
_______________________________________________
kde mailing list
kde@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/kde
New to KDE4? - get help from http://userbase.kde.org
