Regarding codes used for Pidgin

[Michael Secord]

I think the whole issue here, is that the "/me" is a good command, but 
when you add "/say" in front of me, it should NOT interpret the "/me" as 
the actual command, but just as plaintext.  Basically using "/say" as 
the escape character that would be used in IRC clients.

-Michael

-------- Original Message --------
Subject: Re: Regarding codes used for Pidgin
From: Ethan Blanton <elb at pidgin.im>
To: support at pidgin.im
Date: 5/25/2009 12:00 PM

> David Balazic spake unto us the following wisdom:
>> 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 ?
> 
> Perhaps I should have been clearer ... Pidgin interprets an incoming
> message of the form "/me foo" as an emote on *any protocol*.  This
> behavior goes back years and years, and it was spawned from many
> users' desire to have emotes on protocols that have no native support.
> The fact that it also "works" on IRC, which has native emote support,
> is simply fallout.
> 
> As to whether or not it's holistically a good idea, who knows -- but
> I've never seen it come up before, so I'm inclined to think it's not
> hurting much.  ;-)
> 
> Ethan
> 
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> Support mailing list
> Support at pidgin.im
> http://pidgin.im/cgi-bin/mailman/listinfo/support