I use multiple servers across multiple networks. Each one has been correctly listed separately. Each server of course has it's own unique password, along with unique connect commands for example samode commands. When setting a password for server A on network A, then setting a password for server B on network B, Konversation consistently uses the password that you last connected to, and it even changes that password within Konversation. This of course causes nickserv to fail auth., along with any server connect commands. It as well uses and copies all of that info over to ALL connect command lines across all servers which will then cause errors on servers where those commands would not be used for that particular server. I am now forced to use XChat for connections that I have connect commands, ect, and Konversation can ONLY be used for 1 network period. This is very annoying.
I'm not sure I understand fully. Are you saying that the GUI dialogs reflect this, i.e. something you entered in the "Commands" field for one network makes it to the "Commands" field for a different network? Or does it just happen during connecting? Would you be willing to post complete steps-to-reproduce for a test case, i.e. all steps for setting up two networks and connecting in a way that causes this failure? If there's a bug there, we'd certainly very much like to fix it in time for 1.5.
For instance I create a connection of irc.xxxxx.dk under "network", place the chanles to auto join under "auto join chanels", under "edit" "identities" you can then place your nickserv password, type "standard nickserv" "service" "nickserv", "command" "identify" "password" ******* (password of choice for NS). Then click OK. If I repeat this process, example: irc.freenode.net, with a different password, or even place a command into pre-shell command, and now try to connect to one network, than the other. It will reuse the password, and replace the password as well as the pre-shell commands. Example: I connect to irc.xxxx.dk port 7000 with NS password, completes flawlessly. Now I try to connect to irc.freenode.net which of course I use a different password, it will use the password that has been placed into the 1st server i connected to or even vice versa. Each password does NOT persist across different server connections and they get re-written, as do shell commands. For freenode I do not use shell commands nor server connect commands. I do on irc.xxx.dk. This forces me to have to manually use samode commands to appx.16 different chanels for the dk server, as well as having to manually auth to NS. I even tried to use LOAD -e /path/to/command/file and even that gets copied across to ALL servers. Like I said, I am only able to use Konversation for the connection to 1 server period because of this bug(s). Thank you for your diligence.
Ah, you're talking about Identities, not network-specific settings (I thought you meant the Commands box in the Edit Network dialog). Note that in the Identities dialog you can create *additional* identities, and every network can have a different identity set via the drop-down in the Edit Network dialog. If you're using the same identity for all networks then, well, they'll share the same settings; that's kind of the point. If you want separate identity settings for each network, you can just create and assign as many identities as you want.
My nick across ALL networks are the same. I have no need to use a different nick across servers. It is a nick I have been using for years and am known by. And yes, I have created seperate indentities in the server list, but they are ALL the same nick. And yes, it is re-using ALL settings no matter what i do. I am not the only one that uses the same nick across different servers and networks. Everyone has got to be running into the same situation. Unfortunately if there is no way around this, other than make new nicks for every single server Im on, I will be forced to stop using Konversation, because that is not a viable solution for me nor others. And i rather like this client. Typically I used Xchat which support was dropped for 2 years ago, AND I use FiSH. Very few clients have a working FiSH/fishlim for linux that can properly do /keyx auth :) Konversation also handles FiSH perfectly :) Can you possible fix this problem?
There is no reason you can not have several identities containing the same nick and have the rest of the settings being different.
Unfortunately, that can not be accomplished. Even if I ping off one network and then auto reconnect, it auto uses the last password for nickserv and places THAT password across ALL NS password fields. it does the same thing with connect commands which now I have had to remove because of that. I have separate networks already set up, with the same nick in all of them, and it happens every single time, and places the last password used into ALL the NS password boxes on it's own. So, in this essence, this bug is also in the pre-shell field AND if I switch to "server password" field. It replaces everything. Same result. I can only use Konversation for 1 server period.
You can just configure the same nick in the different identities. And make sure that in Edit Network you're selecting the right identity for each network. And no, there have been no other reports of problems with this I'm afraid ... Myself I have about half a dozen networks configured, and about three or or so identities, i.e. some networks reuse the same identity and others have their own identities, but all but one of my identities uses the same nick. It's all possible and works correctly here. I'm not saying there might not be a problem on your end, but I'm currently not able to decide if there is an actual code issue or you're just not using the config the right way yet :).
(In reply to comment #7) > You can just configure the same nick in the different identities. And make > sure that in Edit Network you're selecting the right identity for each > network. > > And no, there have been no other reports of problems with this I'm afraid ... > > Myself I have about half a dozen networks configured, and about three or or > so identities, i.e. some networks reuse the same identity and others have > their own identities, but all but one of my identities uses the same nick. > It's all possible and works correctly here. I'm not saying there might not > be a problem on your end, but I'm currently not able to decide if there is > an actual code issue or you're just not using the config the right way yet > :). OK, I somewhat fixed the problem, although I consider this a workaround. I had to go to each server and rename them all with the name of the server being the actual name of the server. Then under identity I did the same. Gave each one the actual name of the server owner. Then under nickname I of course kept my nick in there. It worked. Passwords and connect commands persisted upon re-launch. \o/ Wish it didn't have to be this way but at least it works. Thank you :)
OK, good.