xmpp: URLs in Windows?

[Eion Robb]

Not sure if you didn't get my email with the screenshot attached to it?
https://pidgin.im/pipermail/support/2018-October/030377.html

If you've got an account set up with 'Hangouts' as the account type, rather
than 'XMPP' then the Hangouts plugin won't provide any URI handling.

Cheers,
Eion


On Wed, 24 Oct 2018 at 09:56, Phil Smith III <lists at akphs.com> wrote:

> See previous note at bottom:
>
> *C:\Program Files (x86)\Pidgin\pidgin.exe
> --protocolhandler=xmpp:xxxxxxx at gmail.com <xmpp%3Axxxxxxx at gmail.com>*
>
> So the URI was:
>
> *xmpp://xxxxxxx@gmail.com <xxxxxxx at gmail.com>*
>
>
>
> But they are all Hangouts (well, and Skype). Is the protocol wrong?
>
>
>
> *From:* Eion Robb [mailto:eion at robbmob.com]
> *Sent:* Tuesday, October 23, 2018 3:06 PM
> *To:* Phil Smith III <lists at akphs.com>
> *Cc:* Pidgin Support List <support at pidgin.im>
> *Subject:* Re: xmpp: URLs in Windows?
>
>
>
> What was the full URI you were using?
>
> Do you have any xmpp accounts set up in Pidgin, or is it still only set up
> with a Hangouts account?
>
>
>
> On Wed, 24 Oct 2018 at 02:50, Phil Smith III <lists at akphs.com> wrote:
>
> Ran with debugging:
>
> *(09:47:05) util: Processing message 'x at gmail.com <x at gmail.com>' for
> protocol 'xmpp' using delimiter ';'.*
>
> *(09:47:05) GLib: g_hash_table_lookup: assertion `hash_table != NULL'
> failed*
>
>
>
> (the *x at gmail.com <x at gmail.com>* was a Gmail ID of mine, and it was valid)
>
>
>
> *From:* Phil Smith III [mailto:lists at akphs.com]
> *Sent:* Tuesday, October 16, 2018 7:04 PM
> *To:* 'Eion Robb' <eion at robbmob.com>; 'Phil Smith III' <lists at akphs.com>
> *Cc:* 'Pidgin Support List' <support at pidgin.im>
> *Subject:* RE: xmpp: URLs in Windows?
>
>
>
> 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 <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/20181024/6f1cc97f/attachment.html>