Regarding codes used for Pidgin

[Jo-Erlend Schinstad]

2009/5/25 David Balazic <David.Balazic at hermes-softlab.com>:
> Ethan Blanton wrote>
>
>> David Balazic spake unto us the following wisdom:
>> >  -  "/say /me foo" is not sent to channel, but interpreted
>> as a regular
>> > "/me foo" command
>>
>> Not exactly.  Pidgin interprets any incoming message of the form "/me
>> foo" as an emote.  You're actually sending "/me foo" to the channel,
>> your Pidgin is simply displaying it the same as it would a CTCP
>> ACTION.
>
> Why would it do that ?
>
> Regards,
> David

This sounds strange. There will never be any incoming commands in the
form "/me description". /me is simply a CTCP ACTION message, which is
a PRIVMSG message. So, if I would send a /me to a channel, then everyone
in the channel -- except me, the sender -- would receive

:mynick!myuser at myhost PRIVMSG #ourChannel :<ascii 1>ACTION some
description<ascii 1>

If I used "/say /me foo", then the channel should receive:

:mynick!myuser at myhost PRIVMSG #outChannel :/me foo

The IRC protocol spesifies that you can never know if your messages have been
sent, received or read. You can wait for error messages, but they might arrive
several minutes after you sent the message, so that's not a good idea either.
So, if you want to handle ctcp actions, then you really have to interpret them
locally.

But what on earth has /say got to do with any of this?

Jo-Erlend