If you type in messenger plus "/me pokes you", msg plus sends "«I pokes you" instead. You can observe this behaviour when you chat with a person who has no messenger plus, e.g. the normal live messenger or an other messengers: They only see "«I pokes you".

The point is, that many messengers like trillian, pidgin and others can handle /me (so "/me pokes you" gets displayed as "username pokes you"), but msg plus don't sends "/me" but "«I".

So if for example, a trillian contact sends you "/me pokes you"; you (with msg plus) don't see "username pokes you". You see only "/me pokes you".
And if you (with msg plus) say to a trillian/pidgin/kopete/... contact "/me pokes you", msg plus sends "«I pokes you" and the contact can only see this "«I pokes you".

Therefore, messenger plus should send and accept "/me" instead of "«I", because it's much more compatible to other programs.

Messenger Plus was using this feature before either of those programs became popular.  For backwards compatibility purposes, Messenger Plus! should not change, however it might be nice to parse "/me" as well as "«I"

I don't think it should be changes to send "/me" as this means that it is not compatible with a lot of machines running MP! 3.x and people who won't upgrade MP!L.

quote:

---

Originally posted by markee
Messenger Plus was using this feature before either of those programs became popular.

---

quote:

---

Originally posted by markee
I don't think it should be changes to send "/me" as this means that it is not compatible with a lot of machines running MP! 3.x and people who won't upgrade MP!L.

---

Looking through the history, this feature has been around since MP! 1.40 way back in October 2001.

Trillian had added the feature before April of 2001, so yes they were first, I will admit that, but neither should change a method of doing it after such a length of time.

I concede that MP! would have less users, however 50million is quite significant!

I really believe that MP!L should interpret "/me" as it does its own commands, but I don't think it should send it out differently to what it has previously for compatibility purposes.

quote:

---

Originally posted by cubefox
mirc

---

Also, if Plus! should parse "/me" in received messages, that somewhat ignores the command escaping feature.

Imagine this scenario:

1. The contact sends a message:

   code:

   ---

   //me is a cool command

   ---

2. The user receives the message:

   code:

   ---

   /me is a cool command

   ---

3. In the case the Plus! should replace that incoming message with "* User is a cool command", it basically destroys the idea of the contact about sending escaped commands.

I didn't hear about the "command escaping feature". Is it really more important than /me? I guess /me is much more often used.

quote:

---

Originally posted by cubefox
I didn't hear about the "command escaping feature". Is it really more important than /me? I guess /me is much more often used.

---

quote:

---

Originally posted by cubefox
I didn't hear about the "command escaping feature". Is it really more important than /me? I guess /me is much more often used.

---

Here is some script code that you can use to reproduce this feature how you want it to.  Please note that all of your MP!L contacts will now see "/me" when you send one of these messages though.

code:

---

function OnEvent_ChatWndSendMessage(ChatWnd, Message){
    return Message.replace(/^\/(\/me\s)/i,"$1");
}
function OnEvent_ChatWndReceiveMessage(ChatWnd, Origin, Message, MsgKind){
    return Message.replace(/^\/me(\s)/i,"«I$1");
}

---

It's a known limitation. (iirc, i think i am)