MSN core crash, and typing support in ebqt

There is one, probably in receiving a message. Can't tell more than
this, because the core just drops *dead*, stops responding to
everything. CPU usage is normal, gdb shows it in select() somewhere
in eb_polling_loop() as (presumably) normal, but everything ebqt
sends goes into a black hole. This didn't happen between two MSN
accounts in the same ebqt session (i.e. both mine), but did happen on
receiving the second message of a conversation...

"hello"
   "hello"
"this is a test to see if your program barfs"
[core is now in a coma]

In other news, typing is in ebqt, with sending commented out until the
core is ready to recognise it. Group chats still need to show *who* is
typing rather than just lighting up the icon, and the feature of
clicking the icon to disable sending typing is ignored and not saved,
but it's basically there in that you can see when an MSN (or other
supported service) buddy is typing. It worked in the above conversation
right up until the crash. ;-)

This also has the nifty side-effect of reintroducing an old feature: on
MSN at least, when someone double-clicks you to open the window, the
session is open and visible to you before they send anything. Old EB
would open the window on your end when this happened, if I remember
correctly. EbQt will now open a tab/window when typing is detected
(which is the earliest it is informed of the session). Thoughts? I can
disable this if people would prefer that, or if people really want to
freak out their friends, the core could send a "not currently typing"
message when the session's opened, to bring back exactly what old EB
had, in that you can answer before they even start typing. >:-)

-- 
Chris Boyle - http://cmb.is-a-geek.org/
GPG: B7D86E0F, MSN: [email protected], ICQ: 24151961,
AIM: kerneloops, Yahoo: kerneloops, IRC: cmb on irc.uwcs.co.uk