[OTR-dev] /me bug

[Thijs Alkemade]

On 10 sep. 2013, at 22:57, Kurt Roeckx <kurt at roeckx.be> wrote:

> If think you always want to have the whole PRIVMSG (and NOTICE)
> encrypted, regardless if it's a CTCP or not.  So that would be:
> PRIVMSG nick :?OTR...\r\n
> 
> What I'm confused about is why this would require Pidgin-OTR to
> parse anything.  But then I have no idea which signals pidgin has.
> What you want is that you can replace the part between the : and
> the \r\n.  Does an irc-receiving-text catch the whole message
> including the PRIVMSG?  Is there a way to only do this for
> the text part of the PRIVSG?
> 
> 
> Kurt

Pidgin's IRC prpl uses two sets of signals currently:

"sending-im-msg"/"receiving-im-msg": These are emitted only for actual IMs, so
not for any form of CTCPs. For most plugins that makes sense, you don't want
a pop-up notification for every CTCP PING you get.

"irc-sending-text"/"irc-receiving-text": These are emitted with a buffer of
the raw protocol data about to be sent/just received. I think this is always
exactly 1 line, but I'm not sure if that is guaranteed.

Thijs
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 841 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.cypherpunks.ca/pipermail/otr-dev/attachments/20130910/9822bc60/attachment.pgp>