EPIC Enhanced Programmable IRC-II Client

quit

Exit IRC and terminate the entire EPIC client session.

Synopsis

/quit [quit-message]

Description

When you are finished talking, quit disconnects from every server, closes the client, and returns control to the shell. It has the same built-in behavior as exit. Use disconnect when you want to close a server connection while keeping EPIC running.

The optional quit message is the entire remaining command text. An explicit message becomes the quit message for every server. Without one, each server uses its configured message, falling back to /set quit_message, then Leaving if no message is available. During connection closing, %s in the message is replaced with the EPIC version. An empty resulting message omits the outgoing IRC quit request, though the connection still closes.

Shutdown performs these actions:

This list describes shutdown effects rather than a contractual ordering for scripts. Exiting with tracked subprocesses can take a short time. The command does not wait for server acknowledgement and does not return to its calling script. Hooks can perform actions during shutdown; calling quit recursively from them forces immediate termination instead of repeating normal cleanup.

The command is always registered, has no options, and works without a live IRC connection. It produces no separate success result.

Examples

Quit with a message:

/quit I'll be back soon!

Quit using configured messages:

/quit

Source

Registration and e_quit are in source/commands.c. irc_exit, its hook, terminal cleanup, and shutdown callbacks are in source/irc.c. Per-server messages, formatting, and connection closing are in source/server.c, with subprocess cleanup in source/exec.c.