Bug 481051

Summary: Can't automatically identify with nickserv when my password has a semicolon in it
Product: [Applications] konversation Reporter: inhahe
Component: generalAssignee: Konversation Developers <konversation-devel>
Status: REPORTED ---    
Severity: normal CC: inhahe
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description inhahe 2024-02-08 12:01:14 UTC 
I'm using Windows 11. I just installed the latest developmental release of Konversation.

In the "edit server" dialog, in the "commands" field, I entered "/msg NickServ IDENTIFY inhahe <password>", where "<password>" is my actual password, and it has a semicolon in it. Konversation seems to treat that as a command separator. I even tried to escape it using a backslash, no luck. So, there should be a way to include semicolons in commands, or, if there is already a way, it should be more obvious how to. Maybe enable backslash to escape semicolons, or maybe make the "commands" field multiline where you add members separately with the "add" button like with the "servers" and "channels" fields, and make semicolons no longer separate commands?

Also, there are channels on Libera that I can only join if I'm registered. I don't know if Konversation will try to join them before or after it executes the command to identify with services. It would be annoying if it tries before and hence fails. 

One other thing, I don't think I noticed the capability to identify using SASL? That would be nice, if it doesn't exist.
Comment 1 inhahe 2024-02-08 12:33:39 UTC 
Of course, the obvious problem with allowing backslash-escaped semicolons in commands would be that any command that's *supposed* to have a backslash in it should rightly be specified as a double-backslash, and that wouldn't necessarily be obvious to the user. I guess a note could be put into the dialog. And it could break people's commands they've already entered in previous versions that have backslashes, but it doesn't have to because they could just be converted to double backslashes.

The obvious problem with making the commands be entered separately in a multiline text box and making the semicolon no longer separate commands would of course be that users would have entered commands on a single line separated by semicolons in previous versions. But that could easily be converted, too. Just separate the already-existing commands into individual lines by splitting the command string on semicolon. (That automatic manipulation of previously entered data might seem a little uncomfortable for the user, but I think that would be on a purely emotional level; none of the the data or its execution would be functionally changed, corrupted, lost, or whatever in any way.)