[Konversation-devel] [Bug 128786] Konversation does not respond to other clients' "/leave" on Undernet servers

[Eike Hein]

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
         
http://bugs.kde.org/show_bug.cgi?id=128786         
sho eikehein com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |FIXED



------- Additional Comments From sho eikehein com  2006-06-08 13:36 -------
Alright, when I got home in the middle of the night yesterday (tired) and hastily went through my bug mail, I did in fact forget that we fixed this problem a couple of weeks back in SVN rev 531718 (on the other hand, without your RAW lag I couldn't have been certain). Quoting my commit message:

"* Add tentative fix for slighly peculiar message-less PART on ircu and
  potentially others. Argument handling in InputFilter may require re-
  factoring as per the information submitted to the mailing list. Thanks
  to Nimrod Gutman and the ircu team for aiding the debugging effort."

IRC users can specifiy an optional "message" for their PART/QUIT events that is displayed in other users' clients as reason for their going away (often used for a funny tagline, though). That's what I meant with "with and without message". This problem occurs on PARTs without a message, as ircu's message format in those cases deviates from most other IRC server applications, notably those we commonly test with. Subtle differences between IRC server implementation like that is what accounts for a significant part of the complexity in an IRC client.


The fix will be included in the next release of Konversation. Alternatively, you can get yourself a checkout of the development version from the SVN repository. Instructions can be found here: http://konversation.kde.org/wiki/SVN

SVN is presently stable; it may destabilize towards the end of the months when new feature work for 0.20 lands. So the time is now.