on_unknown_command
no way to compare when less than two revisions
Differences
This shows you the differences between two versions of the page.
| — | on_unknown_command [2007/02/13 06:05] (current) – created - external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | #$EPIC: on_unknown_command.txt, | ||
| + | ======Synopsis: | ||
| + | [[on]] [< | ||
| + | |||
| + | ======Description: | ||
| + | Whenever the command in a [[command statement|ircii_syntax]] is neither | ||
| + | a builtin command nor a user-created alias, it is an //unknown command//. | ||
| + | When [[set unknown_command]] is **off**, the command statement is hooked | ||
| + | through this handler. | ||
| + | |||
| + | This feature is intended for automatic command completion. | ||
| + | statement explicitly prefixed the command with two slashes, indiciating a | ||
| + | built-in command, then those slashes will be preserved. | ||
| + | any leading slashes will be omitted. | ||
| + | |||
| + | ======Parameters: | ||
| + | |$0 |The unknown command in a command statement | | ||
| + | |$1- |The arguments to the unknown command | ||
| + | |||
| + | ======History: | ||
| + | This first appeared in EPIC5-0.3.2. | ||
| + | |||
on_unknown_command.txt · Last modified: 2007/02/13 06:05 by 127.0.0.1
