[konversation] [Bug 481051] Can't automatically identify with nickserv when my password has a semicolon in it

[bugzilla_noreply at kde.org]

https://bugs.kde.org/show_bug.cgi?id=481051

--- Comment #1 from inhahe at gmail.com ---
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.)

-- 
You are receiving this mail because:
You are the assignee for the bug.