Jo-Erlend Schinstad wrote : > 2009/5/25 David Balazic <david.bala...@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!myu...@myhost PRIVMSG #ourChannel :<ascii 1>ACTION some > description<ascii 1> > > If I used "/say /me foo", then the channel should receive: > > :mynick!myu...@myhost PRIVMSG #outChannel :/me foo
It seems Pidgin takes this and displays it as if it were a CTCP ACTION, intead as a regular text. Even if someome with a different client would send it. So if some sends "...PRIVMSG #outChannel :/me foo", all people would see <someone> /me foo While Pidgin users would see ***someone foo. This is IMO a bug. Regards, David _______________________________________________ Support mailing list Support@pidgin.im http://pidgin.im/cgi-bin/mailman/listinfo/support