bug#56514: ircs:// integration for rcirc (bug#56514)

bug#56514: ircs:// integration for rcirc (bug#56514)

[J.P.]

"J.P." <jp@neverwas.me> writes:

> Rather than mess with `func-arity' or the like, I've opted to just
> hijack an existing variable from the url(-vars) library,
> `url-current-object', which seems ready made for this purpose. The
> idea is to simply bind it to the parsed URL object during calls to
> `url-irc-function'.

Please disregard the above (meaning most everything from my previous
email). Turns out I forgot all about Compat (ironically), which should
make this all a nonissue.

> simply arranging to switch to 'tls whenever the port is 6697 should
> have you pretty well covered, I think.

Actually, this bit here still applies if by chance you want rcirc to
handle ircs:// links. (Not saying you should.)

Thanks and apologies for the noise.

bug#56514: ircs:// integration for rcirc (bug#56514)

[Philip Kaludercic]

"J.P." <jp@neverwas.me> writes:

>> simply arranging to switch to 'tls whenever the port is 6697 should
>> have you pretty well covered, I think.
>
> Actually, this bit here still applies if by chance you want rcirc to
> handle ircs:// links. (Not saying you should.)

I think this would be a nice thing to have (not that I encounter ircs://
links that often...).

> Thanks and apologies for the noise.

No problem, I was more confused than disturbed in any way.

bug#56514: ircs:// integration for rcirc (bug#56514)

[J.P.]

Hi Philip,

Just a heads up: I'm in the process of possibly tweaking url-irc (and
browse-url) to better support irc:// links in internal Emacs apps. If
you're interested, this mostly concerns the second patch here:

  https://debbugs.gnu.org/cgi/bugreport.cgi?bug=56514#22

Basically, I wanted a way to tell `url-irc-erc' whether to connect via
TLS without relying on port numbers and without changing the signature
of `url-irc-function'. Rather than mess with `func-arity' or the like,
I've opted to just hijack an existing variable from the url(-vars)
library, `url-current-object', which seems ready made for this purpose.
The idea is to simply bind it to the parsed URL object during calls to
`url-irc-function'. Please let me know if you see any downsides
to doing this or if a smarter approach comes to mind.

BTW, as the patch shows, I've left the rcirc side alone. But if you want
to handle ircs:// links without bothering with all the
`url-current-object' business above, simply arranging to switch to 'tls
whenever the port is 6697 should have you pretty well covered, I think.
Let me know if that doesn't make sense.

Thanks,
J.P.