[Konversation-devel] [Bug 91934] weird behaviour on /quit
Eli MacKenzie
argonel at sympatico.ca
Tue Mar 14 22:14:42 CET 2006
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
http://bugs.kde.org/show_bug.cgi?id=91934
------- Additional Comments From argonel sympatico ca 2006-03-14 22:14 -------
The only way I can see that a user gets the expectation that /quit
should close the application is exposure to other IRC clients which
may well be doing things incorrectly. Should we copy a poor
implementation?
So perhaps we're talking about the origin of the expectation. While
making /quit entirely exit the application would fulfill the
expectations of some, for others it would be a complete and annoying
surprise. If we could accurately gauge the users initial expectation
and turn this into a satisfying set of defaults, making this
configurable might be useful. But we don't gather any such
information, so the only expectation we should be setting for the user
is that the client follows the protocol.
In fact, it could be that closing anything other than the socket on
the basis of /quit is wrong. For instance, check out xchat. /quit
merely closes the connection - /close is what disposes of tabs or
quits the application.
QUIT, an IRC protocol command, quits the *connection*, not the
application. Reflect on the fact that the QUIT command takes an
argument which is the text to send for the channel visible IRC quit
message. How does one prevent the sending of the default quit message?
Very simple: use the IRC protocol. "/quit :"
We have in other situations of a similar nature decided to remain true
to the IRC protocol, instead of having Konversation isolate the user
from the vagaries of how IRC actually works. By changing what /quit
does, we present an unpredictable subset of commands that don't work
like their IRC counterparts. Where does the someone get the
expectation for this?
An option for those that want the client to quit is for us to create a
command-option of some sort, which you could then alias for /quit. As
yet we have no standard for command options, one would have to be
developed.
(if this message shows up again without this line, then i apologize in advance. somehow the message was sent but didn't arrive until after my patience had run out :)
More information about the Konversation-devel
mailing list