[konversation] [Bug 481051] New: Can't automatically identify with nickserv when my password has a semicolon in it
bugzilla_noreply at kde.org
bugzilla_noreply at kde.org
Thu Feb 8 12:01:14 GMT 2024
https://bugs.kde.org/show_bug.cgi?id=481051
Bug ID: 481051
Summary: Can't automatically identify with nickserv when my
password has a semicolon in it
Classification: Applications
Product: konversation
Version: unspecified
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: konversation-devel at kde.org
Reporter: inhahe at gmail.com
Target Milestone: ---
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.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Konversation-devel
mailing list