I had the same problem the other day, with a friend using WLM..
The transfer was randomly canceled between 70% and 90%, with a ~10MB file.
He didn't cancel the transfer, but in the status log I also had a BYE, preceded by the same stuff as him (GOT SID..) if I remember correctly.

now if you would like to change it yourself, you can always do it of course

Well, actually I did it a while ago..
I suggested that because many people seem confused by these bindings.

Yeah, but he's got a point.. I think Ctrl+Tab is easier to use than Ctrl+PgUp.
As it does nothing right now, why isn't it added ? That way everyone is happy..
Or did I miss something in the FAQ ?

Yeah, it's "\n"..

Anyway, it seems to work like that :
- When I open a conversation, it always work fine.
- When someone else opens a conversation, either it's fine as well : remind shows the last X lines and the windbag plugin works as expected.
- When someone else opens a conversation (always the same contact, apparently), both remind and windbag fail : remind shows nothing, and windbag skips one of the newlines.. Which is weird because the rest of the output is printed out correctly.

kakaroto :
Well, obviously he's using Windows, so no bash scripting.

Improfane :
Most people will want their logs to look as much as possible like the original conversation. They will want to keep the colors. And as MSN allows you to change your font color for every single message you send, you just have to save it inside the log. The log viewer can't just guess which color was used at that time.

billiob :
Is anyone working on XML logging already ? I might have a look into that.

I found where the problem is..
When the conversation is started by the other person, one of the newlines is not outputted correctly.
Apparently, the remind plugin doesn't work either when the other person opens the conversation.
I don't know if this is normal, but it seems weird to me.

It works fine for me..

Make sure you don't have the plugin in both ~/.amsn/plugins and /usr/share/amsn/plugins (assuming you're using linux).. If you do, remove the one in ~/.amsn/plugins and it might work again. It happened to me a few months ago.

I had the same problem twice.. It only happened in one conversation and not in the others.
The newline fails to be inserted in these conversations for some reason, and if I remember correctly, closing that conversation is enough. Maybe you need to unload/reload the plugin as well.

snipe2004 :

Yes, that's easy to do.. Actually that's what I did at first, but it wasn't clear enough in my opinion. Having the timestamp the same color the contact uses is what NWM did if I remember correctly.. I don't like it because on the long run you can't differentiate the timestamp and the message easily enough.

NoWhereMan :

That's what I tried to do, but I can't find a way to change the size consistently according to the font the user uses. That's the first time I code tcl..

nsma :

That's how it is right now..

Thank you..

What do you think about the timestamps ? Should I make them less visible ?

Hmm, it seems to work pretty well. But I'd like to find a way to make the timestamp less obvious..

My version is available here.

Ah, that's right.. Sorry, I don't know how I could miss that.. It was only five posts above.. :shock:

Anyways, I modified the plugin so it works this way :

Yvan says:
[18:55:10] message1
[18:55:20] message2
[18:55:21] message3
[18:55:23] message4
[18:55:26] message5

I made it check whether the user actually want to show the timestamps or not, and colored the timestamps in gray. Now it doesn't change the conversation history, either. I also cleaned a few other things.

I'll upload it later if someone's interested. I still need to test it a bit. :wink:

Does this plugin still work with the latest SVN ?

I tried it for the first time this afternoon, and it didn't work properly.. It outputted something like that :

[18:55:10] Yvan says:
message1
[18:55:20] Yvan says:

[18:55:20] message2
[18:55:21] Yvan says:

[18:55:21] message3
[18:55:23] Yvan says:

[18:55:23] message4
[18:55:26] Yvan says:

[18:55:26] message5

I can't say.. The « authentication failed » error was gone before I updated SVN.
Now I only get unknown errors..

Same here. But now I got an « Unknown error » again..

Then it seems to have worked with another contact (not error was displayed, but I don't know if he actually got the message).
And now I tried again with another contact, and I get « authentication failed ».

Then with another contact it seems to work again. So, to sum up, either I get no error, « invaliduser », « unknown error » or « authentication failed ». But that last one happened only on one, and always the same, contact.

By the way, how come there is nothing in the protocol log when sending OIMs ? Are they sent another way ?


UPDATE : apparently they didn't receive any message, even when no error was reported.