18 years ago
12 years ago


(Reporter: gwalla, Assigned: rginda)


Firefox Tracking Flags

(Not tracked)




18 years ago
As of Mozilla 0.8.1, using the /quit command in Chatzilla gives an error "Sorry,
"quit" not implemented". The only way to log off of a network is to close
Chatzilla or connect to another server, which isn't very graceful.

Comment 1

18 years ago
/quit used to disconnect you from whatever network you issued the command from,
but not exit chatzilla, while /exit disconnected you from all networks *and*
exited chatzilla.  It was impossible to remember which did which (as you can
probably imagine).  So, I renamed /quit to /disconnect, and left /quit to error
with "not implemented".  In retrospect not the best idea, because it leads
people to believe that there is no way to exit the app.  I'll alias quit to exit.
Ever confirmed: true
Summary: implement /quit → alias /exit as /quit

Comment 2

18 years ago
*** Bug 74452 has been marked as a duplicate of this bug. ***

Comment 3

18 years ago
wouldn't it be better to say use if you want to 
disconnect from a server or network please use /disconnect <server/network>
if you want to exit chatzilla (which will disconnect you from all servers and 
dcc connections) please use /exit

Comment 4

18 years ago
Most clients use /quit to disconnect. It's the standard (well, as standard as
anything is in IRC) method of logging off. It's sort of disconcerting to try to
use it and be confronted with an error, or a message saying that a different
command should be used instead. 

I think /quit should be aliased to /disconnect, myself. On other clients, using
/quit won't cut off your DCC connections, and AFAIK on clients that support
multiple server connections it only disconnects from a single server.

Comment 5

18 years ago
Changing Platform/OS to All/All. There's nothing about this bug that is
OS: Windows NT → All
Hardware: PC → All

Comment 6

18 years ago
This is fixed in the (upcoming) patch attached to 27805
Depends on: 27805

Comment 7

18 years ago
*** Bug 88730 has been marked as a duplicate of this bug. ***

Comment 8

18 years ago
bug 27805 was committed so this issue is fixed in latest builds
Last Resolved: 18 years ago
Resolution: --- → FIXED
Product: Core → Other Applications
You need to log in before you can comment on or make changes to this bug.