Version: 0.10.3 (using KDE KDE 3.4.2) Installed from: Mandriva RPMs When chatting in an IRC channel, and both "neo" and "neopoop" are logged, and I try to send a message to neo just writing "neo: good morning!" , Kopete will change the "neo: " to "neopoop: " at its will, after I send the message. This means that I write something to a person, and it ends looking like I wrote it to someone else - that is a bit more than annoying when keeping a conversation. (I guess it will pick whichever name will come first in it's internal list of nicks for the channel) It also happened for "adrian" and "adrian_home". For the time being, the workaround is to put some random text before the nick, in the start of the message. (Like ": neo: good morning!" )
if you hit tab more than once, does it cycle?
It does not cycle. But that is another issue. What I am reporting here is taht if you manually type in a nickname, kopete will change it _after_ you send the message. One is helpless but shouting to the room that there is a bug in the irc client. Like this: if there are both "neo" and "neopoop" on the room, and I type and send: neo: hello! In the chat area, what is displayed is: neopoop: hello! -- If the nickname is not the first thing on the message, it is not touched. (i.e. : neo: hello! is a workaround) I have not tried with commas. What you mention in #1 is another, probably related issue - if I'd try to auto complete for "neo" , it would auto-complete for "neopoop" and get stuck there.
This bug still exists in Kopete 0.12.3 (KDE 3.5.5) on openSUSE 10.2 final.
On a related note, is there any way to turn this function off? It's quite annoying messages get changed after they've been sent, and I've run into issues when simply writing someone's name followed by a colon, and it gets expanded to their whole nick name. I would rather have this auto-complete off, possibly with only the TAB-completion, but without the automated completion *after* submitting.
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!