xmpp: URLs in Windows?

[Eion Robb]

Ok, a few things to go through:

> --help doesn’t show --protocol.
The --help info is generic to both Windows and non-Windows, so it only
shows options common to both.  The --protocolhandler= switch is definitely
the right one.

> I’m using the Hangouts plugin
The hangouts plugin doesn't have a URI handler, and it definitely wouldn't
work with xmpp: uri's; they would get passed off to an active jabber/xmpp
account you've got set up in Pidgin

When I run the command you ran I get a new conversation windows to
xxxxx at gmail.com.  Just to make sure, I tried from the Start->Run prompt and
get the same result:
[image: image.png]

The only thing related to a uri scheme for hangouts, is the uri that is
used on iOS to open the app: com.google.hangouts:// (from
https://stackoverflow.com/questions/36182069/google-hangouts-ios-application-url-schemes
) but this looks to be ios-specific and doesn't work on any other
platform.  I could potentially add it to the Hangouts plugin, but i'm not
sure how much value that would add?

Cheers,
Eion


On Wed, 17 Oct 2018 at 12:04, Phil Smith III <lists at akphs.com> wrote:

> Well, ok, that’s kinda what I’d expected – I installed Pidgin so long ago
> that I’ve just let upgrades run without looking (since it’s one of the
> civilized installers that remembers the options!) and had forgotten it was
> there.
>
>
>
> BUT it is set, and I just reinstalled to be sure. Looking in the Registry,
> I find:
>
> *[HKEY_CLASSES_ROOT\xmpp\shell\Open\command]*
>
> has value
>
> *"C:\\Program Files (x86)\\Pidgin\\pidgin.exe --protocolhandler=%1"*
>
>
>
> But:
>
> *C:\Program Files (x86)\Pidgin\pidgin.exe
> --protocolhandler=xmpp:xxxxxxx at gmail.com <xmpp%3Axxxxxxx at gmail.com>*
>
> from a Run or Command prompt does nothing.
>
>
>
> I’m starting to wonder about the *--protocolhandler* option. is it
> correct? And I’m using the Hangouts plugin; would it still be *protocolhandler=xmpp:xxxxxxx at gmail.com
> <http://gmail.com>*? I notice that Pidgin doesn’t even start when I
> specify this option, which makes me think it rejected it entirely.
> *--help* doesn’t show *--protocol*. I’m on 2.13.0.
>
>
>
> *From:* Eion Robb [mailto:eion at robbmob.com]
> *Sent:* Tuesday, October 16, 2018 5:14 PM
> *To:* Phil Smith III <lists at akphs.com>
> *Cc:* Pidgin Support List <support at pidgin.im>
> *Subject:* Re: xmpp: URLs in Windows?
>
>
>
> The windows installer .exe has an option to register handlers with XMPP,
> AIM and something else.
>
>
>
> The manual way to do it used to be through:
>
> Control Panel->Default Programs->Associate a file type or protocol with a
> program -> Choose default applications by protocol
>
> but it looks like they've gotten rid of the option to manually add a
> protocol to the list now?
>
>
>
> On Wed, 17 Oct 2018 at 06:30, Phil Smith III <lists at akphs.com> wrote:
>
> pidgin at alexoren.com wrote, in part:
> >> the second does nothing.
>
> >Works for me, but does not unescape the message, so spaces are a problem.
>
> Also does nothing from a Run prompt. So I'm back to the original question:
> how do I register Pidgin to respond to XMPP: URLs?
>
> _______________________________________________
> Support at pidgin.im mailing list
> Want to unsubscribe?  Use this link:
> https://pidgin.im/cgi-bin/mailman/listinfo/support
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://pidgin.im/pipermail/support/attachments/20181017/25c1b1bf/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image.png
Type: image/png
Size: 81793 bytes
Desc: not available
URL: <https://pidgin.im/pipermail/support/attachments/20181017/25c1b1bf/attachment-0001.png>