Regarding codes used for Pidgin

[Ethan Blanton]

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

-- 
The laws that forbid the carrying of arms are laws [that have no remedy
for evils].  They disarm only those who are neither inclined nor
determined to commit crimes.
		-- Cesare Beccaria, "On Crimes and Punishments", 1764
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 481 bytes
Desc: Digital signature
URL: <http://pidgin.im/pipermail/support/attachments/20090525/560dd834/attachment.sig>