Bug 126566

Summary: Half-hop status is not properly recognised
Product: [Applications] konversation Reporter: Florent Bruneau <florent.bruneau_kde>
Component: generalAssignee: Konversation Developers <konversation-devel>
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: 0.19   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Florent Bruneau 2006-05-01 15:29:39 UTC
Version:           0.19 (using KDE KDE 3.5.2)
Installed from:    Gentoo Packages
Compiler:          gcc 4.1 
OS:                Linux

In user list, half-ops appears without any kind of op privileges and their surname have a %
eg :
%Schmurtz
%Ey

Other kinds of privileges are displayed as expected.

Here is a patch to correct this :
diff -ur konversation-0.19/konversation/src/server.cpp konversation-0.19.new/konversation/src/server.cpp
--- konversation-0.19/konversation/src/server.cpp   2006-01-30 09:43:46.000000000 +0100
+++ konversation-0.19.new/konversation/src/server.cpp   2006-05-01 15:08:52.000000000 +0200
@@ -195,8 +195,8 @@
     m_socket = 0;

     // TODO fold these into a QMAP, and these need to be reset to RFC values if this server object is reused.
-    serverNickPrefixModes = "ov";
-    serverNickPrefixes = "@+";
+    serverNickPrefixModes = "ovh";
+    serverNickPrefixes = "@+%";
     channelPrefixes = "#&";

     timerInterval = 1;                            // flood protection
@@ -498,7 +498,7 @@
             QString::number(m_serverGroup->serverByIndex(m_currentServerIndex).port()));

         // set up the connection details
-        setPrefixes("ov","@+");
+        setPrefixes("ovh","@+%");
         statusView->appendServerMessage(i18n("Info"),i18n("Looking for server %1:%2...")
             .arg(m_serverGroup->serverByIndex(m_currentServerIndex).server())
             .arg(m_serverGroup->serverByIndex(m_currentServerIndex).port()));
Comment 1 Peter Simonsson 2006-07-03 10:47:04 UTC
Patch applied in svn trunk, will be in 0.20. Thanks for the report and patch.